On Tue, 10.06.14 22:16, Michael Biebl ([email protected]) wrote: > > 2014-06-10 19:44 GMT+02:00 Lennart Poettering <[email protected]>: > > I figure we don't really need network-pre.target, as units that want to > > run before the network is up should just use: > > > > Before=systemd-networkd.service basic.target > > > > THis is enough since network management services like > > NM are normal services, and networkd is the exception in being available > > from earliest boot on, including in the initrd. This means, that any > > firewall service that wants to cover this must be a early-boot service > > (i.e. DefaultDependencies=no), and thus ordering itself before networkd > > and basic.target should suffice... > > > > If one day there's another network management solution that is capable > > of running this early during boot, then we can revisit this, but > > otherwise, the ordering mentioned above should be above, and generic > > enough since it requires no explicit mentioning of units we wouldn't > > ship with systemd anyway. > > Debian's ifupdown does run during early boot, i.e. in sysinit.target.
Hmm.. OK. OK. I added this now, with a different patch, and made it a passive unit as discussed. I have also changed systemd-networkd to make use of it properly. Somebody should update the other network management services too like this i figure... I have also updated http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ to describe the entire new behaviour we have now in place. It would be great if somebody could proof-read that (and fix typos immediately, though I mostly interested in technical feedback). Hope this settles this topic! Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
