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
Sun Aug 11 16:51:06 BST 2019


Thanks for this.

I was aware of this in the sense that I know systemd can't be uninstalled whilst
it is PID 1. Most recently this was discussed in #930105 and tagged wontfix.

The only way I have managed to migrate systems reasonably cleanly is to boot
with init=/bin/sh, replace systemd with whatever else and then reboot again. But
as you point out, that is not the obvious migration route that a normal sysadmin
might take.

The problem is that the route recommended in #930105 (et al.) is to first
install sysvinit-core, reboot and then remove systemd. The first step of this
will require removal of almost the entire GUI environment -- something few would
persist with even though it could all be reinstalled later.

On Sun, Aug 11, 2019 at 03:31:00PM +0100, Simon McVittie wrote:
> Possible solutions:
> (I don't know which of these would be helpful, I'm just speculating...)

These are useful, thank you. I will experiment and see.


More information about the Debian-init-diversity mailing list