Devuan delivers 99% of Debian's software through an identical package manager. The 1% it changes — ripping out systemd — reshapes everything from logging to power management.
Devuan split from Debian in 2014 when Debian adopted systemd as its mandatory default init system. The technical goal was narrow: preserve the ability to boot and run a Debian-derived system without systemd as PID 1.
Devuan accomplishes this by offering three init system choices — SysVinit (default), OpenRC, and runit — and by maintaining a tool called Amprolla that mirrors Debian's entire package archive while swapping in approximately 100 modified packages to break hard systemd dependencies.
Devuan replaces each subsystem with a standalone alternative: rsyslog for logging, eudev for devices, plain /etc/resolv.conf for DNS, chrony or openntpd for NTP, ifupdown or NetworkManager for networking, elogind for session management, and traditional cron for scheduling.
The result is a system built from discrete, independently replaceable components rather than an integrated suite — more moving parts to configure, fewer hidden interdependencies.
Every systemd subsystem has a Devuan counterpart. The tradeoff: more granular control, less integration.
| systemd component | Devuan replacement | Key difference |
|---|---|---|
| systemd (PID 1) | SysVinit / OpenRC / runit | User chooses at install time |
| journald | rsyslog or syslog-ng | Plain-text logs in /var/log/, no journalctl |
| systemd-logind | elogind | Standalone fork, ABI-compatible |
| systemd-udevd | eudev | Standalone fork from Gentoo |
| systemd-resolved | Direct /etc/resolv.conf | No stub resolver, no resolvectl |
| systemd-timesyncd | chrony / openntpd | Must install manually |
| systemd-networkd | ifupdown / NetworkManager | No Netplan support |
| systemd timers | cron / anacron | Traditional scheduling |
Devuan uses apt and dpkg identically to Debian — same commands, same .deb format, same dependency resolution. The Amprolla system transparently presents a unified repository at deb.devuan.org/merged.
Flatpak, AppImage, Docker (with init scripts), PipeWire (manual session start), all CLI tools, most GUI apps
Snap packages (hard systemd dep), GNOME (increasingly incompatible — GDM requires systemd-userdb)
Xfce 4.20 (default), KDE Plasma, MATE, Cinnamon, LXQt, Sway, i3, Openbox — all functional
GNOME devs have confirmed elogind code paths will be removed. Artix Linux already dropped GNOME entirely.
Critical rule: never mix Debian and Devuan repositories directly. Version numbering conflicts and systemd re-introduction will result.
Most daily work feels identical: same Firefox, same LibreOffice, same terminal. Differences surface at the system level. Boot shows text-mode SysVinit service messages rather than a Plymouth splash. The display manager defaults to SLiM rather than GDM or SDDM. There is no journalctl — logs live as plain text in /var/log/syslog, greppable with standard Unix tools but lacking structured querying.
Service management diverges completely. None of these are systemctl:
| Init System | Start a service | Enable at boot |
|---|---|---|
| SysVinit | service nginx start |
update-rc.d nginx defaults |
| OpenRC | rc-service nginx start |
rc-update add nginx default |
| runit | sv start nginx |
Symlink management |
Creating a new service means writing a shell script in /etc/init.d/ rather than a declarative systemd unit file. Simpler for trivial services, but lacking automatic restart policies, socket activation, cgroup resource control, and dependency-aware parallel startup.
The single area where Devuan most visibly underperforms Debian for desktop users. Multiple forum threads document persistent issues:
udisks2 + gvfs + elogind are configuredWorkarounds exist but require manual effort: editing /etc/elogind/logind.conf, writing custom ACPI event scripts, ensuring loginctl suspend replaces systemd-specific commands. On Debian, all of this works automatically.
Benchmarks on a 2-CPU / 4GB VM:
On minimal configurations with static IP, the gap shrinks dramatically — some users report sub-4-second SysVinit boots.
~30 MB for init-related processes. Higher baseline from journald, resolved, timesyncd, logind running by default.
~9 MB for init-related processes. Noticeably better responsiveness on systems with 1–2 GB RAM.
Devuan's release lag has compressed from two years (initial bootstrap) to a consistent two–three months. Codenames follow the Minor Planet Center list alphabetically.
Next up: Freia (tracking Debian 14 "Forky," expected late 2027). The unstable rolling branch is always called Ceres, paralleling Debian's Sid.
Devuan officially supports in-place migration from Debian: swap repos, install devuan-keyring, install your chosen init, purge systemd, dist-upgrade. But the gotchas are real:
libsystemd0 intentionally remains as a compatibility shim (Firefox, GIMP, CUPS, Samba link against it)/etc/apt/preferences.d/ to prevent reinstallationUsers report in-distro upgrades (Daedalus → Excalibur) completing in ~20 minutes with minimal issues.
Devuan's community is orders of magnitude smaller than Debian's. Where Debian has 1,000+ active developers and vast ecosystem coverage, Devuan is maintained by a small team under the Dyne.org Foundation.
IRC #devuan on Libera.chat, DNG mailing list, Dev1Galaxy forum, Devuan wiki (under reconstruction). DistroWatch rank ~39–58.
Most Debian documentation applies directly to Devuan since the underlying system is 99% identical. Arch and Gentoo wikis fill init-specific gaps.
Servers and embedded systems where init choice matters, GNOME is irrelevant, and lower memory footprint (~9 MB vs ~30 MB) provides tangible benefit. Also ideal for minimalist desktop setups with tiling WMs.
Laptops where power management friction creates daily annoyance, and where the loss of GNOME eliminates the most popular Linux DE. Also any workflow dependent on Snap packages.