• corsicanguppy@lemmy.ca
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    3 days ago

    If you’re writing bash scripts you’re basically replicating a lot of the functionality of systemd

    You have that backwards

    If you’re writing Systemd profile profile profiles you’re replicating shell scripts but with a lot of spongey unknown “come on, pumpkin” cancer code that you’re only sure will do what you think because you don’t know what suddenly capriciously changed in enterfuckingprize code and boy is your remote server screwed. Fuck me if I need to actually rely on something starting.

    No one said sysV is awesome. It’s built to best practice and it does what it does really well, but that’s not a lot. But it does it well. Oh, the days Systemd has ruined trying to work half as well as ; well fuck, every alternative.

    The days Systemd doesn’t ruin, it’s the other cancer, network manager and ‘consistent’ naming. And devices that don’t come up. And devices that don’t actually assign a fucking static goddamned address. #youHadOneJob

    Spot the parts of enterprise Linux that runs like shit and barely does the same thing twice on two identical adjacent boxes, and I’ll show you some whiz kid who shat out some cancer and went to go work at Microsoft.

    So. Anyway, because the reliable stuff came before Systemd’s change-for-lulz setup, you had them in the wrong order unless you have a time machine.

    • a Kendrick fan@lemmy.ml
      link
      fedilink
      arrow-up
      1
      ·
      2 days ago

      Very much this, why is systemd entangling itself in every part of the linux kernel, I ripped that mfer network-manager and installed iwd

      I’m on guix-sd and don’t have to suffer systemd