I still haven’t decided what to do about systemd. It seems to be working here and Debian GNU/Linux is inching towards its next release with systemd as default init.“Systemd thus appears to be a massive, fundamental change to core Linux administration for no perceivable gain. This is what is meant when people say that systemd was an answer to a question nobody asked.” TFA, linked below, identifies two or more solitudes fighting over systemd. It identifies desktop and server users as two camps who want/don’t want systemd to run their lives.
I’m kind of straddling the fence… I run multiple PCs and servers and did just fine without systemd and I only tolerate systemd because it hasn’t completely broken my systems. It seems to me that Debian is dangerously close to breaking my systems by even considering that all kinds of stuff could be made to depend on systemd. That’s just not the Debian I know… Why is this even up for discussion?
In case anyone needs reminding, this is from the Debian Social Contract:
“We will be guided by the needs of our users and the free software community. We will place their interests first in our priorities. We will support the needs of our users for operation in many different kinds of computing environments.”
Making all kinds of stuff depend on systemd doesn’t sound like what users need/want. The whole idea of dependencies in APT is making it easy to build systems. If you don’t want systemd and GNOME depends on it, that’s going to be hard. My system doesn’t depend on GNOME but I have a few applications that have a few libraries that do. Even before systemd there were a few applications I did not install because they sucked in half the GNOME repository. Having applications tightly integrated into the underlying OS is a recipe for disaster and the original reason I chose GNU/Linux fifteen years ago. We should be looking forwards not backwards. Why repeat the mistakes that M$ made?