Re: default init on non-Linux platforms
On Tue, 18 Feb 2014, Russ Allbery wrote:
> Henrique de Moraes Holschuh <email@example.com> writes:
> > They *HAVE* to be provided by the active init system. They are an
> > impedance matching layer (aka stable API) used by maintainer scripts to
> > interface with the active init system.
> If you look at the existing implementation, you'll find that the version
> provided by sysv-rc already supports systemd, upstart, and sysv-rc itself.
> So this isn't precisely true. If we stick with the current model, then
> some (probably essential) package just needs to provide those
Hmm, we can provide one, yes. Probably in sysvinit-utils, which already has
some important tools that are not strictly related to sysvinit itself.
> There are some advantages to providing only one version with knowledge of
> all of the init systems given that we're supporting init system switching,
> and therefore may need to set up state for init systems that aren't
> currently running so that switching can work properly. A good example is
> registering an init script with insserv so that the correct S and K links
> are created even if the system is currently booted with a different init
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot