Linux distributions explained, and which to pick

level:Beginner

If Linux is one kernel, why are there hundreds of things to download, all called Linux, with different names and logos and fierce online fan bases? The previous part gave the short answer: a distribution is somebody's particular assembly of the kernel plus all the surrounding programs, and because the pieces are free, anyone can assemble them differently. This part is the longer answer. The good news is that the hundreds of distributions are not hundreds of unrelated things. They cluster into a handful of families, and once you understand what actually differs between them, the choice stops being overwhelming.

What actually differs (and what does not)

Start with what does not differ: the kernel is essentially the same everywhere. The thing that talks to your hardware is shared, which is why "it runs on Linux" means roughly the same thing whether you are on Ubuntu or Arch. The differences are all in the assembly around it, and they come down to four things.

The first is the package manager — the tool that installs, updates, and removes software. The second is the release model — whether the distribution ships big versioned releases every year or two, or updates continuously. The third is the defaults — which desktop you get, which applications are pre-installed, how much is configured for you out of the box. The fourth, underneath all of it, is philosophy — whether the project optimises for stability, for newness, for simplicity, for corporate support, or for handing you complete control. Almost every argument about distributions is really an argument about one of these four.

What a package manager is

On Windows or macOS you install software by downloading an installer from a website and double-clicking it, and you update each program separately. Linux works differently. A package manager is a single tool, built into the distribution, that installs software from a central, curated repository maintained by the distribution itself. You ask for a program by name and the package manager downloads it, installs it, and pulls in anything else it depends on. One command updates every program on the system at once.

The closest reference point you may already have is a phone app store, or Homebrew if you have used a Mac: one trusted place to fetch software by name, with updates handled centrally. The Windows .exe-from-a-website habit, where every app updates itself and you trust each download individually, is the model Linux deliberately moved away from. macOS sits in between — an App Store for some things, manual downloads and Homebrew for the rest — whereas on Linux the package manager is the default path for essentially everything.

The package manager is the most visible thing that distinguishes a distribution family, because the families use different ones that are not interchangeable. The Debian family uses apt and .deb packages. The Red Hat family uses dnf and .rpm packages. Arch and its relatives use pacman. openSUSE uses zypper. Learning a distribution largely means learning its package manager, and the commands you build muscle memory for do not carry over between families.

The major families

The hundreds of distributions descend from a handful of roots. Debian sits at the head of the biggest tree, Fedora feeds the Red Hat enterprise line, Arch spawns friendlier relatives, and openSUSE stands largely on its own. Seeing the lineage makes the names click into place.

graph TD
    A["Debian"] --> B["Ubuntu"]
    B --> C["Linux Mint"]
    D["Fedora"] --> E["RHEL"]
    D --> F["CentOS Stream"]
    G["Arch Linux"] --> H["EndeavourOS"]
    G --> I["Manjaro"]
    J["openSUSE<br/><i>Leap + Tumbleweed, standalone</i>"]

The major lineages: each child inherits its parent's package manager and broad approach, then changes the defaults.

Debian to Ubuntu to Linux Mint

Debian is one of the oldest distributions, founded by Ian Murdock in 1993, and it is famous for prioritising stability and free-software principles above all. It is the root of the largest family tree in Linux. Ubuntu, first released in October 2004, is built on Debian but adds polish, a predictable release schedule, and commercial backing, which made it the distribution that brought Linux to a lot of ordinary desktops. Linux Mint, in turn, is built on Ubuntu and aims squarely at newcomers, especially those coming from Windows, with a familiar layout and sensible defaults. All three use apt. This is the most beginner-friendly lineage and by far the most heavily documented.

Fedora to RHEL and CentOS Stream

Fedora is the community distribution sponsored by Red Hat, and its character is "modern but stable": it ships newer software than Debian-family distributions and frequently adopts new technologies first, while staying polished enough for daily work. Upstream of the commercial product, Fedora feeds into Red Hat Enterprise Linux (RHEL), the paid, long-support distribution that dominates corporate servers, with CentOS Stream sitting between the two as a rolling preview of what the next RHEL will contain. This family uses dnf and .rpm packages. If you have heard that "enterprise Linux" means Red Hat, this is the family they mean.

Arch to EndeavourOS and Manjaro

Arch Linux was started by Judd Vinet in March 2002, and its philosophy is the opposite of "we will set this up for you." Arch ships a minimal base and expects you to build the rest yourself, which is exactly why this series ends on it. It uses pacman and is famous for two things beyond the package manager: a rolling release model and the legendary Arch Wiki. Because installing Arch by hand intimidates people, two relatives smooth the edges: EndeavourOS gives you a near-vanilla Arch with a friendly graphical installer, while Manjaro goes further, holding packages back for extra testing and adding its own tooling. This series teaches the manual Arch install on purpose, but it is worth knowing the gentler relatives exist.

openSUSE, off to the side

Worth a mention because it does not fit neatly into the three big lineages: openSUSE is a well-regarded European distribution that comes in two flavours — Leap, a stable point-release, and Tumbleweed, a rolling release — and uses the zypper package manager. It is less common in beginner guides than the others but is solid and powerful, particularly for anyone who likes its YaST configuration tool.

Release models: stable versus rolling

What stable (point) release means

The Debian, Ubuntu, and Fedora families mostly use a point-release model. The distribution picks a set of program versions, tests them together as a unit, and ships that frozen set as a numbered release — Ubuntu 24.04, Debian 12, and so on. For the life of that release you receive security and bug fixes but not new feature versions of your software. Debian Stable takes this to an extreme: its packages can be several years old, deliberately, because old-and-thoroughly-tested is the whole point. The advantage is predictability — your system does not change underneath you. The cost is that your software ages between big upgrades.

What rolling release means

Arch and openSUSE Tumbleweed use a rolling release model instead. There are no big numbered versions; packages are updated continuously, so the system is always current. You install once and, in principle, keep that same installation up to date forever, always running close to the latest kernel and the latest application releases. The advantage is freshness and never facing a scary once-every-two-years mega-upgrade. The cost is a slightly larger surface for surprises: because updates arrive with a shorter testing window, a rolling system occasionally hands you a change that needs your attention. On Arch this is manageable precisely because the documentation is so good and the system is so transparent — but it is a real difference in temperament, and choosing rolling means accepting that you are an active participant in keeping your machine healthy.

ℹ️ Note Rolling versus point is not "better versus worse," only a trade between freshness and predictability. A point release changes rarely but ages; a rolling release stays current but asks for your attention more often. Match the model to your temperament, not to which one sounds more advanced.

The two models look quite different as flows. A point release moves in big, infrequent jumps between frozen, tested snapshots; a rolling release is a single install that receives a steady stream of small updates and never jumps versions at all.

graph LR
    A["Install release N<br/><i>frozen, tested set</i>"] --> B["Security + bug fixes only"]
    B --> C["Big upgrade to release N+1"]
    C --> D["Repeat every 1-2 years"]

Point release: discrete frozen snapshots, upgraded as occasional events.

graph LR
    A["Install once"] --> B["Small update"]
    B --> C["Small update"]
    C --> D["Always current, no version jumps"]

Rolling release: install once, then a continuous stream of small updates forever.

Which to pick

The honest recommendation depends entirely on what you want from the experience. The decision really comes down to a couple of questions about what you want from the machine.

flowchart TD
    A["What do you want?"] -->|"just works, new to Linux"| B["Linux Mint or Ubuntu"]
    A -->|"newest hardware or dev work"| C["Fedora"]
    A -->|"learn and control everything"| D["Arch Linux"]

Beginner or migrating from Windows leads to Mint/Ubuntu; modern hardware and development to Fedora; the urge to learn and control to Arch.

💡 Tip If you just want a default: pick Mint or Ubuntu when you are new to Linux or coming from Windows, Fedora when you have newer hardware or do development work, and Arch when your goal is to learn and control the whole system. Any of the three is a defensible first choice.

If you are a first-timer or migrating from Windows and you mainly want a computer that works so you can get on with your life, install Linux Mint or Ubuntu. They are the gentlest landing, the most documented, and the least likely to ask anything difficult of you on day one. There is no shame in starting here; many long-time Linux users still run them.

If you have newer hardware, you are a developer, or you want current software without committing to the maintenance temperament of a rolling release, Fedora is an excellent middle path: modern, polished, and well supported.

If your goal is to genuinely understand and control your system — which, if you are reading this series, it probably is — then Arch is the answer, and that is where this series is going. You will not pick Arch because it is easy; you will pick it because building it yourself teaches you what every other distribution hides. The full case for that choice, including what the rolling model and the Arch Wiki and the AUR actually give you in return for the effort, is the subject of why Arch Linux.

One more variable cuts across all of this: every distribution ships a different default desktop, and the desktop is the part you actually look at and click all day. Linux Mint defaults to Cinnamon, Ubuntu and Fedora Workstation to GNOME, Manjaro to KDE Plasma or Xfce depending on the edition. Those are swappable, separate pieces — not welded to the distribution — and understanding that layer is important enough to get its own part: what a desktop environment is.

A short close

Distributions do not differ in the kernel; they differ in the package manager that installs your software, the release model that governs how it ages, the defaults you start with, and the philosophy behind all three. Sort them into families — Debian, Red Hat, Arch, openSUSE — and the hundreds collapse into a handful of real choices. For a first machine, reach for Mint, Ubuntu, or Fedora. To learn, reach for Arch, and read the next part to understand the desktop layer before you commit.