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

Michael Biebl biebl at debian.org
Sun Jul 17 22:12:12 BST 2016


Am 17.07.2016 um 23:05 schrieb Michael Biebl:
> Am 17.07.2016 um 22:12 schrieb Josh Triplett:
>> This change would break the mechanism that allowed switching between
>> init systems via init= (or the generated options in GRUB).  That makes
>> it more difficult for someone who needs to test sysvinit for whatever
>> reason.  (The reverse works fine: having sysvinit-core installed but
>> booting via systemd.)
> 
> Well, I don't think that we "break" that mechanism.
> 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.

That all said, if someone want's to keep the sysvinit package alive,
then speak up now. I'm happy to hand it over to someone else, as long as
that person is willing to take over the maintenance and actually fix the
current sysvinit package to do something useful beyond the actual jessie
transition.

Regards,
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/20160717/e5a9114b/attachment-0002.sig>


More information about the Pkg-systemd-maintainers mailing list