Le 22/12/2013 18:17, Armin K. a écrit : > On 12/22/2013 04:59 PM, Pierre Labastie wrote: >> Hi, >> >> I think jhalfs is now usable for building the systemd branch of LFS. Be >> careful that the configuration files indicated at the end of the build are >> for >> LFS trunk, and that they are different for systemd. >> >> I have a question for systemd gurus: when you use "systemctl enable" does is >> do more than linking the right files to the configuration dir? >> >> If not, why not use ln -s commands in chapter 7 instead? >> >> Regards >> Pierre >> > > Because it's the systemd way. It might create more than one link in more > than one (sub)directory of /etc/systemd/system. > Sorry I am answering so late, and this thread has been going to several directions... Interesting though.
My point was this (posted by Armin on trac): "Do note that *ctl commands should not be run during the build process since they require systemd, dbus and required components to be running when *ctl commands are used." So there is some kind of circular dependency here (or maybe I am out of my depth): - you cannot use systemctl for setting the configuration files while in chroot, unless your build host is already running systemd. - you need working configuration files to be able to boot LFS systemd That's why I thought ln -s could be used while in chroot to at least set the most basic configuration files. BTW, thanks to Armin for adding role="nodump" attributes. That is what allows jhalfs to work with systemd. Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
