• Venia Silente@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      3
      ·
      14 days ago

      Just use the normal procedure for switching to sysvinit (or openrc) + elogind. Easy to perform if you still have your install media.

      • 0x0@lemmy.zip
        link
        fedilink
        arrow-up
        2
        ·
        14 days ago

        Just use the normal procedure for switching to sysvinit

        On Debian?? That’s news to me.

        • Venia Silente@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          4
          ·
          14 days ago

          It’s actually well-documented in their wiki (yeah, I know, it’s 2025 people don’t read that because it’s not Discord and that shit). Tho i recommend adding Antix’s nosystemd repo if you do that on systems that are not Sid, because the packaging of some important high-level tools is stupidly tied to systemd for some weird reason (NetworkManager being a good example) and the upstreams refuse to unfuck it (which is as simple as restoring the init script those upstreams already used to have).

          • 0x0@lemmy.zip
            link
            fedilink
            arrow-up
            1
            ·
            14 days ago

            is stupidly tied to systemd for some weird reason

            Intentional hard-linking.

            I went gentoo once debian forced systemd on its users, i wasn’t aware they sorta backtracked, nice to know.
            Slackware and Devuan fill my other needs so i have no plans to go back to Debian.

            • notabot@piefed.social
              link
              fedilink
              English
              arrow-up
              1
              ·
              13 days 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
                ·
                11 days 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
                  ·
                  11 days 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.