aerynOS has advanced its new installer with Btrfs support and rebuilt its entire package repository.

The second item is the one that deserves attention. Rebuilding every package in a distribution is not routine maintenance.

Why a full rebuild is a big deal

A distribution’s repository is the accumulated output of thousands of builds, each produced by a specific toolchain against a specific set of dependencies at a specific point in time. Over months that becomes archaeology: packages built against different compiler versions, different library ABIs, and different build flags, all coexisting and mostly working.

Rebuilding everything from scratch gives you one consistent state. Every package built with the same toolchain, the same hardening flags, the same optimisation settings, against the same library versions.

The reasons a project does this:

Toolchain migration. A new GCC or LLVM version, or a change of C library, requires a rebuild for consistency and to catch packages that no longer compile.

Build flag changes. Enabling hardening, changing optimisation, or altering the ABI baseline means existing binaries do not match the new policy.

Reproducibility work. Verifying that packages build deterministically requires actually building them.

Finding the rot. A full rebuild surfaces every package that has quietly stopped compiling, which is information a project otherwise lacks.

It is also days or weeks of compute and a great deal of fixing things that break, which is why most distributions do it rarely and deliberately.

The installer and Btrfs

Btrfs support in an installer means more than selecting a filesystem. Done properly it means the subvolume layout is configured correctly from the start, which is what makes snapshots useful.

The layout matters because a snapshot of the whole filesystem including /home is not what you want. The conventional arrangement separates the root subvolume from /home, so a system snapshot can be rolled back after a bad update without reverting the user’s documents to yesterday.

Getting that right at install time is considerably easier than reorganising it later. Our Btrfs snapshots explainer covers the arrangement and why it is worth having.

aerynOS and Ikey Doherty

aerynOS is the continuation of the Serpent OS work by Ikey Doherty, who previously created Solus. It is genuinely independent, not a reskin of Arch or Debian, with its own package manager and build tooling.

We covered the August updates recently. The pace has been steady, which for an independent distribution built by a small group is the hard part, since the effort required to maintain one from scratch is the reason there are so few.

Doherty has also just introduced another project, Barney, which is worth noting mainly because his track record means new projects from him tend to be technically interesting even when their longevity is uncertain.

Independent distributions matter disproportionately. The Linux ecosystem has enormous apparent variety and a small number of actual bases, and almost everything is downstream of Debian, Fedora, Arch, or SUSE. Projects that build their own tooling are where genuinely different ideas about packaging and system management get tried.