> Date: Fri, 21 Feb 2014 00:27:53 +0100 > From: "Armin K." <[email protected]> > To: BLFS Development List <[email protected]> > Subject: Re: [blfs-dev] BLFS Systemd Additions > > On 02/19/2014 11:00 PM, Armin K. wrote: > > Hello, I've taken some time to write "modifications" that are necessarry > > for the current BLFS book to get some packages to work with native > > systemd units or to utilize features that they can use from systemd > > components itself. > > > > The notes are available here if anyone wants to play with it. > > > > http://www.linuxfromscratch.org/~krejzi/notes.txt > > > > This is incredibly ugly to read, but I'm not very friendly with wikis > > and such to put them there. Note that instructions only up to > > > > IV. Networking > > > > for now. I hope to continue tomorrow since it's getting late now. > > > > Cheers > > > > Notes have been updated for remaining server packages. Only Iptables, > CUPS and Cups Filters modifications remain to be added. > > The following packages need to be modified and/or (not) installed when > using LFS systemd as a base. > > Chapter 3: The Bash Shell Startup Files . # + 58 pkgs. . > Chapter 39: alsa-utils-1.0.27.2 > > If anyone cares enough to add the instructions to the wiki, let me know. > Otherwise, I'll keep them at the same address. >
Might it be better all-round if you retained these as sets of patches against your own working copy of blfs book xml, and then apply/rebase them with mainline blfs book xml? That way, you kind-of get a de-facto blfs-systemd book? Yeah, I know it'd be likely not quite as straightforward as that. But, you're putting a non-trivial amount of resource expenditure into the above work: and then it's being stored/presented in a very un-structured way; thus, I'd suggest, wasting/undoing a non-trivial part of your effort. I'm aware of the issues last year whereby - if I may presume to word it - it seems you felt inter alia that your work was being wasted on mainstream blfs book; and so perhaps want to avoid getting back into that scenario. But, it doesn't have to be either _that_ or the present (wiki/notes) approach: I think that the suggest patches or similar structured (parseable/programmable) route be considered as a good intermediate option. >From here, it looks like you've more-or-less got a blfs-systemd book there. Why not publish it just like for lfs-systemd? rgds, akh p.s. For the avoidance of doubt: I still think sysd has, to say the least, serious issues. However, I really think it's not good for such work as what you've done above, to be shovelled into largely-unstructured notes/wiki that makes it awkward to work with in an automated fashion. > -- > Note: My last name is not Krejzi. > -- > -- -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
