‹ BackHN Continuity

Thread

Systemd is a suite of basic building blocks

37 points · 71 comments · Bluestein

  1. badatnames · · focus · HN ↗
    Where "basic" follows a highly nuanced alternate definition, where if you step out of line without realising it, you lose 3 days debugging a complex undocumented interaction between 4 enterprise crapware daemons only to find out the answer is "you're wrong and won't fix" buried in a 6 year old bug report, when all you did was plug in a USB mouse or try to set the default audio output device, or something else.

    Total and utter propaganda, it's underdeveloped steaming garbage

    1. ux266478 · · focus · HN ↗
      I think the problem is that it's overdeveloped rather than underdeveloped.
      1. 9dev · · focus · HN ↗
        The reason for seeing overcomplexity in systemd components is usually that you never considered the use cases of other people or proper server management - mostly because in the days of olde, everyone cobbled together their shell script Jenga towers in seclusion.
        1. kqgnkqgn · · focus · HN ↗
          If they don't have the problems that other people are having...maybe they don't need that complexity. Different use cases can use different solutions.

          An Army unit crossing rocky and muddy terrain might want tracked vehicles and tanks. I don't need that in a vehicle I drive 10 minutes to the office in the city.

          1. kjs3 · · focus · HN ↗
            This. I can see the utility of systemd and probably would have liked to have it when my team was riding herd on a DC full of Sun E15Ks and HP Superdomes. But for basically everything else that I use Linux for, every time someone says "systemd does this", at least 50% of the time I don't need that, and most of the rest I could do with with other tools with vastly less complexity.
            1. 112233 · · focus · HN ↗
              Not "this". By that logic most people do not need backups too. Rebuilding working service state after config change is non-trivial, requires using admin-only kernel interfaces, and said kernel does not care about these types of problems. Meaning average user ends up simply rebooting rather than trying to figure why enabling wifi makes printer stop working (and such). We cannot have network stuff controlled by multiple programs, because linux kernel is broken like that. This thing is the userspace part of the monolith.
              1. kjs3 · · focus · HN ↗
                By that logic most people do not need backups too.

                You need to go back for remedial logic.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.