not-systemd status in Bullseye?

[Axel Beckert]

Hi,

On Tue, Mar 10, 2020 at 08:42:57PM +0000, Matthew Vernon wrote:
> Is the expectation that sysvinit will plausibly work in Bullseye? I see
> elogind and libpam-elogind are in bullseye, but libpam-elogind-compat is
> still only in experimental.

I have many sid installations running sysvinit or openrc. No
critical issues there. Occasionally broken init scripts of some
non-critical daemons.

> I have a fresh bullseye system that has systemd on (because no option in the
> installer), which runs fvwm and lightdm, but I'm not sure how likely a move
> to sysvinit is to work - AFAICS, systemd prerm will refuse to run if systemd
> is init, making switching hard...

That's already the case in buster and never was an issue for me:

* Replace systemd-sysv with sysvinit-core (or openrc).
* Reboot (with systemd still running as init system).
* Booting will happen with init system of your choice.
* Purge systemd after reboot.

Works as a charm for me upon every installation in the past two years
or so. No new Sid or Bullseye installation recently, but I don't
expect that much changed at that point.

> I think it'd be worth asking the installer folk to add an init system choice
> (even if only in expert mode);

Definitely.

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe at debian.org>, https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE