The Distro Landscape

A Linux distribution is a curated world — the same kernel and userland, packaged a hundred different ways. The differences aren't skin-deep: each family chooses a package manager, a release model, an init system, and a philosophy — stability vs freshness, handholding vs transparency, binary vs source. This chapter maps the families, the release models, and the choice that actually matters.

The family tree — five root stocks

Almost every distro descends from one of a handful of roots:

• Debian → Ubuntu → Mint, Pop!_OS, elementary, Kali, Raspberry Pi OS, MX... — the largest lineage on Earth. apt, .deb, legendary stability, massive repos.
• Red Hat → Fedora → RHEL → CentOS/Rocky/Alma — the enterprise path. dnf, .rpm, systemd-native, SELinux.
• Arch → Manjaro, EndeavourOS — rolling release, minimal base, AUR's vast user repo. pacman.
• Slackware → Slint, Salix — 1993's survivor, BSD-style init, pkgtools, nothing hidden — this handbook's reference.
• Gentoo → source-built everything — USE flags as configuration — the LFS-adjacent lineage.
• Independents — Void (runit+musl/glibc, xbps), Alpine (musl+BusyBox, the container base), NixOS (declarative), openSUSE (zypper, rpm), Solus, Clear.

The release models — the real fork

The choice is temperament: want it to work for years → Debian stable/Ubuntu LTS. Want it new → Arch/Fedora. Want to see it all → Slackware/Gentoo/LFS.

The family differences that actually matter

• Package manager — apt/dnf/pacman/xbps/pkgtools — the daily interface (chapter 20's table)
• Init — systemd (most) vs SysVinit (Slackware) vs runit (Void) vs OpenRC (Gentoo/Alpine) — the boot personality
• libc — glibc (standard) vs musl (Alpine/Void-musl) — the ABI difference that disqualifies musl hosts from LFS
• Release cadence + support length — Debian ~5yr, Ubuntu LTS 5-10yr, RHEL 10+, Arch forever-until-broken
• Philosophy — Ubuntu's polish vs Arch's minimalism vs Slackware's transparency vs Gentoo's build-it-yourself

The specialist distros — the ecosystem's branches

• Live/rescue — SystemRescue, Knoppix, Slackware install media
• Security — Kali, Parrot — pentest toolkits
• Containers/minimal — Alpine (musl+BusyBox — why it's in every Docker image), Distroless
• Accessible — Slint, Vinux, Sonar, Accessible-Coconut, TalkingArch
• Router/embedded — OpenWrt, Buildroot, Yocto
• Privacy — Tails, Qubes, Whonix
• Old hardware — antiX, Puppy, Tiny Core (~20MB)
• Enterprise — RHEL, SLES, Ubuntu LTS
• DIY — LFS itself — the terminal point of the lineage

Choosing — the honest guide

Why Slackware — the handbook's argument

Slackware (1993 — the oldest living distro) is the choice because it hides nothing: the installer makes you partition, the init is readable scripts, the package tools leave artifacts visible in /var/log/packages. It's the LFS philosophy with a package manager — the perfect staging ground for chapter 2. Slint adds the accessibility layer that makes it the eyes-free path too.

The LFS endpoint

LFS isn't a distro — it's the source of the distro idea: a system you built yourself, no upstream. The landscape exists because someone else does the curation work — LFS shows you what that work actually is.

Exercises

1. Place three distros you've used on the family tree — which root?
2. Compare apt, dnf, pacman, xbps on the same task — the syntax grammar.
3. Identify a musl vs glibc distro — and the consequence for LFS.
4. Map a specialist distro to its niche — why that choice?
5. Argue for a distro for a specific real use — which family and why?

Timeline

See also

• Getting Linux · Package Management · Linux · Eyes-Free Linux