You’ve decided to learn Linux. Good. You go to download it, and immediately hit a wall — not the command line everyone warned you about, but a menu. Ubuntu? Debian? Fedora? Mint? Arch? AlmaLinux? There are hundreds, each insisting, with the quiet confidence of a timeshare salesman, that it is the one true choice. It’s enough to make you close the tab before you’ve typed a single command.
So before we go anywhere near a terminal, let’s clear that first hurdle: what all these “distros” actually are, why there are so many, and — the bit you actually want — which one to just pick so you can get on with it.
But… why not just use Windows?
Fair question, and worth answering honestly before you invest a minute in any of this. Windows and macOS are genuinely excellent at plenty — gaming, a great deal of professional software, and the general business of “it just works.” This isn’t a crusade. But there are real reasons to bother:
- The servers run Linux. The overwhelming majority of servers, cloud instances and containers — the machinery behind very nearly every website and app you touch — run Linux. If you want to work anywhere near infrastructure, development or networking, you will meet it. You may as well be fluent.
- It’s free, open, and runs on anything. No licence, the source is out in the open, and it’ll happily run on everything from a cheap Raspberry Pi to a supercomputer.
- It doesn’t hide the plumbing. Minimal telemetry, no bloat you didn’t ask for, no forced reboot mid-sentence — and because it lets you see how it works, it’s a superb teacher. You come out the other side actually understanding the machine.
And the best part: you don’t have to abandon Windows to start.
Tip: start without leaving Windows
WSL (Windows Subsystem for Linux) runs a real Linux distribution inside Windows — one command and you’ve a proper Linux shell sitting alongside your desktop. No spare machine, no dual-boot, no risk. It installs Ubuntu by default, which — as you’re about to see — is a very sensible first pick. Not on Windows, or want the real thing? A virtual machine or a cheap second-hand box does the same job.
So what is a “distro”, and why so many?
Here’s the reframe that makes the whole menu stop being frightening. “Linux” itself is really just the kernel — the core that talks to the hardware. On its own it’s an engine with no car around it. A distribution (“distro”) is that engine wrapped in everything that makes it usable: a package manager, a set of default programs, sensible configuration, a release schedule, and some notion of support.
Different people want different things from that wrapper — rock-solid-and-boring versus shiny-and-new, community-run versus enterprise-backed, stripped-to-the-bone versus batteries-included. So different distros exist to serve them. That’s the reassuring truth: these aren’t hundreds of different operating systems, they’re hundreds of different opinions about how to bundle the same core.
The family tree — the only map you need
Almost every distro you’ll meet descends from one of a handful of lineages. Learn the families and the hundreds collapse into a tidy few:
flowchart TD U["Unix lineage"] --> BSD["BSD family"] U --> LX["Linux kernel"] BSD --> FBSD["FreeBSD, OpenBSD"] BSD --> MAC["macOS (Darwin)"] LX --> DEB["Debian"] LX --> RH["Red Hat"] LX --> ARCH["Arch"] LX --> SUSE["SUSE / openSUSE"] DEB --> UBU["Ubuntu"] DEB --> MINT["Mint"] RH --> FED["Fedora"] RH --> RHEL["RHEL"] RHEL --> ALMA["AlmaLinux, Rocky"] ARCH --> MANJ["Manjaro"]
The two that matter most for a newcomer: the Debian line (Debian itself, its famous child Ubuntu, and friendly desktops like Mint and Pop!_OS), which uses the apt package manager; and the Red Hat line (Fedora, and the enterprise RHEL with its free rebuilds AlmaLinux and Rocky), which uses dnf. Arch — for people who enjoy assembling things themselves — and SUSE round out the usual suspects.
Zoom out one more level and there’s a pleasant surprise: Linux is Unix-like, part of a wider family that includes the BSDs (FreeBSD, OpenBSD) and — quietly — macOS, whose core is BSD-derived. That’s why your Mac’s Terminal already feels like this world: a great deal of what you learn here transfers straight to it.
The Linux you already own
Here’s the part that surprises people: you’re almost certainly running Linux already, without a screen or a login in sight. It hides inside routers, switches, NAS boxes, smart TVs, CCTV recorders and countless other appliances — anywhere a manufacturer wants a capable OS without paying a licence. That home router blinking in the corner? Very likely Linux. The switches and access points from the Networking series? Ubiquiti’s gear runs Linux, MikroTik’s RouterOS is Linux underneath, and OpenWrt is an entire Linux distro built to replace router firmware. (Their BSD cousins turn up here too — the popular firewalls pfSense and OPNsense are FreeBSD.)
Which raises a fair question: how do you fit a full Unix toolbox onto a gadget with a few megabytes of storage? That trick has a name, and it earns its homage.
Tidbit: BusyBox, the Swiss Army knife
A normal Linux system ships hundreds of separate little programs — ls, cp, cat, a shell, and so on. On a tiny device that’s a lot of files. BusyBox crams stripped-down versions of them all into a single executable a few hundred kilobytes big, and simply behaves as whichever command you invoke it by. It’s how a router — or a Docker base image — can hand you a working shell and a pile of familiar commands in almost no space at all. It bills itself, fairly, as “the Swiss Army knife of embedded Linux”; the tiny Alpine distro beloved in the container world is built on it.
The two questions behind every “which distro?” argument
You can cut through almost all the noise with two sliders:
- Stability versus freshness. Do you want software tested to within an inch of its life that changes slowly (an LTS or enterprise release), or the newest versions the day they land (a “rolling” release)? Servers lean stable; enthusiasts lean fresh.
- Community versus enterprise. A big volunteer community and forums, or a company you can pay for a decade of guaranteed support?
Nearly every heated “you should use X!” online is really just someone telling you where they sit on those two sliders. Once you know where you sit, the choice mostly makes itself.
Right, just tell me which one
Fine — here’s the opinionated bit, no fence-sitting:
| Distro | Family | Packages | Best for |
|---|---|---|---|
| Ubuntu | Debian | apt | Learning, desktops, general servers — start here |
| AlmaLinux / Rocky | Red Hat | dnf | Enterprise / RHEL-compatible, boring-stable servers |
| Debian | Debian | apt | Minimal, rock-solid servers |
| Fedora | Red Hat | dnf | Newest tech, if you like it fresh |
| Arch | Arch | pacman | Learning by building it yourself — not your first |
For your very first Linux: install Ubuntu if it’s for learning or a general-purpose machine, or AlmaLinux if you’re aiming at servers and enterprise. Then stop agonising and go type something.
Tidbit: why AlmaLinux and Rocky even exist
For years the go-to free server distro was CentOS — a free, rebuilt clone of Red Hat Enterprise Linux. In 2020 Red Hat replaced it with “CentOS Stream”, which sits ahead of RHEL rather than mirroring it — not what the people relying on a stable clone wanted. AlmaLinux and Rocky Linux sprang up almost overnight to fill the gap: free, community-run, bug-for-bug RHEL-compatible. It’s why “just use CentOS” quietly stopped being the advice.
The relief: it mostly doesn’t matter
Here’s what nobody tells the panicking beginner: once you’re at the shell, something like 90% of what you learn is identical across every distro. The commands, the filesystem, the way permissions and processes work — all the same. The genuine differences come down to the package manager (apt vs dnf vs pacman) and a few default choices. Distro-hopping later, once you’ve found your feet, costs you an afternoon and teaches you something. So don’t let the choice paralyse you — it’s a starting point, not a marriage.
The one-sentence version
A distro is just an opinionated bundle wrapped around one shared Linux kernel; pick a popular, well-documented one — Ubuntu or AlmaLinux — and almost everything you learn will travel with you.
So: you’ve chosen one, installed it (or fired up WSL), and now you’re sitting in front of a blinking user@host:~$ prompt with no idea what to type. That’s exactly where we start next time — finding your feet at the console, and the mental model that turns a Linux box from a black box into a conversation. And since, out in the real world, you’ll usually meet these machines over the wire rather than sat in front of them, that thread leads somewhere rather useful too.