[systemd-devel] Ordering for early initialization services

Umut Tezduyar umut at tezduyar.com
Fri Mar 8 05:12:56 PST 2013


What would be the advantage of placing an early boot up script in between
local-fs.target/sysinit.target OR in between sysinit.target/basic.target?

I cannot decide what should be the ordering for some early initialization
"oneshot" services I have in my embedded system. These services makes some
simple preparations that were previously in /rcS.d/. Dropped support for
/rcS.d/ in systemd was placing these services as After=sysinit.target and
WantedBy=sysinit.target (and I am not entirely sure but possibly
Before=basic.target). I could place them as systemd did before or I could
place them as After=local-fs.target and Before=sysinit.target.

Since my embedded system doesn't have login prompt, I don't see the
difference between basic.target and sysinit.target other than socket
activation. Even then, a service that is socket activated has
DefaultDependency=yes (It will start after basic.target).

To summarize, where are users encouraged to place their early boot up
initialization services (ex: setting up the bandwith on a NIC)?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20130308/cc019135/attachment.html>

More information about the systemd-devel mailing list