Arch Linux, and why I keep coming back

What Arch actually is

Most Linux distributions hand you a finished house — furniture arranged, defaults chosen, a friendly installer. Arch hands you the materials and the best-documented set of instructions in the world, and lets you build the house you actually want. Nothing is on your system unless you put it there.

That's the whole philosophy: keep it simple (in the engineering sense — no unnecessary layers between you and the system), and trust the user. It rubs some people the wrong way. For me it's the point. I like knowing what every piece of my machine is doing, because I put it there on purpose.

How it's different from Ubuntu or Fedora

• Rolling release.There's no "Arch 24.04." You install once and update forever; packages arrive continuously, close to upstream. You're always on the latest, which is wonderful and occasionally requires you to read a news post before updating.
• You assemble it.A base Arch install is a terminal. Desktop, audio, drivers — you choose and add them. The result is a system with exactly what you need and nothing you don't.
• pacman + the AUR.pacman is a fast, no-nonsense package manager, and the Arch User Repository is a community collection that puts almost any piece of software one command away.
• The Arch Wiki.Honestly one of the best technical resources on the internet, for any distro. Half of "learning Arch" is really just learning to read the wiki.

The core difference: other distros hand you a pre-assembled stack; Arch hands you the parts and the best manual on the internet.

Arch isn't hard so much as unabstracted. It asks you to understand the thing you're using — and then rewards you with a system that never surprises you.

Installing it, in plain terms

You boot the live ISO and do a handful of deliberate steps. Here's the whole map before we walk it — it's shorter than its reputation.

The full install, end to end. The manual part stops at arch-chroot; the highlighted step is where my script takes over.

1 · Connect and partition.Get online, then carve up the disk — at minimum an EFI partition and a root partition.

2 · Install the base system.pacstraplays the core packages onto your root partition, andgenfstabrecords how your disks should mount.

3 · Step into the new system.This is the moment it becomes "your" machine rather than the installer's.

Where my script picks up

Everything afterarch-chroot— locale, timezone, your user account, networking, the bootloader, a desktop — is the same twenty-odd commands every single time. So I wrote them down once. From inside the chroot:

It walks you through setting the root and user passwords, creates your account with Zsh and the right groups, enables NetworkManager, turns on the multilib repo, lets you pick GRUB or systemd-boot, and installs a KDE Plasma desktop plusyayfor the AUR. I broke down each section on thesetup-script pageif you want to see exactly what it touches before you run it.

Should you run Arch?

If you want a computer that just works and you never think about, genuinely — use something else, and that's not a knock. But if you want to actually understand your machine, if you like the idea of a system that only contains what you chose, and if reading a great wiki sounds like a fair trade for total control — Arch is a joy. It made me a better engineer simply by refusing to hide things from me.

I also wrote aboutusing Btrfs to make an Arch system basically un-brickable— snapshots you can roll back to when a rolling-release update inevitably has an opinion. Pair the two and you get the best of both worlds: bleeding edge, with an undo button.