Bug#746577: closed by Michael Biebl <biebl at debian.org> (Re: Bug#746577: systemd-sysv: for upgrade safety, systemd-sysv and sysvinit-core must be coinstallable)

[Tollef Fog Heen]

]] Zack Weinberg 

> On Mon, May 5, 2014 at 5:40 PM, Tollef Fog Heen <tfheen at err.no> wrote:
> > ]] Zack Weinberg
> >> Fundamentally what I want is a bulletproof procedure for reverting to
> >> sysvinit in case something goes wrong.
> >
> > Sounds like you're arguing that sysvinit-core should no longer ship
> > /sbin/init, then, so systemd-sysv doesn't have to conflict with it.
> 
> Wouldn't that make the sysvinit implementation of /sbin/init
> completely unavailable?  This is an earnest question.  I do not have
> access to package contents right now.

No, to revert you'd boot with init=/sbin/sysvinit.

> Note that coinstallability is not enough -- the bulletproof procedure
> (e.g. "update-init-system") must also be implemented, shipped, and
> documented.

I have still not seen any reason whatsoever for this to be a command
rather than just changing a configuration file.

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are