I use plasma, BTW

    • AVincentInSpace@pawb.social
      link
      fedilink
      English
      arrow-up
      9
      ·
      1 year ago

      Borderline impossible if you aren’t using a distro designed with that in mind. Pretty much everything that isn’t a program you directly start (e.g. sound system, desktop environment, bluetooth daemon etc.) either only provide a systemd unit to start them (which you’ll have to manually translate into e.g. a shell script if you want it to work with your new init system) or is entirely reliant on systemd to function.

      Your choices of distro if you don’t want systemd are Debian, Void, Artix, and Gentoo, and afaik that’s about it.

      Replacing components of the systemd suite (e.g. using connman or networkmanager instead of systemd-networkd) isn’t actually that bad as long as your DE has support for them, but replacing systemd itself is something you are building your entire system around.

      • pascal@lemm.ee
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        Your choices of distro if you don’t want systemd are Debian, Void, Artix, and Gentoo, and afaik that’s about it.

        IIRC Debian was one of the first distros implementing systemd.

        • AVincentInSpace@pawb.social
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          It still leaves sysvinit as an option. Debian doesn’t lock you into systemd. Heck, it doesn’t even lock you into Linux – you can use Debian on top of the FreeBSD kernel if you so desire

    • MigratingtoLemmy@lemmy.world
      link
      fedilink
      arrow-up
      5
      ·
      1 year ago

      Extremely. When things like your DE starts being dependent on systemd, you don’t want to replace it.

      I had posted about the monopoly that systemd has, and was down voted to oblivion.