this post was submitted on 23 Sep 2024
768 points (95.6% liked)

linuxmemes

20993 readers
1320 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
    768
    submitted 3 weeks ago* (last edited 3 weeks ago) by [email protected] to c/[email protected]
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 33 points 3 weeks ago* (last edited 3 weeks ago) (2 children)

    Bullshit, there's always reasons listed. Some more, some less opiniated, but there's always lists.

    For me personally:

    • no portability
    • not-invented-here syndrome
      • manages stuff it shouldn't, like DNS
      • makes some configurations unneccessarily complicated
    • more CVE than all other init together
      • service manager that runs with PID 0
    [–] [email protected] 6 points 3 weeks ago (1 children)

    Try writing a init script on systemD.

    It's amazingly simple

    [–] [email protected] 3 points 3 weeks ago

    But only that.

    Btw, dinit is simpler. :)p

    [–] [email protected] 20 points 3 weeks ago (1 children)

    To the feature creep: that's kind of the point. Why have a million little configs, when I could have one big one? Don't answer that, it's rhetorical. I get that there are use cases, but the average user doesn't like having to tweak every component of the OS separately before getting to doom-scrolling.

    And that feature creep and large-scale adoption inevitably has led to a wider attack surface with more targets, so ofc there will be more CVEs, which—by the way—is a terrible metric of relative security.

    You know what has 0 CVEs? DVWA.

    You know what has more CVEs and a higher level of privilege than systemd? The linux kernel.

    And don'tme get started on how bughunters can abuse CVEs for a quick buck. Seriously: these people's job is seeing how they can abuse systems to get unintended outcomes that benefit them, why would we expect CVEs to be special?

    TL;DR: That point is akin to Trump's argument that COVID testing was bad because it led to more active cases (implied: being discovered).

    [–] [email protected] 8 points 3 weeks ago (1 children)

    Sure, some like overengineering.

    [–] [email protected] 6 points 3 weeks ago (1 children)

    is it overengineering or just a push back against "make each program do one thing well," and saying yeah but I have n things to do and I only need them done, well or not I just need them done and don't want to dig through 20 files to do it...

    [–] [email protected] 3 points 3 weeks ago* (last edited 3 weeks ago)

    I'd argue s6 does that aspect better, and without overengineering and userspace-dependents. Systemd was just the earlier bird.