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/.

    • greyscale@lemmy.grey.oooEnglish
      11·
      9 days 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.

      • Jesus_666@lemmy.world
        1·
        3 days 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?

        I absolutely have. The solution wasn’t found in the init system, though, but by giving my NFS mounts the nofail option in /etc/fstab. Filesystem handling isn’t init’s job.

        Overall I haven’t had significantly more or less issues with systemd over OpenRC. I’m not a particularly big fan of their approach to things but their init system is perfectly serviceable.

      • Archr@lemmy.world
        0·
        8 days 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.

          • Archr@lemmy.world
            2·
            8 days ago

            Strange I guess I am not aware of any distros that come with network drives pre-configured. But either way that would be a configuration error on the distro’s side then. Waiting for a network share to be available is actually a feature to many.

            Say for instance you had critical data on the network share then you might not want to boot if that is not available. And if you don’t then you might mark the share as nobootwait.

            Without knowing what the configuration on this specific drive you are having trouble with I really could not say what is wrong.

      • mexicancartel@lemmy.dbzer0.comEnglish
        0·
        9 days 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