Ken Moffat wrote: > On Thu, Apr 03, 2014 at 05:11:10PM -0500, Bruce Dubbs wrote: >> I've committed a major change to the -dev version of LFS. >> >> The new version installs systemd and System V side-by-side with the >> ability to reconfigure and come up in the other system. >> > > I'm sorry to see eudev disappear from the book after its brief > appearance, but more power to your elbow for providing the two > alternative init systems. > > I'm now sufficiently interested by this to try a _minimal_ build > (i.e. LFS and not much else - many of the things I normally build > before rebooting have their own local bootscripts, which will > probably give me pain in systemd), and then try running that > [expletive deleted :-o ] init variant.
To try a minimal build, try using jhalfs. Without the tests, it takes about 65 SBU on my system at 121 minutes/sbu. That's using -j1. > But first, I'm still in the middle of various non-LFS-related > things, together with some BLFS tickets. I've now completed a build > of my normal desktop on svn-20140331 with the following : linux-3.14, > gmp-6.0.0a, tzdata-2014b, file-5.18, flex-2.5.39 with lex as a > symlink following Armin's suggestion, libpipeline-1.3.0. If it > assists, I can pick up any of those tickets. I can do those easily enough. I want to let the current changes settle for a couple of days though. > Meantime, two brief comments - > >> The scripts to reconfigure are in /usr/local/sbin and are named >> set-systemd and set-sysv. I recommend re-reading Chapter 7 as there are >> a lot of changes there. > > Why /usr/local ? They will be an intrinsic part of LFS if this all > works out. Some of us occasionally try things in /usr/local, and > then wipe it all out. [ Well, I do ;-) ]. /usr/sbin just didn't feel right to me, but it would be easy enough to change. > [...] >> >> I'm sure there are still latent bugs in the current commit, whether they >> be in scripts, build instructions, or text. Please test this out and >> let me know of needed changes. > > Section 7.3.3 (configuring the network with systemd) - I think > there is missing whitespace in front of '@' in each of the three > commands in this section. At the moment they each say > ifupdown@eth0 ? No, the page is correct. There is a learning curve with systemd, and I can't say I've gotten very far yet. Note that the three lines are informative: enable, disable, and start. The actual file that is called is /lib/systemd/system/ifupdown@.service, so the part after the @ is the device. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
