No Systemd

#1

Post by standeven » Tue, Jun 30, 2026, 3:35 PM UTC

Re: No Systemd

#2

Post by sph » Tue, Jun 30, 2026, 5:04 PM UTC

The effort of dealing with the increasing amount of software that expects systemd to run underneath makes all these initiatives not very worth it unless you buy heavily in the political, rather than technicals reasons, of avoiding systemd.

I don’t care. I have run Linux machines since 2001 and systemd is one of the least offensive reinvention of the wheel I have had to deal with. All software is shit one way or another, all that matters is how much effort do I have to spend to find myself dealing with another, unsupported pile of shit.

Re: No Systemd

#3

Post by Suzuran » Tue, Jun 30, 2026, 5:10 PM UTC

"Bait used to be believable."

Re: No Systemd

#4

Post by vekntksijdhric » Tue, Jun 30, 2026, 5:12 PM UTC

showing a list of bugs and vulnerabilities is not a compelling case against systemd, or it is a compelling case agains every single piece of software.... providing an argument *why* systemd is bad is what I expect

Re: No Systemd

#5

Post by vivzkestrel » Tue, Jun 30, 2026, 5:35 PM UTC

- every software has bugs, even curl does, does that mean you ll start a new website called nocurl.org?

Re: No Systemd

#6

Post by paulddraper » Tue, Jun 30, 2026, 5:38 PM UTC

That's a shockingly light list of bugs.

Guaranteed that the replacements would have a combined list at least as bad.

Re: No Systemd

#7

Post by pknomad » Tue, Jun 30, 2026, 5:50 PM UTC

Every time I see no systemd - I remind myself of this post: https://www.reddit.com/r/archlinux/comments/4lzxs3/why_did_a...

> What most systemd critics consider "bloat", I consider necessary complexity to solve a complex problem generically.

Re: No Systemd

#8

Post by Glandalf » Tue, Jun 30, 2026, 6:04 PM UTC

systemd will never be done, it’s a scam designed to make Linux UN maintainable and incompatible and force businesses to buy service contracts from IBM.

Re: No Systemd

#9

Post by foxrider » Tue, Jun 30, 2026, 6:12 PM UTC

I swear, the more time goes on, the more I disrespect the "no to systemd crowd", not because they don't have valid arguments, but because in recent years it attracted a very *specific* kind of audience, and now it smells bad.

I've used Linux for over 20 years at this point, my first Linux computer was a PS2 console and my second one was a PS3 console. I remember the rc scripts and upstart, and I hated dealing with any of it, systemd, its timers and the user units were the most convinient change in decades. I hear so many anecdotal accounts of "sytemd destroying someone's system", yet personally it was nothing but a pleasant experience.

I think there's always needs to be an alternative, and I welcome anyone who's actually building alternative code paths and doing the work to create the alternative tools, but every time some tool gains a dependency on systemd to improve the functionality and the mob comes in complaining I can't help but get angry. It's open source. You can patch it. You can switch to something else, but instead you hurl insults at people volunteering their time to make software you run better.

Re: No Systemd

#10

Post by branon » Tue, Jun 30, 2026, 6:26 PM UTC

There was probably a case to be made for this stance when systemd was very new and getting shoehorned everywhere but increasingly I don't see the point

I think the issue people took with it was less on technical merit and more about the principle of resisting a change which was occurring too quickly for comfort

it was kneejerk reactionary to begin with and hasn't made any more sense as systemd has improved and received better integration with other software

I do mourn the loss of Upstart though, I thought that was one of Canonical's cooler projects

I also use Void/runit primarily and enjoy it because of its simplicity, it's a nice _exercise_ to run systemd-free but I don't pretend it comes anywhere near the level of capability that systemd provides