Learning Devuan GNU/Linux - History, Background & Why It's Needed

#Introduction

Every technology has a birth story, and Devuan was born from one of the most controversial moments in the history of modern Linux distributions. Episode 1 invites you to understand why Devuan exists — not just what it is. You'll trace the systemd debate in Debian, the philosophy of init freedom, and the line of releases that brought Devuan to the 6.0 era.

Understanding this background matters because every architectural decision in the following episodes — sysvinit as PID 1, eudev as the device manager, elogind for sessions — is a direct answer to that debate. Without the historical context, you'll see many of Devuan's choices as complicated when they all boil down to a single principle.

By the end of this episode, you'll be able to explain to others why Devuan exists, what its mission is, and why that choice remains relevant even ten years after the fork began.

#From Debian to the Devuan Fork

#The systemd Debate and the Birth of the Fork

In 2014, Debian's decision to make systemd the default init system sparked a long debate in the community. Some developers felt systemd violated the Unix philosophy — many functions that should be separate tools were instead combined into one large daemon holding PID 1. Others considered systemd the right modern direction.

The debate wasn't just technical; it touched on project governance, compatibility with sysvinit, and who had the right to decide the distro's direction. When no consensus could be reached, the group that rejected systemd took a bold step: forming a new project.

The former Debian developers who came out of it formed Devuan as a Debian fork with a clear mission: Debian without systemd. Its core principles are init freedom — the user's right to choose the init system they believe in — and the simple Unix philosophy, where each component does one task well.

#Release After Release

Devuan releases stable versions following Debian's base. Each major name in its history:

• Jessie (1.0, 2017) — the first stable release, based on Debian Jessie.
• Beowulf (3.0, 2020) — based on Debian Buster.
• Chimaera (4.0, 2021) — based on Debian Bullseye.
• Daedalus (5.0, 2023) — based on Debian Bookworm, now oldstable.
• Excalibur (6.0, 2025) — based on Debian Trixie, the current stable release.

Note that version 2.0 "ASCII" once existed between Jessie and Beowulf, but the pattern you need to remember is: each Devuan release is built on top of a mature Debian release, so the apt experience and package ecosystem stay intact.

Verify the release you're running with:

cat /etc/os-release
grep PRETTY_NAME /etc/os-release

The output of cat /etc/os-release shows PRETTY_NAME="Devuan GNU/Linux 6 (excalibur)" on an Excalibur-based system. This information is your reference for whether your repositories and examples are still relevant.

#Why Choose Devuan

#Full Compatibility with Debian Packages

Devuan's biggest strength is full compatibility with Debian packages. Because almost the entire repository is taken from Debian, you can still use apt, dpkg, and the ecosystem of thousands of Debian packages. What's replaced is only the init layer: sysvinit as the default, with OpenRC and runit as alternatives, plus eudev — a fork of udev that runs without systemd.

For organizations that have long used the classic init or reject vendor lock-in, Devuan offers a middle path: Debian's stable ecosystem with the freedom to choose your init. You don't need to relearn apt, dpkg, or the filesystem structure — it's all the same as Debian.

#Who Needs Devuan

Devuan is highly relevant for several groups: old servers running on limited hardware, users who want to understand every component of their system without mystery, operators who need a predictable and deterministic boot process, and supporters of free software principles who want full control over the init.

If you feel systemd "decides" too many things for you — from service management to logging — Devuan gives you that control back. Conversely, if you enjoy systemd's convenience, Devuan may feel like more manual work, and that's a legitimate choice too.

In practice, many Devuan users come from a server background: they appreciate fast boots because they're minimal, logs that can be read as plain text files, and no hidden processes running without their knowledge. This nature is what makes Devuan popular among operators who hate surprises.

Beyond that, the free software principle is also a driving force: with an init truly under community control, no single company dictates the direction of the operating system's development. Devuan maintains this independence through a project structure that is community-funded and community-governed — not vendor-driven.

#Practical Check: Is Your System Free of systemd?

The easiest way to prove this principle is to check PID 1 and the package list:

ps -p 1 -o comm=
apt list --installed | grep -i systemd || echo "no systemd packages"

If the output of ps -p 1 -o comm= shows init or openrc-init instead of systemd, your system is genuinely running an alternative init. The second command should find no systemd packages at all — and that's not a coincidence, but the result of the hard work of Devuan developers.

#The Philosophy Behind the Design

#Init Freedom and Simple Unix

The init freedom principle affirms that users have the right to choose how their system is booted and managed. Devuan requires all core packages to run on alternative inits and rejects hidden dependencies on systemd. The result is a more transparent system: every service is a simple shell script in /etc/init.d/ that can be read and edited directly.

This is also why Devuan maintains eudev — a device manager functionally equivalent to systemd-udev but without any dependency on systemd — and provides elogind as an optional session layer for desktops. We'll dissect this architecture fully in episode 2.

#What Doesn't Change

It's important to note what actually doesn't change in Devuan: the apt/dpkg package system, repositories, directory structure, the Linux kernel, and the majority of Debian tooling remain identical. This is what makes Devuan feel familiar to Debian users and makes migration easy — a topic we'll cover in episode 18.

#Common Misconceptions About Devuan

#Devuan Is Not Just Debian Minus systemd

There's an assumption that Devuan is just Debian minus systemd. The reality is more than that: Devuan maintains eudev, assembles init scripts for thousands of packages, provides an installer with init options, and keeps its own repositories at deb.devuan.org. Removing systemd from an already-installed Debian can cause instability — that's why episode 18 explains the correct migration process.

#Devuan Is Not an Ancient Distro

Because it uses sysvinit, which is decades old, some people assume Devuan is outdated. In fact, Devuan Excalibur is built on Debian Trixie with kernel 6.12, GNOME 48, and Python 3.13 — current technology. What's "old" is only its design philosophy: small, transparent components, not obsolete technology. Devuan's kernel, packages, and repositories always follow Debian's development periodically.

#Conclusion

Episode 1 explained that Devuan was born from the systemd debate in Debian in 2014 as a fork that preserves init freedom and the simple Unix philosophy. You also got to know Devuan's release line from Jessie to Excalibur and the reasons to choose Devuan: full compatibility with Debian packages combined with complete freedom over the init.

Key takeaways:

• Devuan is a Debian fork that runs without systemd.
• Born in 2014 after the systemd debate in Debian by former Debian developers.
• Consecutive stable releases: Jessie, Beowulf, Chimaera, Daedalus, Excalibur.
• sysvinit is the default init; OpenRC and runit are alternatives.
• eudev replaces systemd-udev as the device manager.
• Debian package compatibility stays intact because the repositories come from Debian.

In the next episode, we'll cover core concepts and the main architecture of Devuan — how the Debian kernel and packages are still used while the init layer is replaced, the roles of sysvinit, OpenRC, runit, eudev, and elogind, as well as the Devuan repository structure apt uses every day.