[Pkg-sysvinit-devel] Bug#826205: Please move /lib/init/{vars.sh, init-d-script} to sysv-rc

[Petter Reinholdtsen]

No objections from my part, as I do not have all the required details in
my head any more, just want to clear up something that look like
misunderstandings.

[Martin Pitt]
> Some of its dependency should also  move, e. g. startpar is only
> needed for initscripts [4]. Ideally insserv could be moved to
> initscripts as well, but I haven't done research yet whether that
> would still be "necessary infrastructure to keep SysV init scripts
> working" (I have a hunch that this is the case, as something needs to
> create /etc/rc?.d/ links for packages that only have SysV init
> scripts, under any init system).

'startpar' is not really needed for scripts in the initscripts package.
'startpar' is an implementation detail behind the code in /etc/init.d/rc
and /etc/init.d/rcS which belong to the sysv-rc package.  The
implementation detail is to run the init.d scripts in parallell using
the dependency information stored in /etc/init.d/.depend.* (generated by
insserv).

And 'insserv' is not really needed for the initscripts scripts either.
It is the internal implementation for the sysv-rc way of starting init.d
scripts called by /usr/sbin/update-rc.d from the init-system-helpers
package.

So update-rc.d require insserv when /etc/init.d/rc from sysv-rc is used,
and /etc/init.d/rc require startpar to run scripts in parallell.

Do your proposal still make sense when those details are the way they
are?  I'm not sure using the initscripts package as a resting place for
things that is no longer needed with systemd is a good idea.  After all,
the initscripts scripts work just fine with file-rc and no parallel
boot, and in that use case startpar isn't used.

The key platforms in Debian using sysvinit/initscripts/sysv-rc these
days are Hurd and kFreeBSD.  Perhaps someone from those platforms should
test the new proposal to ensure it do not break their installation and
boot?

-- 
Happy hacking
Petter Reinholdtsen