Linux Is a Stance, Not a Distro

A distro war is usually a shopping argument: wallpaper, installer, which package manager feels friendlier. The interesting decision sits upstream of the ISO.

Thesis

Linux is a stance toward the commons. You run a kernel, an init system, and a packaging culture you can read, fork, and argue about in public. The distro is how that stance arrives on disk.

Context

I daily-drive Fedora. Not because it won a beauty contest. Because it sits close to upstream, ships a current kernel, and treats the workstation as something you can rebuild when a disk dies or a country changes. Auckland 2026 is a relocation, not a license transfer. I do not want the machine that holds mystic-bytes drafts to depend on a store account that might not follow me.

The fights people remember as “taste” were policy. systemd as pid 1. Pulse versus PipeWire. SELinux on by default. Those arguments were about who starts services, who owns logs, who may isolate a process, and whether “the Unix way” still means a pile of text files you can grep. Fedora picked sides. Debian wrote a lot of the culture down. Neither choice was a theme pack.

When mystic-bytes CI runs on a Linux runner, the same stance shows up in miniature: a kernel, cgroups, a user, a package set. The essay repo is markdown. The build host is still an operating system with opinions.

Mechanism

The Linux kernel is a commons with a written process. In-tree documentation describes how subsystems work and how changes land.¹ You do not pick a kernel like a laptop skin. You consume a shared artifact, live with the license and the merge discipline, and discover whether your Wi-Fi chip has a mainline driver.

A distribution is a social contract around that commons. Debian’s policy manual is the blunt version: what a package may do, how it must declare dependencies, what “free” means in that archive.² You can dislike a paragraph and still recognize the genre. Fedora’s contract is different: closer to upstream, faster cadence, Workstation as a supported opinion about a developer laptop. The installer is not the stance. The stance is: we will ship what just landed, and we will document how to live on it.

Init is policy wearing a daemon. systemd is a suite of building blocks for starting, logging, and isolating services.³ The decade of arguments about it were arguments about pid 1: unit files versus shell scripts, journald versus text logs, cgroups as a first-class interface. People dressed those fights in aesthetics. Underneath, they were asking who gets to define “the machine is up.” Fedora’s default is a vote. Pretending it was only about Unix purity was how the thread stayed loud.

Packaging is trust: who signs the RPM, which COPR you enable at 1am, whether /usr is yours to replace. Kernel docs will tell you how a subsystem behaves. They will not tell you whether your distro’s freeze window lets you have that subsystem this month. That gap is why “I use Linux” is under-specified. You use a policy bundle.

Rebuildability is the test I actually run. If the SSD fails in a hostel, can I reinstall, clone mystic-bytes, and be writing the same afternoon? Fedora plus git plus a documented dotfile set passes. A sealed appliance that needs a vendor blessing does not.

Tradeoffs

You own the breakage. A workstation you can rebuild is a workstation you can brick. Fedora’s closeness to upstream means you meet regressions earlier than a conservative freeze. I accept that because the alternative is waiting on a vendor’s calendar. I do not pretend it is free.

Hardware still assumes someone else’s OS. Laptops, printers, and the Wi-Fi chip in a cheap travel adapter are still certified against Windows, sometimes macOS. Linux on the daily driver is a research project the week a new machine arrives. The stance includes that week. It does not include sneering at people who cannot spend it.

Choice is not a feature if it never converges. A thousand spins look like freedom and behave like a support desert. Fedora Workstation is an opinionated slice. I stay there so I am not also maintaining a rice.

A beautiful cage is sometimes the product constraint. NeuroShell is a macOS terminal. That work lives under Apple’s notarization and Gatekeeper rules whether or not my writing laptop runs Fedora. Linux as a stance does not require Linux as every ship target. It requires honesty about which machines you govern and which machines you rent.

Close

Pick a distro the way you pick a constitution: readable rules, a known update cadence, a story for disaster recovery that does not include a store chat. Fedora is my current vote. The kernel remains a commons either way. The stance is whether you treat that as a consumer detail or as the reason the machine is yours.

When the Auckland move lands, I want the same kernel docs, the same unit files, the same git remotes. Wallpaper can change. Policy should travel.

— JV · Dark Heart Labs.

References

The Linux Kernel documentation, https://docs.kernel.org/. In-tree docs for subsystems, admin guides, and development process. ↩
Debian Policy Manual, https://www.debian.org/doc/debian-policy/. Packaging, dependencies, and what the archive will carry: a distro as written policy. ↩
systemd project documentation, https://systemd.io/. Pid 1, unit files, journaling, and cgroup integration: the artifact the init wars were about. ↩