140
Is Systemd that bad afterall?
(sopuli.xyz)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 29 Jun 2023
140 points (94.9% liked)
Linux
48332 readers
569 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
Well, no, and that's the whole problem; Systemd removed choice, and it was designed to do so. That is why there is so much anger. It is bad software design, by design. It flies in the face of the core linux principles, all in the name of homogenising the linux ecosystem, and you know exactly which big corporations benefit from that.
The simple fact is: today, if I want to run a mainstream distro without Systemd, I cannot. Its cancerous tentacles run so deep that decoupling it from a mainstream distro, and keeping it decoupled, is a full time job.
Instead I have no choice but to run a smaller, less featured, less secure and less funded alternative.
Full credit to Devuan, MxLinux, Artix, and the other united underdogs.
Fuck you Redhat/IBM and your proxy evil-doer Lennart.
Lets be perfectly honest. The reason systemd is so popular is because the init script based predecessors were so bad in so many ways. Not only did you have to reimplement the same things over and over in every script, the behaviour of your script also depended on environment variables in your environment while you started a service and other things that leaked into the script.
Would an init system have to do as much as systemd does to fix those issues? No. Are the existing alternatives really, really bad? Yes.