About Daxo OS

History

Daxo OS began as a learning project following the famous “Writing an OS in Rust” tutorial by Philipp Oppermann. I started from the very first boot sector and gradually built each component: VGA output, interrupt handling, memory paging, and heap allocation – step by step, line by line.

After reaching the basic multitasking skeleton, I decided to go far beyond the tutorial. I added:

  • A custom PIO ATA driver to read raw disk sectors
  • A simple FAT‑like file system built on top of the ATA driver
  • A cooperative async task executor with full `Future`/`Waker` support
  • Hardware privilege switching (Ring 0 → Ring 3) with isolated user pages
  • Formal verification of the frame allocator in Lean 4
  • A domain‑specific language (DSL) and an AOT compiler to WebAssembly
  • Full integration with the microkernel.info registry

So while the initial inspiration came from the tutorial, Daxo OS today is an independent, feature‑rich microkernel that reflects my own design decisions and engineering work.

Motivation

The best way to understand a computer is to write software that runs directly on its hardware. Daxo OS serves as an educational sandbox for low‑level systems programming, exploring memory protection, interrupt handling, hardware drivers, and formal methods. It also experiments with building a self‑hosting compiler toolchain.

Team

Currently, Daxo OS is a solo project by Daxo Developer (13 years old). Contributions are welcome via GitHub.

Roadmap

  • v0.3.0 – Simple file system (FAT‑like) on top of the ATA driver. (Completed)
  • v0.4.0 – Multi‑process support with context switching and IPC.
  • v0.5.0 – TCP/IP stack for networking.
  • v1.0.0 – A minimal but usable OS with a shell and utilities.

Philosophy

Keep it simple, keep it verifiable. The kernel should be small enough to reason about formally, yet powerful enough to run interesting user programs. Abstractions are welcome only if they don’t hide the hardware.