Ive been runing Debian 12 (kde) since bookworm was released and am loving it.

I have recently discovered Devuan which seems to be Debian without systemd - what is the benefit of removing this init system?

  • Arigion@feddit.de
    link
    fedilink
    arrow-up
    11
    arrow-down
    12
    ·
    10 months ago

    My problem with systemd is that since I’m practically forced to use it that it’s flakey in starting services after boot (independent of service and distro). Since systemd I had to install monit to check if all services came up. Didn’t had that problem before. Or I forgot, it’s been a while…

    • 7heo@lemmy.ml
      link
      fedilink
      arrow-up
      10
      arrow-down
      7
      ·
      edit-2
      10 months ago

      Don’t worry about the downvotes, Lemmy is a systemd sausage fest. If you want negative “karma”, just write “systemd bad” or even “pulseausio bad” anywhere, and wait…

      • ProtonBadger@kbin.social
        link
        fedilink
        arrow-up
        10
        arrow-down
        1
        ·
        10 months ago

        Well yes, if you don’t provide intelligible arguments it doesn’t deserve better. And a lot of the arguments really are like that: “systemd bad” or “is monolithic blob” (which it isn’t).

      • Arigion@feddit.de
        link
        fedilink
        arrow-up
        4
        arrow-down
        1
        ·
        10 months ago

        Lol. Thanks. I really don’t care. I’m running linux servers professionally since the late 90s, which means I have seen one or the other WTF. And systemd had quit some of them, especially flooding log files and race conditions. For example see https://github.com/systemd/systemd/issues/7293. That took more than 2 years to fix. And if people like to downvote my personal experience with it they are welcome to do so. I mean all I did was answering a question why one might use a systemd free distribution. Oh and for the downvoters: SYSTEMD IS MICROSOFTS ATTEMPT TO KILL LINUX! Poettering always was their agent. https://en.m.wikipedia.org/wiki/Lennart_Poettering 😉

    • ProtonBadger@kbin.social
      link
      fedilink
      arrow-up
      3
      ·
      10 months ago

      systemd does have one problem that also existed before: sometimes services come with buggy unit files (or copy/pasted from something else and modified), similar to how there were all kinds of buggy scripts before. Unit files are much simpler than scripts and it should be easier to get right but when the author sometimes doesn’t consider dependencies or test fail scenarios…

    • argv_minus_one@beehaw.org
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      10 months ago

      Use systemctl --failed to see which services didn’t come up, systemctl status SERVICENAMEHERE to see some status info about a service, and journalctl -b -u SERVICENAMEHERE to see all log messages generated by a service since last reboot.