What Actually Makes a Distribution "Different"

Comparative Linux Distributions

Chapter 1 · What Actually Makes a Distribution "Different"

Installing and Configuring Linux already teaches how to install and configure a Linux system well — generically, without dwelling on what makes one distribution genuinely different from another. Windows 11 Fundamentals 1's own OS-landscape table went further, positioning "Linux" as a single row: CLI-first by tradition, with a GUI desktop environment as one optional layer on top. This course exists specifically to open that one row up — Linux isn't one philosophy wearing different outfits, it's several genuinely different philosophies, and this chapter names exactly what actually varies between them.

Five Components, Not One "Look"

A distribution is a specific combination of five real components — and the one most beginners notice first is, genuinely, the least defining:

Kernel — almost every mainstream distribution runs the same Linux kernel (with its own specific version and patch set), so this is rarely the real differentiator between them.
Package manager & format — how software actually gets installed, removed, and tracked; a genuinely load-bearing difference this course's own Chapter 6 covers directly, side by side.
Init system — what actually starts services at boot and supervises them afterward; overwhelmingly systemd today, with one real, living exception covered in Chapter 5 and Chapter 8.
Release model — point releases, a continuous rolling model, or a multi-year enterprise support window; covered in full in Chapter 7.
Default desktop environment — GNOME, KDE Plasma, XFCE, or none at all — the single most swappable, least defining component of the five, despite being the first thing anyone actually sees.

"It's basically all just Linux underneath" is the exact assumption this course exists to correct

A command copied from a support forum post — sudo apt install <package>, say — assumes a specific package manager that simply doesn't exist on every distribution. Running it on Arch or Alpine won't produce a helpful error pointing at the right tool; it will just fail, because the assumption baked into that one command was never universal in the first place.

Why the Desktop Environment Is the Weakest Signal

Two machines running GNOME can be running genuinely different distributions underneath — different package managers, different init systems, different release philosophies — while looking nearly identical on screen. Conversely, the same distribution can run several different desktop environments, or none. Judging "how different is this distro" by its default wallpaper and icon theme is judging the single most interchangeable piece of the whole picture.

A First Look at the Four Families This Course Covers

Family	Package manager	Init system	Release model
Debian / Ubuntu	apt (.deb)	systemd	Point release / LTS cadence
Fedora / RHEL	dnf (.rpm)	systemd	Fast cycle / multi-year enterprise
Arch	pacman	systemd	Continuous rolling release
Alpine	apk	OpenRC	Point release, minimal-first

Notice that three of the four share the same init system — the real, still-living exception is exactly where Chapter 5 (Alpine) and Chapter 8 (init systems generally) pick the story back up.

Identifying a distro reliably, from the inside

cat /etc/os-release works consistently across virtually every modern distribution and reports the exact family and version — far more reliable than guessing from a desktop's own visual theme, or assuming a colleague's "it's just Ubuntu" description is complete enough to act on.

This Course's Own Roadmap

Debian/Ubuntu and Fedora/RHEL next, then Arch, then Alpine — one chapter each, going deep on what genuinely distinguishes it. Then package managers, release models, init systems, and governance compared directly across all four at once. Raspberry Pi OS gets its own chapter as a genuine Debian derivative worth understanding on its own terms. A practical decision framework and a real, worked capstone — the same service, deployed three different ways — close out the course.

Hands-On Exercises

Exercise 1

A colleague says two machines are "basically the same Linux" because both run GNOME. Using this chapter's own five-component list, explain why that observation alone doesn't actually establish much.

📄 View solution

Exercise 2

A forum post's suggested fix begins with "just run sudo apt install...". Explain, using this chapter's own warn-box, why this instruction can't simply be assumed to work on any given Linux machine.

📄 View solution

Exercise 3

Explain why this chapter's own compare-table pointing out that three of the four families share the same init system is still a useful observation, rather than undermining the idea that these are four genuinely different distributions.

📄 View solution

Chapter 1 Quick Reference

Five real components: kernel, package manager, init system, release model, default desktop environment
The desktop environment is the most swappable and least defining of the five — despite being the most visible
cat /etc/os-release reliably identifies a distro's actual family and version
Debian/Ubuntu, Fedora/RHEL, and Arch all use systemd; Alpine's OpenRC is the real living exception (Chapters 5 & 8)
Assuming a distro-specific command (like apt install) works everywhere is a real, common mistake this course exists to prevent
Next chapter: Debian & Ubuntu — Stability-First