sysvinit should depend on initscripts for a functional /lib/sysvinit/init

[Michael Biebl]

Am 18.07.2016 um 00:07 schrieb Josh Triplett:
> On Sun, Jul 17, 2016 at 11:30:26PM +0200, Michael Biebl wrote:
>> Am 17.07.2016 um 23:17 schrieb Josh Triplett:
>>> On Sun, Jul 17, 2016 at 11:05:09PM +0200, Michael Biebl wrote:
>>>> If you have systemd-sysv installed and you want to try sysvinit-core,
>>>> you install the package and you get a fallback grub menu entry for
>>>> systemd (unless you also purge the systemd package). So it is still
>>>> easily possible to switch between the two init systems.
>>>
>>> Only by having sysvinit installed as the default init system.
>>> Previously, it was possible to have systemd as the default (matching the
>>> Debian default) but still use sysvinit.  Now, it seems like sysvinit
>>> will become the only init system in Debian that *can't* boot without
>>> being the default.
>>
>> Which other init systems do you have in mind which would allow that?
> 
> systemd.  upstart, until it was removed.

No, upstart was not co-installable in Debian.

>  runit. 

runit doesn't provide /sbin/init, so is not comparable to
systemd/systemd-sysv or sysvinit-core

 openrc (which can't
> coexist with sysvinit because it replaces sysv-rc, but which doesn't
> have to be the default unless sysvinit does).

openrc and sysv-rc are no init systems.

Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20160718/6974050c/attachment-0002.sig>