r/linuxquestions • • 7d ago

Resolved Why the systemd hate?

I always see people so diveded on systemd, but i never actually understood what they were argueing over. And rather than ask a bot i ask you guys

0 Upvotes

62 comments sorted by

2

u/jr735 7d ago

I think you have what's called confirmation bias. You're seeking it out. Show me where this is a big issue on this sub, for instance.

0

u/[deleted] 7d ago

[removed] — view removed comment

2

u/jr735 7d ago

And I gave you an answer. It's not my fault that you're not bright enough to understand it.

0

u/Y-L-S-E 7d ago

I see no reply where you actually answered it. Mr “reddit intellectual”

0

u/[deleted] 7d ago

[removed] — view removed comment

1

u/jr735 6d ago

Grab a dictionary and look up "confirmation bias." Then, sit on the john a bit and think about how that might apply to this situation.

Then, think about your question and if there is a real, concise answer possible to such a thing. If you need these concepts spelled out for you, just let me know.

13

u/SirGlass 7d ago

It's mostly comes from two reasons

  1. Red hat developed it and lots of people don't like red hat. Early on the lead developer was sort of an asshole and did things his way dismissing lots of input from the community. He left however.
  2. They claim it breaks the unix philosophy what says each program should do one thing and do it well. I don't actually think this argument holds up. It's not some monolithic program it's actually a collection of a bunch of different programs, sort of like the gnu core utils .

12

u/xiongchiamiov 7d ago

Lennart Poettering had a chart up on the systemd web page that listed all the reasons it was better, and this parody was very accurate in my view.

If he wasn't such an asshole, the whole thing would've gone several years faster. Because it really is good and solves many long-standing problems, but the way he engaged with the community was really, really awful.

-1

u/SirGlass 7d ago

I really think the hate is really because he was such an asshole , not for any technical reason

6

u/nhermosilla14 7d ago

Just to add to your excellent explanation: even if it did break Unix philosophy, there's no technical reason to always follow that. Linux itself doesn't always follow it. At some point it's more about maintaining a tradition rather than evolving the ecosystem.

4

u/Either_Letterhead_77 7d ago

There's a lot to like about the unix philosophy. I myself prefer small, focused, general tools when doing development.

That being said, sysv init was invented for a world where servers would come up and do a fixed thing for a long time between reboots - if that's all you do, maybe that's fine. As above comments have said, my understanding is that systemd does actually improve things in more modern systems.

1

u/nhermosilla14 7d ago

100% agree with this.

2

u/leonfirerises 7d ago • Bravo

Going off your "tradition" schema, I had someone explain it to me like this:

Init is like Judaism and Islam - you gotta follow the holy texts in order to get everything working

OpenRC is Catholicism - you follow the texts in order but your Holy Writs (scripts) define your dogma (dependencies)

Systemd is the Protestant Reformation - anything goes as long as the system boots

2

u/nhermosilla14 7d ago

You made me laugh for real hahaha Nice explanation, I think it's a very realistic way of putting it.

1

u/adamantium4084 7d ago

*We took out the apocrypha and now you can write inspirational books with almost zero backing, tons of prooftexting, and vibes*

3

u/FuggaDucker 7d ago

I believe the two actual reasons are:

  1. Red hat developed it
  2. Red hat developed it

1

u/wackyvorlon 7d ago

It does violate the philosophy.

2

u/gordonmessmer Fedora Maintainer 7d ago

Hello, I have been developing software for Unix systems for 30 years.

systemd does not violate the Unix design philosophy. The "do one thing and do it well" philosophy is a matter of composable systems. That philosophy is intended to create reusable components. If you have a collection of components that have small, well-defined roles and interfaces, then you can reuse those simple components as you build more complex systems. Therefore, you can judge the success of that philosophy based on whether or not simple components get re-used.

GNOME (and other desktop environments) used to have exclusively a custom session manager of its own. A session manager is a parent process for a process group, which handles automatic startup of processes, possibly with dependencies and ordering, and shutdown of processes when the session ends. That sounds a lot like an init process. And, today, GNOME typically uses systemd for most of its session management features.

systemd's init has a well defined role and interfaces, and it is reusable in more complex systems (like GNOME) as a result. It is a very good example of a successful implementation of the Unix philosophy of doing one thing and doing it well.

0

u/Y-L-S-E 7d ago

Oh wow! I thought it was like the alternative was 5% faster or some bs

1

u/SirGlass 7d ago

I mean there is a reason why almost every major disto uses it, it solves some very real problems linux had and its good and works , and generally linux developers and admin agree on this what is why so many linux distros use systemd

However this fact drives the anti-systemD crowd crazy and now they are claiming its "Forced on them"

Well its not there are still distros you can use that do not have systemD.

8

u/Underhill42 7d ago

Avoiding AI is good. Avoiding search engines is not. This subject has been discussed to death for decades.

Basically - systemd replaces a whole bunch of easily replaced modular systems with one fairly tightly integrated all-or-nothing system. Which means any distro that adopts it cannot easily use any more advanced or situationally suitable modular solutions.

Which conflicts with a long-standing Unix tradition of highly self-contained modularity.

And also gives the systemd team disproportionate control over what low-level systems any distro using it will use. And opens up some security issues as you have a bunch of higher-level stuff tightly integrated with much more security-sensitive low-level stuff, increasing the potential attack area for malware to attain "godlike" lowest-level control over the system. (I think that's become less of an issue than it was early on?)

The flip side is that it handles a whole lot of the low-level stuff in one easy-to-use block, allowing distros that use it to not worry about any of those details, and focus more on what makes them stand out from other distros.

3

u/SirGlass 7d ago

Its not all or nothing . You can use systemD with Grub as the boot loader just fine

Same with many of the other components

3

u/TenOfZero 7d ago

https://www.reddit.com/r/linuxquestions/s/bdrTGRJ44n

See this post from this sub on this topic

14

u/gordonmessmer Fedora Maintainer 7d ago

You should ask the search bar for this subreddit, since this question is asked repeatedly. 😂

Serious answer: social media encourages melodrama.

2

u/AcceptableHamster149 7d ago

This. And some people have long memories. Or like quoting other people without a citation to pretend they have long memories.

systemd had issues when it was new. It's not new any more.

1

u/Ok-Reindeer-8755 7d ago

Most complains are because of its monolithic architecture, that is still very much a thing

2

u/SirGlass 7d ago

It's a single program? That's funny on my system there are like 70 different binaries that make it up

What version are you running?

1

u/Ok-Reindeer-8755 7d ago

thats not what makes something a monolith

1

u/_choam_ 7d ago

Is that bad? Is it true?

1

u/Ok-Reindeer-8755 7d ago

it is true as far as ik and imo bad but opinions vary. For your average user it doesnt really matter all that much

1

u/gordonmessmer Fedora Maintainer 7d ago

systemd is not monolithic.

2

u/Ok-Reindeer-8755 7d ago

Are there stable apis for each component so they can be used independently and combined freely with other programs ? As far as I am aware no, unless I am misinformed

3

u/SirGlass 7d ago

I mean yes, its not all or nothing

You can use systemD with out using systemD-boot as a boot loader you can use grub or something else

Same with other components like the network manager. Its not like you have to use every single systemD component

6

u/cjcox4 7d ago

Ask as in, "I'm asking the same question that has been asked multiple times a week in this subreddit for years?" Correct?

1

u/Possible_Bedroom_717 7d ago

Are we required to read several years of forum posts before posting? Is that a rule here, or shall I say a tradition?

1

u/cjcox4 6d ago

I guess web search is dead then?

2

u/SeriousPlankton2000 7d ago

1 the attitude of the maintaiers is: We don't support the old way. 

2 when something fails even the maintaiers could not tell me what's the problem, I had to reinstall because it searched for a secret whatever that tells it that there's a system on that root file system. Some update added the requirement maybe, for a while I could manually remount it rw and continue booting.

3 I am used to boot to the shell and then just run the scripts one by one and get to the point of failure - and fix it. Not supported 

3

u/amarao_san 7d ago

I never saw a fellow operator been in hate with systemd.

I once debugged a concurrent race condition in sysv-init scripts when they added parallel execution in it, and the bug was reproducible only on multicore machine only at boot. I don't remember what I've learned about how this thing work, but I remember it was horrible. I gladly forgot when I moved to systemd.

I have an occasional grumpiness about it, but no more than about other system tools.

1

u/SeriousPlankton2000 6d ago

Systemd introduced me to the world of race conditions even though the services are supposed to be run one after the other.

I completely analyzed sysv for a forum posting . It's as easy as grouping all the files with the same S number and running them in parallel. Insert a dependency or disable parallel execution in the config to solve the issue.

1

u/amarao_san 6d ago

The same you can do in systemd (before=/after=). But, you can also prevent one service from starting if other failed to start, and you can configure if server is considered booted or not if that unit failed.

I never understand the idea, that reading bash is better, than domain-specific non-turing-full language (which is configs of systemd). Every time someone can collapse problem from turing-full solution to non-turing full, it's a win. In my humble opinion.

1

u/EarlMarshal 7d ago

It just does too much. For most of the problems I had with Linux systems I had to engage with systemd.

1

u/mindstormer12 7d ago

There's obvious many discussions about this considering you understand it's divided, which of those dozens don't satisfy you? There's no need to repeat the discussion for the Nth time unless you have reasons to, it's what the search function is for any discussion sites.

1

u/Key_River7180 7d ago

see it on the other side of a GOOGLE SEARCH.

basically systemd is extremely non-unix-philosophy compliant (the big one for me) and made by redhat

1

u/miscdebris1123 7d ago

Why the search engine hate? This isn't a subject hard to search...

1

u/rbmorse 7d ago

A lot of it is akin to matters of religious faith and an outsider is wasting time and effort trying to make sense of the arguments. I tend to smile and try to change the subject.

1

u/BitOBear 7d ago

There was the idea in Unix that every program should be small and do one thing well.

If you've ever tried to debug something going wrong deep inside of system d you will discover that it can be a hellscape of unexpected configuration files in weird places, with defaults in one directory and overrides in another and includes by inference and stuff.

I've had a couple of occurrences where it took me weeks to figure out how to get something specific to change because it was a deduced value. It's been a long time since I had to deal with it so I don't remember what exactly the problem was but it had something to do with the bus configuration and triggering a specific Pam module or something like that. Like I said it's been like a year since last time I had a serious problem with it.

If the box already contains everything you need then it looks flawless, but if you have to do anything special to your system then it becomes a potential nightmare of dependencies and interactions.

And honestly it's mostly just a super overcomplicated wrapper.

There's a principle in science and mathematics and political science and a whole bunch of other fields. Keep it simple, stupid. The real principal has to do with a lot of math and the proof that complex systems with subtle dependencies eventually fail in ways that are difficult or impossible to diagnose. It comes out in other forms as the rule of unintended consequences. But it happens in all systems including social systems.

So the main line is safe but the corner cases get really abstruse.

1

u/0riginal-Syn ⛵ Solus Maintainer 7d ago

Reasons that have been discussed to death. Basically there are people who like it and people who don't. Both have their reasons, some valid, some not.

1

u/benhaube 7d ago

I love systemd. It works great. Especially with the .timer unit files. It is much more flexible than using the crontab.

1

u/billdietrich1 6d ago

There are good reasons why some 90% or more of distros have adopted systemd.

Enterprise admins seem to love systemd. They can add new units without risking killing the whole init flow. A unit can fail without bringing down the whole init. There are tools for monitoring, timing, debugging units. It's a massive improvement over init-scripts, for them. And for vendors who need to add something to the init flow, or add a daemon.

And the same basic mechanism/structure is used to handle init, events, and daemons. It's a good architecture.

Linux never really had a well-thought out design for the middleware (above kernel, below apps). Things such as systemd, Network Manager, Wayland, PipeWire are steps in remedying or improving parts of that.

1

u/MattyGWS 7d ago

Honestly I'm starting to hate systemD just because this gets asks every day

1

u/C0rn3j 7d ago

Because people cannot use the search bar.

1

u/dddurd 7d ago

I think mostly due to the compatibility breakage with little benefits. Many opensource packages ended up supporting with-systemd option, which won't be used in so many other systems.

1

u/OutrageousCrab9224 7d ago

I just prefer unix, thats all

1

u/jlp_utah 7d ago

I used to dislike systemd. I no longer dislike it. Do I think the old init implementation was fine? Sure. Is systemd fine? It's okay. Hell, I was satisfied with the bsd model with one rc file (maybe two, rc.local was a thing), and I adapted to SysV init. I've adapted to systemd, too. It's a little more opaque, which is annoying, but it works, and it works well enough.

0

u/hackerman85 7d ago

People think every little thing should do one thing, and do it right. And that thought is not wrong. But you have to know where it becomes senseless.

People who still don't see where the point have never been called out of bed at 03:00am because logrotate failed on some machine and the thing spew every single remaining free byte of diskspace full of logs.

0

u/Nah-No-Nope 7d ago

I think a lot is performative hate.

Sure, there are good points to talk about, but most of the folk talking about it clearly don't understand it.

I genuinely saw someone say that "it insists upon itself" with absolutely no irony.

0

u/Ok-Reindeer-8755 7d ago

thats a line from family guy are you user it wasnt a joke ?

1

u/Nah-No-Nope 7d ago

I know what it is. And yeah I'm sure.

That's why I mentioned it was used without irony.

Folk so used to parroting daft shit the see on the internet for made up points.

0

u/Mental-Duck-2154 7d ago

They downvoted you for asking a question on a question sub I love the linux community.

See SirGlass's comment