I use plasma, BTW

  • ebc@lemmy.ca
    link
    fedilink
    arrow-up
    6
    ·
    2 years ago

    At the level I care about, which is “I want this daemon to start when I boot up the computer”, systemd is much better. I can write a ~5 line unit file that will do exactly that, and I’ll be done.

    With init, I needed to copy-paste a 50-line shell script that I don’t really understand except that a lot of it seemed to be concerned with pid files. Honestly, I fail to see how that’s better…

      • uranibaba@lemmy.world
        link
        fedilink
        arrow-up
        4
        ·
        2 years ago

        The only arguments against I have seen so for is systemd does a lot more than just handing system startup (systemd-resolved is one such example) and files that was previously stored as text now require systemd’s own tool to read (journalctl?).

        So not the actual startup function, just everything else.

        • CanadaPlus@lemmy.sdf.org
          link
          fedilink
          arrow-up
          3
          ·
          edit-2
          2 years ago

          Based on the video someone posted, it’s not very portable either.

          I feel that little part of my brain that wants to add yet another standard itching. Easily starting something at boot is good, but I don’t see why that has to come with loss of modularity.

          • jbk@discuss.tchncs.de
            link
            fedilink
            arrow-up
            1
            ·
            2 years ago

            Afaik they don’t care about being portable to instead focus as much as possible on being fast and whatever