Bug#934491: libelogind0: failing to switch from systemd to sysvinit-core/elogind results in libsystemd.so.0 disappearing

Mark Hindley mark at hindley.org.uk
Thu Aug 15 10:42:19 BST 2019

On Tue, Aug 13, 2019 at 04:46:32PM +0200, Thorsten Glaser wrote:
> But TTBOMK it is possible to install sysvinit alongside systemd,
> then reboot and select sysvinit as “alternative” init from the
> GRUB menu, then remove everything else. Now that I see /sbin/init
> is part of sysvinit-core, I wonder if this is really possible any
> more and, if not, why not… packages are not supposed to depend on
> systemd-sysv… (but, ouch, libpam-systemd does).

Can you point me to any official documentation that says packages should not
depend on systemd-sysv?



More information about the Debian-init-diversity mailing list