Arch — Rolling Release & DIY

Comparative Linux Distributions

Chapter 4 · Arch — Rolling Release & DIY

Chapters 2 and 3 both covered distributions built around discrete versions — Debian Stable's own frozen releases, Fedora's ~13-month cycles, RHEL's multi-year majors. Arch has none of that at all — no version number to even ask about — and its own installation philosophy is just as deliberately different.

Rolling Release — There Is No "Arch 15"

Arch has no discrete releases in the way every distribution covered so far does. Packages update continuously, directly from upstream, with no periodic freeze-and-snapshot cycle at all — the system genuinely is whatever's currently in the repositories, all the time. There's no equivalent to "Fedora 40" or "Debian 12" to name, because the entire concept of a numbered release doesn't apply here.

What "an update" means
Debian / Fedora / RHEL (point release)Small patches within a fixed version, until the next full version replaces it entirely
Arch (rolling)Continuous, small, frequent updates — there is no "next version" to eventually move to

pacman & the AUR

pacman is Arch's own package manager — pacman -S installs, pacman -R removes, pacman -Syu performs a full system update. The philosophy is frequent, small, incremental updates rather than the big periodic jumps Chapters 2 and 3 both described.

The AUR (Arch User Repository) is community-submitted — but critically, it doesn't hold pre-built binary packages the way the official repositories do. It holds PKGBUILD scripts, community-written build instructions that fetch source code and compile it locally.

The AUR is not vetted the way official repositories are
An AUR package is a user-submitted script, not a package reviewed and signed by Arch's own developers — treating it with the same default trust as an official repository package is a real mistake. Reading a PKGBUILD before building it (to see exactly what it downloads and runs) is standard, sensible practice within the Arch community itself, not excessive caution.

The Arch Wiki — Respected Well Beyond Arch Itself

The Arch Wiki is genuinely well regarded across the entire Linux world — detailed enough that users of completely different distributions regularly consult it for generic Linux configuration and troubleshooting information, adapting package-manager-specific steps to their own system as needed.

"You Configure Everything Yourself"

Installing and Configuring Linux covers a guided installer making sensible decisions on a user's behalf — partitioning, package selection, bootloader setup, all handled with reasonable defaults. Arch's own traditional installation process is the deliberate opposite: partitioning, mounting, base package selection, and bootloader configuration are all performed explicitly, one command at a time, with no default assumed unless the installer using it chose one on purpose. (A newer, official archinstall script offers a guided path today, but the manual process remains the canonical, most-documented route — and still the one the Arch Wiki's own installation guide centers on.)

Checking installed package versions directly
pacman -Q lists every installed package and its exact current version — genuinely useful given there's no distribution-wide version number to reference instead; on a rolling-release system, the individual package versions are the only meaningful version information that exists at all.
Rolling release means reading before updating, not blindly running pacman -Syu
Arch's own official policy explicitly expects users to check the Arch news feed before a major system update — occasionally, a package update requires manual intervention (a config file migration, a one-time extra step) that an automatic update alone won't handle. This isn't a flaw in the rolling model; it's the trade-off the model makes explicitly, in exchange for never needing a disruptive, all-at-once version jump.

Hands-On Exercises

Exercise 1

A user asks "which version of Arch are you running?" Explain why this question doesn't have the kind of answer it would have for Debian or Fedora, using this chapter's own explanation of the rolling-release model.

📄 View solution
Exercise 2

A user installs an AUR package the same way they'd install one from Arch's official repositories, without reviewing it first. Using this chapter's own warn-box, explain what real risk this overlooks.

📄 View solution
Exercise 3

Explain what "you configure everything yourself" actually means in Arch's traditional installation process, contrasting it directly with Installing and Configuring Linux's own guided installer.

📄 View solution

Chapter 4 Quick Reference

  • Rolling release — no version numbers at all; the system is always whatever's currently in the repos
  • pacman — -S install, -R remove, -Syu full system update, favoring frequent small updates
  • The AUR holds unvetted, user-submitted PKGBUILD scripts — not equivalent in trust to official repository packages
  • The Arch Wiki is respected and consulted well beyond the Arch community itself
  • Arch's traditional installer requires every decision explicitly, contrasted with Installing and Configuring Linux's own guided defaults
  • Rolling release trades away disruptive version jumps for the occasional need to read release notes before updating
  • Next chapter: Alpine — Minimalism as a Design Goal