On Sat, Feb 1, 2014 at 8:36 PM, Chris Knadle <chris.kna...@coredump.us>wrote:

> On Saturday, February 01, 2014 19:14:21 Cameron Norman wrote:
> > On Sat, Feb 1, 2014 at 6:35 PM, Russ Allbery <r...@debian.org> wrote:
> > > I *like* systemd, and I would still be very unhappy
> > > if a routine aptitude upgrade (or even a dist-upgrade) of a system
> > > currently running sysvinit suddenly resulted in running systemd without
> > > some sort of critical debconf question or the like.
> >
> > In my mind, the package to change init systems would still be separate
> from
> > its respective init systems.
>
> There's a work-in-progress tool starting to implement this, it currently
> works
> for switching between sysvinit and systemd, and will work with others later
> (assuming the package interdependencies can be worked out).
>
>
This is not really what I was interested in. I want a package for each init
system (init-systemd, init-upstart, etc.) that uses something like
init-select (under the hood) to prompt the user to change the init system.
This will allow packages to depend on a certain init being pid 1, which is
essential seeing as the current TC members seem to be leaning towards
allowing tight coupling.

--
Cameron Norman

Reply via email to