Skip to content

AriCodeOS 0.14.0

Choose a tag to compare

@Lynx-Boss Lynx-Boss released this 24 Oct 18:00
· 519 commits to main since this release

AriCodeOS 0.14.0 (2026-10-24): the system leaves the LAN. Machines update from this project's GitHub releases over HTTPS, a development channel puts a build on real hardware in minutes, and SSH sessions see what their programs print. Each fix was reproduced before it was changed, kernel, IPC, network and update changes were audited by independent reviewers, and everything below was run on the reference laptop.

Website: https://www.aricodeos.org/ · Master document: AriCodeOS.md, section 94.14.

What is new

  • Public updates (ADR 0048): the updater follows HTTPS redirects (at most five, never from https to http) and accepts the larger headers GitHub sends, so a machine updates from https://github.com/AriCodeLabs/AriCodeOS/releases/latest/download/. This release is the first to carry that source: its stick registers it, and its update files (index, index.sig, aricodeos-14.img) are attached here, signed with the release key. cargo xtask serve-update serves the same path and redirects locally, for tests that need nothing published.
  • Development channel (ADR 0045): update --channel dev / upgrade --channel dev install a signed build of develop or a branch, named by build number and commit, on a machine whose stick opted in; update rollback goes back to the other slot; a stable floor keeps released machines from going below the newest release they ran.
  • Updates that scale: installed images are verified piece by piece up to the slot size, and update apply verifies the copy in the slot before it can boot (incident 0021); one package limit for the whole system, said as such when exceeded (incident 0026).
  • SSH sessions (ADR 0047): programs started from an SSH shell (run bench, the updater) write to the session, through a console object that can only write text; sshd applies flow control.
  • Randomness: diag names what seeded the kernel generator (ADR 0039), and the loader carries a seed across boots, so a machine without rdrand is strongly seeded from its second boot (ADR 0043).
  • Responsiveness: services wait on IPC, interrupt lines and a deadline at once (ADR 0044, ABI 6); a network query went from about 10 ms to 70 µs and the USB controller lost its polling. The compositor repaints only what changed (ADR 0046).
  • Network robustness: a full TCP table recycles connections waiting out TIME-WAIT, and a peer that never closes its side is reset after 30 s (incident 0027).

Trying it

  • USB stick (aricodeos-0.14.0-usb.img.xz, attached; xz -d it first): write it to a stick you can wipe and boot a UEFI x86-64 machine with Secure Boot off; see docs/hardware.md. Check it against SHA256SUMS. Once it has network, update and upgrade fetch from this page. Machines on 0.13.0 or older cannot follow GitHub's redirects: write the 0.14.0 stick.
  • Docker: docker run --rm -it ghcr.io/aricodelabs/aricodeos:0.14.0 boots it in QEMU (quit with Ctrl-A X).

Signed with the project's release key, fingerprint 1d3e24f3c7c753a5bcb384041ace6481736decd86345eab71e2a6ff410ad446e (keys/release/).

Known open items

System image downloads above 6 MiB (the release image is 3.1 MB) and applications above 32 KiB (AriFS file size) need design decisions; one SSH command that once came back empty was never reproduced (incident 0025); EHCI hubs and split transactions are only verifiable on hardware.