this post was submitted on 08 Oct 2025
787 points (94.3% liked)

linuxmemes

27604 readers
1762 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn, no politics, no trolling or ragebaiting.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
  • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
  • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
  • Β 

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] JackbyDev@programming.dev 29 points 17 hours ago (4 children)

    I don't get the systemd hate. The most common complaint I see is that it's too bloated, but Arch uses it, so what gives? Is it just that people dislike change? Like Wayland hate (not Wayland frustration)?

    [–] PiraHxCx@lemmy.ml 8 points 12 hours ago* (last edited 12 hours ago)

    From what I heard, people hate systemd because Linus Torvald was approached by the NSA to create a backdoor on Linux, he said it wouldn't be possible to change the kernel because there were too many eyes on it, and right after that a mysterious hack of kernel.org introduced a mysterious code but it was spotted and removed... well, what was the other thing common to all Linux? The sysv-init, but it was too small, too tight, too specific for them to create a backdoor there, they needed something big, bloated, doing way more than it should do, like it was just supposed to start the system but it can also do unrelated stuff like handling DNS, and then a subsidiary of an American Big Tech company shows up bring systemd, that solved all the problems the NSA had to create a backdoor on Linux, and all distros jumped into the honeypot :)

    [–] jj4211@lemmy.world 8 points 14 hours ago* (last edited 14 hours ago) (1 children)

    Generally I see a few:

    • People wanting the highly deterministic, but slower behavior of the rc scripts.
    • People liking the fact that the rc startup was generally almost entirely defined in plain script files
    • Some folks criticizing certain opinionated things in systemd, as systemd delves deeper into things like capabilities and users.
    • Systemd can sometimes be a bit weird about how it does/does not capture stdout/stderr as one might guess in some situations.
    • Some folks not liking the journald angle of binary-only files

    Mainly the last point is the only one I personally find potentially aggravating, but since I never really am in a broken system without journalctl I'm not too bothered by it. I have saved myself some effort thanks to systemd including stuff that the daemons used to provide for themselves.

    [–] tetris11@feddit.uk 10 points 14 hours ago* (last edited 14 hours ago)

    People wanting the highly deterministic, but slower behavior of the rc scripts.

    This is literally it for me. I got to work on an alpine system and it was like a breath of fresh air - I could edit the service script files directly. So easy, so little abstraction

    [–] ZILtoid1991@lemmy.world 10 points 17 hours ago (1 children)

    I'm more frustrated with GNOME devs sabotaging Wayland.

    [–] SpaceCadet@feddit.nl 6 points 16 hours ago

    That is a self-inflicted wound caused by how Wayland was designed, particularly the part where they offloaded so much responsibility onto the different compositors.

    [–] erev@lemmy.world 8 points 17 hours ago (2 children)

    So people hate on systemd because they interpret it as an init system thats gone too far and has thus violated the unix principle. in reality systemd is an entire suite of tools based around a very feature rich and robust service management suite that also includes an init system. there is something to be said about the Linux ecosystem's reliance on systemd, but there are no comparable tools. this is why Arch uses systemd. if you dont want to use systemd, you can use distros like Arco Linux; however currently Gnome no longer works on Arco

    [–] Verat@sh.itjust.works 7 points 14 hours ago* (last edited 13 hours ago) (1 children)

    Part of the problem with it is that it is very difficult not to use it, for instance if your code uses dbus, that makes systemd a dependency and almost all of the tools are like this. Want to use alternate software with systemd init? A-OK! want to use systemd tools without systemd init? Too bad! This inter-dependence is what I think makes it break the unix philosophy, its components dont like to be replaced or used outside of the "intended" environment of systemd init, keeping it from being replaced without breakage on lot of systems.

    On my install for instance, systemd is roped in by xdg-user-dirs (and hence steam), flatpak, fcitx5, and cups. And that is just a few. So the init system isnt a problem to me, the lack of drop-in replacements for its suite of tools is.

    [–] erev@lemmy.world 5 points 13 hours ago (1 children)

    I think the biggest problem is that developing each other underlying subsystems without the rest is a hassle. As such no one has come up with a non-systemd dbus replacement. But there is a lot that can be replaced. There are some systemd services i just turn off immediately woth new installs and use something else because they're such dogshit (looking at you resolved).

    god i fucking hate systemd-resolved

    [–] lightsblinken@lemmy.world 3 points 8 hours ago (1 children)

    +1 on systemd-resolved. dumpster fire of horribleness. i dont mind 99% of systemd subsystems, but this one tips me over the edge, hard.

    [–] erev@lemmy.world 3 points 6 hours ago

    it pisses me off so much. what do you mean theres no way to set the priority of nameservers or to force them to be resolved in a specific order? no i don't want a public nameserver thats only there as backup to take precedence over my local nameserver thats necessary for kerberos to work!

    [–] BartyDeCanter@lemmy.sdf.org 6 points 17 hours ago (1 children)

    So you're saying systemd is the emacs of init?

    [–] erev@lemmy.world 1 points 15 hours ago

    if sysv init or open rc are ed and sed, then systemd is Visual Studio or Pycharm; they have some functionality that overlaps but they scopes of what they do are completely different