this post was submitted on 07 Mar 2024
485 points (96.5% liked)

linuxmemes

21172 readers
903 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 members of the community for any reason.
  • 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.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
    • 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. Even if you watch it on a Linux machine.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

    • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
    [email protected]
    [email protected]
    [email protected]
    485
    Systemd controversy be like (sh.itjust.works)
    submitted 8 months ago by [email protected] to c/[email protected]
    147 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 28 points 8 months ago (2 children)

    I feel like the people who complain about systemd have never tried to mess with sysVinit scripts before

    6+ years ago, I was trying to configure a touchscreen HAT for a raspberry pi, and dicking with the init.rc script was a massive pain

    [–] [email protected] 4 points 8 months ago (2 children)

    The alternatives to systemd isn't init.d or some other legacy init systems. I use runit, pretty easy to understand and use. Stop being lazy dude

    [–] [email protected] 3 points 7 months ago

    Or dinit. dinit is awesome. s6 defeated me; an init system shouldn't be that complex.

    systemd has a lot of nice features, esp. in the area of dependencies and triggers. But it infects everything it touches, is enormous, and is buggy.

    Frankly, I'm waiting for the PipeWire successor to systemd. Like systemd, Pulseaudio was everywhere by the time enough people realized how bad it really was and someone wrote a well-designed, well-written replacement. ALSA has problems that Pulseaudio fixed, but with a badly written solution; then a good software developer came up with a good solution that solves the same problems but isn't just a giant hacky hot mess and now PA is slowly being replaced everywhere. Given that the same person, of questionable skill, who wrote PA also wrote systemd, I fully expect a better-designed solution to replace systemd.

    S6 isn't it. dinit is close, but has some holes that need addressing before it could succeed systemd, and I think it won't be it; I think systemd's successor hasn't been written yet, but I have confidence it will be.

    [–] [email protected] 1 points 8 months ago

    +1 to runit. So much simpler than systemd unit files.

    [–] [email protected] 3 points 8 months ago

    Yep. Having services stateful is a thing that SysV init doesn't offer. Look at the massive whatever that process management is that postfix had to build to get around that. No, systemd any time over custom stuff like that.