Because of the ubiquity, nay, monopoly of systemd I always assumed it was miles ahead of other init systems. Nope. I’ve been using a non-systemd environment for a while and must say I’m surprised by how little breaks, i.e., next to nothing. Moreover, boot and shutdown times are faster, and more of that good stuff. I suggest trying it out.

https://nosystemd.org/.

  • False
    32·
    17 hours ago

    I’ve never had systemd break either

    • greyscale@lemmy.grey.oooEnglish
      104·
      13 hours ago

      I have. Never had your machine just sit there and refuse to boot because a network share is down? Or because the wifi isn’t connected yet? Or because its waiting on some nebulous thing until timeout…

      Never had to crawl through journalctl to diagnose things and wanted to claw your own eyes out in frustration?

      You are a fortunate person.

      • KernelTale@programming.devEnglish
        3·
        3 hours ago

        My system once refused to boot, because I deleted a partition and didn’t remove it from fstab. Thankfully it was an easy and fast fix but I would expect it to just boot and give an error.

        • flying_sheep@lemmy.ml
          1·
          3 hours ago

          Right, that happened to me too.

          And it’s a problem 100% unrelated to systemd, so I wouldn’t count it here.

      • Archr
        7·
        8 hours ago

        If you are having those issues with booting maybe it is because you configured your network share incorrectly? If you are waiting on shutdown timeouts for something then just go edit the timeout. systemctl edit <stuck thing>.

        Typically when I crawl through journald it is to diagnose a problem with a specific application. Actually, the fact that those logs are easily accessible in a centralized place with easy to understand commands to access them is a reason why systemd (or more specifically systemd-journald) is so great.

        The only times that I have had major issues like that was either because (A) I misconfigured something or (B) a package came misconfigured.

      • mexicancartel@lemmy.dbzer0.comEnglish
        5·
        13 hours ago

        I hate thoose timeouts. If only there was a way to manually trigger that timeout on shutdown tty, say Ctrl-C or something which can kill it

    • arsCynic@piefed.socialOPEnglish
      81·
      17 hours ago

      I’ve never had systemd break either

      That’s not what I’m implying. Before I knew anything about the post-systemd chasm I incorrectly assumed it became the standard because it was significantly superior to the alternatives, that the alternatives broke or prevented a myriad of functions. Turns out they don’t. At least not judging from my experience in general PC usage.