Dev1 Galaxy Forum / Devuan completely without systemd?

Re: Devuan completely without systemd?

dummy@example.com (ralph.ronnquist) — Sun, 19 Apr 2026 03:19:16 +0000

Really, kids, I don't think this is the forum to tell that systemd is shit. We all know that. Up on the barricades instead!

Re: Devuan completely without systemd?

dummy@example.com (brocashelm) — Sun, 19 Apr 2026 02:54:16 +0000

You can definitely remove or disable Elogind itself. You might have a harder time using a computer without the libraries most "conventional" packages are built against. ConsoleKit2 and Seatd can both help out more, plus the dummy Logind package (dummy-logind) that Devuan has made available since Daedalus. Since I need incremental RSYNC backups from Timeshift and Back in Time, Polkitd must be kept. Still, it's nice to have KDE and Network Manager functioning without any issues without an existing Elogind process (again, only the libraries are kept to avoid breaking the entire system).

Eudev is still a problem. I also personally removed Udisks2 and now use Udevil for automatic USB mounting as a non-root user (you can optionally use SpaceFM as an extra safety cushion).

As of Trixie, Debian has made it harder to remove or replace ALL parts of Systemd, never mind D-Bus (which is completely impossible to rip out and still have a functional computer). Devuan simply follows Debian's steps and applies its own blacklists regarding packages that have a hard dependency on Systemd. Elogind is used in place.

The only other Debian-based distro that has gone the great lengths to remove or lessen the impacts of Systemd or Elogind would be antiX.

Devuan completely without systemd?

dummy@example.com (nosystemd) — Sun, 19 Apr 2026 02:31:06 +0000

Systemd is a LLM-slop project now.

Systemd-udevd is replaced by eudev currently, which shows that other compoments of systemd can be removed or replaced too.

Systemd-standalone-* like etmpfiles and esysusers are unnecessary.

About elogind: it is considered not very useful. It is harmful somrtimes. It forces my machine to suspend and hard-reboot when I was compiling GCC.

Xorg/Xlibre/Xenocara works well without elogind, seatd, consolekit and polkitd, which means that a "logind" is not a critical part for GNU/Linux.

Only GNOME/KDE force the use of elogind, so I think elogind can be optional.

Most packages depending on elogind at present won't be malfunctuonal without elogind, so it's possible to make elogind optional.