My favorite is Debian, with systemd uninstalled. At this point, you can’t install Debian without systemd, but you can uninstall systemd after OS installation.
It used to be that most desktop environments in Debian depended on libpam-systemd, which depended on systemd and systemd-sysv. More recently, desktop environments just depend on libpam-elogind and elogind which is only part of systemd, and allows you to use sysvinit.
I prefer sysvinit mainly because I find it easier to create custom services out of my own programs. My success rate at doing this in systemd is 1/3, and in sysvinit about 10/10.
I also had a problem where a Debian-based embedded system had some kind of broken NTP client running on startup, and due to systemd, I couldn’t figure out how to disable it. It would set the time to several years into the future, as soon as it first got a network connection on each startup.
After having a lot of sysvinit experience, the transition to setting up my own systemd services has been brutal. What finally clicked for me was that I had this habit of building mini-services based on shellscripts; and systemd goes out of its way to deliberately break those: it wants a single stable process to monitor; and if it sniffs out that you are doing some sketchy things that forks in ways it disapproves of, it is going to shut the whole thing down.
My favorite is Debian, with systemd uninstalled. At this point, you can’t install Debian without systemd, but you can uninstall systemd after OS installation.
It used to be that most desktop environments in Debian depended on libpam-systemd, which depended on systemd and systemd-sysv. More recently, desktop environments just depend on libpam-elogind and elogind which is only part of systemd, and allows you to use sysvinit.
I prefer sysvinit mainly because I find it easier to create custom services out of my own programs. My success rate at doing this in systemd is 1/3, and in sysvinit about 10/10.
I also had a problem where a Debian-based embedded system had some kind of broken NTP client running on startup, and due to systemd, I couldn’t figure out how to disable it. It would set the time to several years into the future, as soon as it first got a network connection on each startup.
Devuan is doing the Lords work
Sorry if it wasn’t obvious, I’m using sysvinit.
It was obvious, don’t worry.
I just thought of the joke, and thought it was funny.
After having a lot of sysvinit experience, the transition to setting up my own systemd services has been brutal. What finally clicked for me was that I had this habit of building mini-services based on shellscripts; and systemd goes out of its way to deliberately break those: it wants a single stable process to monitor; and if it sniffs out that you are doing some sketchy things that forks in ways it disapproves of, it is going to shut the whole thing down.