systemd

“Systemd is, legitimately, well divided. Most of the complaints against systemd are from people who know basically nothing about systemd.”

“the architecture is sound and relatively straightforward given the inherent complexity in managing a diversity of system processes”

“systemd makes it so so easy, and integrates many many different mechanisms and systems for locking down what procesess can do”

“It's a piece of software designed to turn all distros into Red Hat, and then sell consulting services to manage the untameable complexity.”

“SystemD is not "building blocks" — which implies modularity — it is a monolith: components cannot be added or taken away or replaced.”

“With systemd, core updates can affect PID 1, logind, journald, udev, user managers, socket activation and cgroup state as one dependency graph.”

“The problem with systemd is not the init system. Most people who do not like systemd are happy with the init system, but do not want the rest of it.”

“systemd is awfully documented (volume is not quality), things are still changing and haven't even caught up in functionality with any init hack.”

“Systemd is not 1 giant thing that does 100000 things - it is a collection or 10000 services doing 10000 things, integrating amongst themselves where practical.”

“With systemd that all becomes explicit, so of course it is awkwardly verbose. That is the whole point and a huge upgrade.”

“Unix and BSD are developed even moreso in the same way - the init system is sitting in the same repo as the libc, the kernel, and the entire rest of the OS.”

“...and then keep up with behavioral changes that the Systemd Project people introduce and load-bearing bugs that services end up relying on for lifecycle management.”

“there are times systemd has a critical bug; sure the same way x11, kernel modules or drivers have critical bugs are annoying”

“I am not the greatest fan of most of systemd's features. I will always prefer it tho since I just view it as a "packaging format".”

“Using systemd, and building on top of it makes it much easier to implement features without having to do everything yourself.”

“The whole point of systemd is to use Linux kernel features like cgroups to the fullest extent, and it does so to great effect.”

“While I think systemd is a great init system (as well as some other components under the systemd umbrella), I really dislike when components up in the stack hard-depend on it.”

“A lot of the things make image based systems more modifiable/user accessible without compromising on the general security aspect.”

“I wish I wasn't running systemd. ... the service manager works well enough that most distros have accepted the downsides.”

“It's still up to the distro, so I think this is fine. This gives distros an easy way to comply and lets other distros nope out of it.”

“They just dare to be successful by tackling problems that people have today over trying to deliver solutions designed in 1989.”

“I've heard from many sysadmins and distribution maintainers that systemd has been amazing. We went from ad hoc shell scripts to declarative plain text files.”

“The whole philosophy of systemd is to move away from these kinds of "simple" and "mostly working" pile-of-shell-script systems”

“All other components under the systemd project are optional and not required, nor is there any push to make them required.”

“systemd solves actual problems and gets shit done, with a level of consistency that cannot be achieved by LEGO-like wet-dreams of UNIX worshippers”

“systemd's chosen heuristic is pretty reasonable - match against a list of filesystem types that probably require network connectivity.”

“They've built various components to help with that, including writing specifications (via the UAPI group) on how that should all fit together.”

“systemd also took a relatively non-unixy approach, where it's a big stack to adopt, rather than individual programs that work together well”

“many options that are complicated beyond the understanding of the distro maintainers, and yet still don't allow expression of common semantics”

“SystemD has a lot more people refining it down but a clean (under the hood) implementation probably won't be witnessed in my lifetime”

“systemd and friends go around absorbing other projects by (poorly) implementing a replacement and then convincing the official project to give up.”

“I find systemd pleasant for scheduling and running services but enraging in how much it has taken over every other thing in an IMO subpar way.”

“systemd doing dumb shit device naming so that changing the physical location of an unrelated GPU renames your NIC and breaks your internet”

“instead it's one guy that just did what he wanted and shared it with the world, and enough other people liked it and started building upon it.”

“Why the fuck does systemd lock up the entire startup process for 2 minutes if you start a desktop machine without network connectivity?”

“SystemD as init replacement is "fine"; SystemD as kitchen-sink-of-the-server-with-everything-tightly-coupled can get annoying.”

“systemd is 69 different binaries (only one of which runs as pid 1), all developed under the same project, designed to work together”

“I've been using systemd based distros since around ~2012, and while I've had many issues with Linux in that time, I can't really say that any of them were caused by systemd.”

“if you complain about these bugs to the systemd project, they will consider you a bump in systemd's way of greatness that must be purged”

“The hardening options highly restrict the unit files from accessing anything more than it's required for it's function.”