[systemd-devel] Ordering for early initialization services
umut at tezduyar.com
Tue Mar 19 01:30:19 PDT 2013
I would like to bring my discussion back. Any help?
On Fri, Mar 8, 2013 at 2:12 PM, Umut Tezduyar <umut at tezduyar.com> wrote:
> 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...
More information about the systemd-devel