On 06/15/2014 05:22 AM, Armin K. wrote:
On 15.6.2014 2:44, DJ Lucas wrote:

Done. LFS-systemd is caught up with LFS-svn. Booted it up, just as it is
now, using jhalfs to complete.

A couple of suggestions:

1. Disable systemd-networkd.service and systemd-resolved.service by
default. This can be done by removing the symlinks after systemd is
installed:
rm -fv
/etc/systemd/system/multi-user.target.wants/systemd-{resolved,networkd}.service

rm -fv
/etc/systemd/system/network-online.target.wants/systemd-networkd-wait-online.service


Yeah, those would need to be disabled by default. We can add a couple of systemctl disable commands if necessary.

Yeah, wasn't sure if it'd work in chroot or not. It appears to though.

Also need to comment out lines 19-21 of /usr/lib/tmpfiles.d/systemd.conf
as a result of the above, and probably remove the run lines from there
too...but those aren't so important, just cosmetic.


These are just directories and get populated if networkd is running. In later version we'd need more systemd users. I've reserved uid's/gid's for all 5 of them in BLFS.

Cool, cool, then you are on top of it.
2. Enable tty{2,3,4,5,6}:
for tty in 2 3 4 5 6; do
     ln -s "/lib/systemd/system/[email protected]" \
"/etc/systemd/system/getty.target.wants/getty@tty$tty.service"
done


I don't think this is necessary at all. tty1 is always enabled and other ttys will get auto spawned once switched to them. No need for all 6 to be enabled all the time.

You are correct. Only tty1 needs enabled, logind handles the rest. I had assumed that they were always enabled before. I'm not sure why the generator didn't work at first (on two builds no less), but after disabling them, and rebooting, it is working correctly. :-/ I observed that if getty@tty1 is disabled, the auto-generator works for only 2-6 and doesn't switch to tty2 automatically (but you can switch it manually, login fine and fix a dumb mistake ;-) )

--DJ

--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to