Skip to content

Package repository · Saphira D

Hatched

The first Saphira D system hatched from Hatchling. The same Saphira base, now breathing with systemd on musl, proved in the nest and now flying.

Saphira Linux dragon mascot

What Hatched is

Hatched is the first Saphira D system produced through the new generation of Saphira packaging work. It runs systemd 261.2 on musl libc with Saphira's true non usr merged filesystem. It came from the Hatchling, which came from the Egg, which came from the first Dragon. One circle, closed and then opened again.

This is still Saphira. The base is the same musl userspace and the same triple x86_64-saphira-linux-musl, the same layout with /bin and /sbin distinct. What changes is how the system wakes: OpenRC or systemd. The dragon is the same, the way it rises is different.

What this means

With Hatched in view, the main, latest and hatchling streams and the systemd units become the practical surface. The package streams describe where packages live, and the systemd unit pages provide the concrete files:

The default Saphira design uses OpenRC. Saphira D is the systemd variant born from Hatchling, a musl and systemd sibling experiment to test whether the same Saphira philosophy survives a different init and service layer. OpenRC need not lose for Saphira D to succeed, nor vice versa. A systemd boot can still fall back to OpenRC until those scripts are removed, which shows how thin the difference is. The systemd 261.2 port behind Hatched was built to preserve Saphira's true non merged layout, keeping kmod, mount and umount in /bin and sulogin, swapon, swapoff, agetty and nologin in /sbin.

A note on status

Hatched is the current edge of what is proven. The systemd bootstrap image has shipped and been boot proven, a release QCOW2 with an upgrade guide accompanies it, and the first natively built packages (openssh and chrony among them) are already serving from this generation. The systemd and udev split has been tested as a strict complement, keeping kmod, mount, umount and friends exactly where Saphira expects them.

Work continues in the open rather than being declared done: kernel BPF support for systemd firewalling is being rolled forward, and further validation runs before anything here is claimed finished. The next step in the circle, Spawn of Saphira, is the self hosting stage where Saphira rebuilds Saphira from itself. It is described on its own page and is not claimed as complete until it is genuinely proven. The Egg hatched. The Dragon flies. Whether it can make another of itself without help is the next turn.

Continue to Spawn of Saphira, return to Hatchling or the package repository.