54
systemd really, really sucks
(ser1.net)
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 27 Oct 2026
54 points (69.9% liked)
Linux
68414 readers
514 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 7 years ago
MODERATORS
While I get the sentiment, isn't the fact that systemd is broken into various components and you can use or choose not to use each part of it still within the unix philosophy? You can use the init system without using the rest. It just integrates well with the other components.
That argument is addressed in the article. With few practical exceptions, systemd components expect you to be running the other systemd services. E.g. running systemd without journald is not a supported usecase.
Not supported doesn't mean it won't work
Fair enough, but there's a reason no one runs almost any of the systemd services in isolation. There's a big difference between "takes a bit of tinkering" and "need to maintain massive patch files to make journald independent of systemd"
Yeah that's fair. I will say that I've used distro's that used systemd and journald, but not resolved, networkd, etc and it worked fine.