ABSD — An experimental operating system.
ABSD is a small operating system written in Rust. It boots under QEMU, runs isolated processes, keeps files across reboots, and is administered over stock OpenSSH. Its userspace includes a shell, commands, manual pages, and some unmodified Rust programs.
Try ABSD
ABSD Developer Preview 2 (state published): Download / Try ABSD on a Linux x86-64 host with QEMU, with no build tools. The matching first-party source records its reconstruction instructions and limits. Status keeps the earlier source release separate.
ABSD is experimental, single-operator software, not ready for production. SSH sessions share the operator's files; they are not separate user accounts. No physical hardware is supported. How sessions are isolated.
There is no fork, no user IDs, and existing Unix or Linux software needs porting. The published developer previews have no staged upgrade or rollback; a newer preview requires a new machine. Read the selected release's instructions and limits before running it.
One developer directs the work. AI coding agents wrote most of the code, tests, documentation and reviews; no independent human audit has been done. How ABSD is developed.
Release records
What distinguishes it
- Isolation
- Every program is a separate process in its own address space, started by spawn; there is no
fork. A process can act only on itself and its own children; a few whole-system counts are readable by any process. Design: spawn, not fork. - Explicit authority
- A process can touch only what it was handed: handles to kernel objects, each carrying rights that can be dropped and never added. There are no user IDs and no ambient privilege. This is the capability model of earlier systems, not a new invention. Design: handles and rights.
- Bounded scheduling and recovery
- Bounds are fixed limits, not timing guarantees: 16 processes in the whole system and four SSH connections by default. Processes are preempted by a timer; the experimental periodic scheduling class has no real-time guarantee. Failure handling and its evidence depend on the revision. Design: replacement is not recovery.
- Evidence-oriented engineering
- Claims on the status, design, hardware, and evidence pages carry a label saying how strongly each is supported, in which environment, and where the claim stops. Failed runs stay on record. How statements are labelled.
Releases and evidence
The published preview, earlier qualification runs and ongoing development are separate. A result applies to the named revisions and environment; newer development does not extend a published release's capabilities or evidence.
The earlier release absd-20261003.1 was RELEASE-QUALIFIED, including host-staged update and rollback. That result does not establish those capabilities for Developer Preview 1 or Developer Preview 2. Status describes the releases and their limits; evidence records the runs, including failures.
ABSD's own source is public under Apache-2.0 at github.com/unpingable/absd; third-party material keeps its own licences. The earlier source release is absd-preview-20261010, 2026-10-10. EXPERIMENTAL-INTEGRATION Historical source-preview result, recorded 2026-10-11: built, booted and smoke-tested from a clean clone; full qualification was not established for these exact revisions. See source identities and reconstruction limits.
A session
An SSH session to the operator image, booted under QEMU from the milestone commits. The output below was captured, not written.
absd$ uname -a
ABSD x86_64 x86_64-unknown-absd pid=5
absd$ man afterboot | head
AFTERBOOT(8) System Manager's Manual AFTERBOOT(8)
NAME
afterboot -- building, booting, and checking the operator image
DESCRIPTION
This page is for the operator of an ABSD system: how to get the
operator image, boot it, check it, and look after it, and what it
cannot do yet. It describes the qualified system (see intro(1),
"QUALIFICATION"): a served `net fsd' boot under QEMU, whose file server
absd$ ps
session 1 (this session), terminal, connected 2 s
PID PROGRAM
4 /bin/absd-sh
other holders: input 0, file server channels 0
absd$ cd /home/operator
absd$ echo hello > notes.txt
absd$ cat notes.txt
hello
absd$ shutdown
ABSD is going down for halt: sessions are told and end, the file server commits and stops, then the machine halts.
absd$
sshd: the system is going down for halt; this session ends
milestone/general-usability-qemu-20260927 (kernel 1983172, platform ff025b1), QEMU TCG. Text after absd$ was typed; everything else is the system's output. A session starts in /, which sessions see read-only, hence the cd.Further reading
- About: why ABSD exists, what it is and is not for, how it is developed, and how to follow it.
- Status: what works, what has been qualified and where, what has not, and what the source release establishes.
- Design: spawn instead of fork, handles and rights, and how durability is stated.
- Manual: the 17 pages installed on the operator image, rendered from their mdoc source.
- Hardware: what has been qualified, on what, and how that will be recorded.
- Compatibility: how far unmodified Rust programs get today.
- Research program: the question ABSD tests, the method, and prior work it builds on.