• Venia Silente@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 day 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
      ·
      1 day 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
        arrow-down
        1
        ·
        19 hours 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
          ·
          18 hours 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
            ·
            6 hours 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.