On Mon, 2013-02-11 at 23:50 +0100, Armin K. wrote: > On 02/11/2013 01:22 AM, Armin K. wrote: > > Not useful for systemd since it logs anything to journal. Still enable > > it by default on LFS. > > > > I guess we would want to use this for lfs/systemd branch, but we need > > some kind of new bootscripts package which will include init-functions > > (needed by all services in BLFS), ifup and ifdown programs as well as > > ifup/ifdown systemd service (maybe nscd service file, too). > > > > I'd appreciate if someone would respond to this part. Patch is attached > to the original message.
I'm somewhat surprised that systemd doesn't come with its own ifup/ifdown scripts, given how it should be controlling everything at startup. If a systemd unit requires a network interface to be up, how does systemd ensure that dependency is satisfied? It looks like https://wiki.archlinux.org/index.php/Systemd/Services#Static_Ethernet_network would work, and doesn't require an ifup/ifdown script. Not sure how you'd implement populating the routing table on top of that, but I've given that issue about 20 seconds of thought so far :-) There's some discussion on starting/stopping network interfaces with systemd at http://lists.freedesktop.org/archives/systemd-devel/2011-October/003585.html too. As you say, we'll probably need a fairly small package, containing at least init-functions, for compatibility purposes; or simply provide that file as a patch to the systemd package so that it's installed alongside it. If it turns out that we do in fact need things like ifup/ifdown, then we may as well put them all together in a small package though. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
