Comment on [deleted]

• lambalicious@lemmy.sdf.org ⁨13⁩ ⁨hours⁩ ago

  Because it was not always the case that sysvinit was supported - things were sorta “accidentally hazy” for a while. There was a time (I think during Debian 9 and 10) that systemd not only was the default, but was also enforcedly linked against a large part of the stack (you couldn’t have a desktop environment, PulseAudio or NetworkManager without systemd, for example).

  This led to the rise of projects like Devuan, that provide a working system that installs without systemd by default; Antix’s nosystemd repo, which allows to install components of the Debian stack without the enforced systemd dependency; and later libam-elogind-compat which aided shimming some of systemd’s requirements under elogind.

  Nowadays at least, the only hard part of not using systemd in Debian is 1.- switching (from or to) seems to require rescue mode and 2.- you lose some of the container management goodies (for eg.: Podman services).

  source

  • communism@lemmy.ml ⁨11⁩ ⁨hours⁩ ago

    I see, that’s interesting. Well glad that it’s not hard to switch away from systemd on Debian for those who want it—although I still think if you don’t want systemd you should just pick another distro, given that the Debian installer doesn’t let you pick another init.

    source