Akadata Linux · Version 0 Saphira

About Akadata Linux

The design principles, filesystem contract, and privilege boundaries behind the distribution.

Technical preview

Why it exists

Ownership all the way down

Akadata Linux is a from-source distribution for operators who want to understand and reproduce the complete system. Pinned archives and a fixed epoch replace an opaque prebuilt cache.


Traditional filesystem contract

Akadata is deliberately non-usrmerged. /bin, /sbin, /lib, /usr/bin, and /usr/sbin remain distinct directories.

  • Early-boot OpenRC programs remain in /sbin.
  • Service scripts use #!/sbin/openrc-run.
  • /etc/mtab resolves to /proc/self/mounts.
  • No BusyBox multicall binary replaces the selected userland tools.

Privilege and provenance

Compilation runs as the invoking builder. Root privilege is restricted to installation into the target rootfs; installed files become root:root while source and build trees stay builder-owned.

Completion markers are accepted only with matching policy and Stage2-input fingerprints. A failed unit cannot write successful completion evidence.


Akadata Linux releases

Akadata Linux is one deliberately simple server operating system. Every release uses musl libc, OpenRC, a proper non-usrmerged filesystem and an x86-64-v3 baseline.

Release names come from dragons. They do not represent editions, performance tiers, storage roles or specialised products.

  • Version 0 — Saphira: The first Akadata Linux release.
  • Version 1 — Vermithrax: Planned release name.
  • Version 2 — Ancalagon: Planned release name.
  • Version 3 — Smaug: Planned release name.

Each release advances the same focused system: simple, source-built and designed for modern x86-64 servers.

The architecture and build documentation are public now. Images remain gated until acceptance, measured sizes, checksums, detached signatures, signing identity, and release notes agree.

View release status