• notabot@piefed.social
    link
    fedilink
    English
    arrow-up
    1
    ·
    2 months ago

    Debian never actually forced the use of systemd, they just didn’t make it obvious you could switch at install time fairly easily, or later with a bit more work. I’m running multiple sysvinit debian systems, ans they’re ticking along quite happily.

    • Venia Silente@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 months ago

      I’m not sure “tying the use of user-facing structures most useful for the community” (such as cgroupsv2 or NetworkManager) doesn’t count as “forcing”, since IIRC wicd (alternative to NetworkManager which doesn’t require systemd) has not been available in packages since Bookworm.

      • notabot@piefed.social
        link
        fedilink
        English
        arrow-up
        1
        ·
        2 months ago

        NetworkManager seems to operate correctly without systemd, although maybe there is some aspect of it that I’m not using that does require it. It’s working find on both desktop machines and laptops though, correctly managing ethernet, wifi, and vpn connections.

        Likewise, I’ve not encountered any issues with cgroupsv2.

        Support for different init systems was improved in Bullseye, although sysvinit had pretty good support even before then. I followed the instructions here and everything seemed to work out of the box.