- #Linux
- #Fedora
- #Arch Linux
- #Security
Distro arguments assume you get exactly one. You don't. Most people who work in tech end up with more than one machine anyway, and each of those machines has a different job.
Here's how mine split after I moved my main box to Fedora, and how to work out your own split.
The dev box: Fedora
Job: be the same machine every day, so the work gets my attention instead of the box.
That job needs consistency. Fedora gives me releases instead of a rolling stream, so it changes only when I decide it should. SELinux is enforcing by default with a maintained policy.
The bonus is that it lines up with Red Hat-family servers: dnf, RPM, the same SELinux. When something I build has to run on RHEL, it's a lot closer to working there.
The other machine: Arch
Arch is great for a box where being current matters more than being predictable. Packages show up close to how upstream wrote them, soon after they ship. The wiki is still the best Linux documentation anywhere. You build the system up from almost nothing, so you understand every piece of it.
That's the same reason it wasn't right for the dev box: a machine built to keep up with upstream is going to keep changing. Anywhere that isn't a problem, Arch is still my pick.
The airgap: Arch
Job: never touch a network.
It runs Arch, it stays on Arch, and that's the last I'll say about it here. Any detail about an airgapped machine you publish is a detail somebody else gets to plan around.
How to pick yours
For each machine you own, finish this sentence: "This machine's job is to..."
Then pick the OS by what that job needs:
| If the job needs... | Lean toward... |
|---|---|
| To match RHEL, Rocky or Alma servers | Fedora (or the RHEL clone itself) |
| To match Debian or Ubuntu servers | Debian or Ubuntu |
| Newest software, maximum control | Arch |
| Changes only when you say so | Anything with fixed releases |
| A security policy that matches production | Whatever enforces the same one (SELinux or AppArmor) |
| Offline, minimal, nothing you don't understand | Whatever you know well enough to audit |
If two machines have the same job, they should probably run the same OS. If they have different jobs, there's no rule that says they have to match.
Keep your hands the same
More than one distro sounds like a lot to keep in your head. The trick is to keep the parts you touch the same, even when the base system isn't. Put your dotfiles in git and carry your keybinds with you, and every machine feels familiar under your hands.
The full story of the move is in why my dev box runs Fedora now, and what nearly bit me on the way is in what breaks when you switch distros.
- Linux
- Fedora
- Arch Linux
- Security
