I use plasma, BTW

  • Limitless_screaming@kbin.social
    link
    fedilink
    arrow-up
    24
    arrow-down
    1
    ·
    1 year ago

    If you try to switch a distro that’s already using Systemd to some other init system, you’ll have so many broken things to fix!

    • danA
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      1 year ago

      Debian lets you switch and AFAIK it mostly works fine. They provide both sysvinit and runit as alternatives. Packages are only required to provide systemd units now, however a lot of core packages still provide sysvinit scripts, and Debian provides a package orphan-sysvinit-scripts that contains all the legacy sysvinit scripts that package maintianers have chosen to remove from their packages.

      That’s just in the official repository, of course. Third-party repos can do whatever they want.

      • laurelraven@lemmy.blahaj.zone
        link
        fedilink
        arrow-up
        7
        ·
        1 year ago

        None of the others are as deeply integrated into everything as systemd, they pretty much just handle starting things up so dropping in a replacement should be fairly straightforward. At least, it was until everything switched to systemd. Which is probably my biggest issue with it: that it integrates to the point you can’t replace it anymore.

      • Limitless_screaming@kbin.social
        link
        fedilink
        arrow-up
        5
        ·
        1 year ago

        Honestly I don’t know. I just know that desktop environments and a lot of other packages have hard dependencies on Systemd, at least on Arch and Debian based systems. Those packages include: base, flatpak, polkit, xdg-desktop-portals, and vulkan-intel. So yeah, it’s nearly impossible to not break anything.