[Pkg-sysvinit-devel] Where do /lib/init/init-d-script belong?

Petter Reinholdtsen pere at hungry.com
Wed Feb 5 11:55:21 UTC 2014

> Are they really independent of boot system? I don't think systemd or
> upstart will use such scripts. In this sense, /etc/init.d/script and
> /lib/init/init-d-script have the same portability.

It depend on what you mean by boot system, but I would say yes.  Both
upstart and systemd handle packages with init.d scripts, and openrc
and file-rc can be used instead of sysv-rc to execute them with
sysvinit.  So this is a tool for package maintainers to make it easier
to provide a init.d script in their package, and the will of the
systemd and upstart maintainers is not really relevant here.

> IMHO, they goes into initscripts. That avoids an extra dependence
> (initscripts -> sysvinit-utils).

This definitely make some sense, but most of initscripts are parts
that I suspect upstart and systemd will want to replace, as their
behaviour is quite tied to how sysvinit work.  Just look at how much
of initscripts ubuntu changed for upstart, moving the early boot
initialization to tasks tuned to how upstart work.

While sysvinit-utils contain tools useful for any boot system
(fstab-decode, killall5, last, lastb, mesg, pidof, service, startpar
and sulogin), and the init-d-script code is more a tool for packages
writing init.d scripts than it is a integrated part of the boot

Happy hacking
Petter Reinholdtsen

More information about the Pkg-sysvinit-devel mailing list