This chapter follows A short history of Unix and Linux.
Downloading “Linux” usually means downloading a distribution: a curated combination of kernel, init system, libraries, desktop or server defaults, and a way to install updates. Debian is one of the oldest and most influential distributions; this series uses Debian 13 “trixie” as the reference for paths, tools, and defaults while explaining ideas that apply across distros.
What a distribution adds to the kernel
The kernel handles hardware, scheduling, memory, and system calls. Everything you interact with as an administrator or developer sits in user space: systemd or another init, apt, OpenSSH, Apache, GNOME, and thousands of packaged pieces.
A distribution answers practical questions the kernel does not:
- Which kernel version and patch set ship by default, and for how long are they supported?
- Which init and service manager run at boot?
- Where do packages come from, and who signs them?
- What is free software policy—firmware, codecs, non-free drivers?
Two machines can run the same upstream kernel version yet feel different because Fedora, Debian, and Arch make different choices in those layers.
Debian’s social contract and software freedom
Debian is governed by a Social Contract and Debian Free Software Guidelines (DFSG). The main archive on Debian mirrors contains software that meets the DFSG. Contrib holds free software that depends on non-free elsewhere; non-free-firmware (and related components) hold firmware and other items Debian ships separately so users can opt in.
That split matters on real hardware: Wi-Fi and graphics often need firmware packages from non-free-firmware. The installer can prompt you to enable that component; see Package management on Debian for how repositories express those choices.
Stable, testing, and unstable
Debian development flows through named suites:
| Suite | Role | Typical use |
|---|---|---|
unstable (sid) |
New uploads land here first | Developers and testers |
| testing (e.g. trixie before release) | Release candidate quality | Early adopters |
| stable (e.g. bookworm, then trixie after release) | Security and point releases | Servers and desktops that want predictability |
Stable receives security updates and occasional point releases; version numbers of major packages stay fixed unless backports or a new stable release brings newer stacks. Testing freezes before a release: installers and documentation target that codename until it becomes the new stable.
On a stable system, /etc/debian_version and lsb_release -a show what you run:
cat /etc/debian_versionlsb_release -aDerivatives and downstream branding
Many distributions derive from Debian without forking the kernel:
- Ubuntu and Linux Mint rebuild and repackage Debian workflows with different release cadence, defaults, and support contracts.
- Raspberry Pi OS targets ARM boards with Debian-based roots and board-specific kernels.
Derivatives can lag Debian stable or track testing for newer desktops. When you read “Debian-based,” expect .deb packages, apt-style workflows, and often similar filesystem layout— but not identical package versions or kernel configs.
Other distribution families
Understanding Debian is easier with contrast:
| Family | Examples | Package model | Release style |
|---|---|---|---|
| Debian-derived | Debian, Ubuntu, Mint | .deb, APT |
Stable + timed releases (Ubuntu) or rolling-ish LTS |
| Red Hat lineage | Fedora, RHEL, AlmaLinux | .rpm, DNF/YUM |
Fedora fast; RHEL long support |
| Arch lineage | Arch, Manjaro | .pkg.tar, pacman |
Rolling release |
| Independent | openSUSE, Alpine | RPM or apk | Varies |
Alpine is common in minimal containers; RHEL dominates enterprise support contracts. None of that negates Debian as a neutral reference for POSIX layout, systemd, and the topics in this series.
Choosing a base for your work
Pick stable Debian (or an LTS derivative) when you want reproducible servers and documented upgrade paths every few years. Pick testing or a rolling distro when you need newer drivers or desktops and accept more churn. Pick a vendor image (cloud AMI, WSL, Raspberry Pi) when hardware or platform integration matters more than vanilla Debian ISOs.
The kernel behavior underneath is shared; the next chapter, The Linux kernel, explains what that shared layer actually does in kernel space versus user space.
The next chapter is The Linux kernel.
Check your understanding
Question 1 of 6
0 of 6 checked