![Pottering: No SSH for you! [1080x1761 - 226KB]](https://pic8.co/sh/yV6GzF.jpg){kind=link}
Systemd is the biggest piece of shit to ever be allowed into linux and it's destroying linux. Did you know systemD breaks vpn split tunneling with the resolved,networkd,network mangler,dns mask demon spawn they kludged together. Good luck ever trying to find the right place to config anything about the network.
Yes, systemd is a total piece of shit. It is easy to identify idiot system admins simplly by their happiness with systemd.
I have zero doubt there are multiple NSA CIA backdoors built into it. As far as I'm concerned, backdoors are the only reason systemd exists.
Every distro has decided they are primarily a workstation OS maybe system d has a place if your trying to make linux like windows but on a server deployment i do not want any of the garbage it has to offer. I want concise static config that doesn't get changed by 50 different init processes. Init scripts for servers was 1000x better. Ontop of that almost all of my use case is running docker containers. I don't deploy or start anything on the hosts but network and the oci container layer so i basically dont need an init manager for anything as the orchestration layer manages containers.
Everything systemd does could have been done better, while avoiding the monolithic model of systemd. Work station of not, no need for systemd implementation or model has ever existed.
Redhat got cozy with DoD with big contracts. Suddenly systemd was the rage everywhere over most everyone's objections.
(post is archived)