Orientation
Can we build a full, performant, general-purpose OS that is mathematically proven correct — and do it for a world where AI models are a managed system resource like memory or CPU?
What it unlocks
Every other field runs on an OS. Advances here mean more secure devices (memory-safe kernels kill whole classes of exploits), better battery life and performance (smarter scheduling for heterogeneous chips), and new computing paradigms — the OSes for spatial computing, for AI-as-a-system-resource, and eventually for quantum and neuromorphic machines all have to be invented.
Where we are now
As of 2026 the frontier is memory-safe kernels (Rust in Linux and Windows), AI as a first-class OS resource (Microsoft's Windows AI Runtime / HAIEnv announced at Build 2026), and capability-based microkernels (seL4, Google's Fuchsia/Zircon shipping in real devices). The general-purpose desktop OS is a solved product; the live research is in security, verification, and rethinking the OS for AI and new hardware.
How it began
Early machines ran one program at a time, loaded by hand. As compute got expensive, batch systems and then time-sharing (letting many users share one machine) drove the first real OSes. Unix (1969, Bell Labs) crystallized the ideas that still dominate: everything is a file, small composable tools, a portable kernel written in C. Almost everything since is a variation on, or reaction to, Unix.
- 1969 — Unix at Bell Labs (Thompson, Ritchie)
- 1985 — Windows; 1987 — MINIX (teaching OS)
- 1991 — Linux kernel released by Linus Torvalds
- 2007 — iOS; 2008 — Android (both Unix-lineage)
- 2009 — seL4: first formally-verified kernel
- 2020s — Rust enters the Linux & Windows kernels for memory safety
The Journey
Prerequisites
- 1
Beginner
1–3 months alongside other studyYou understand processes, threads, virtual memory, and syscalls as a user of the OS. You can write multi-threaded programs, reason about deadlocks, and use strace/dtrace to watch what the kernel does.
- ▸Read & internalize OSTEP (the free textbook)
- ▸Write a shell that handles pipes and job control
- ▸Use strace/ltrace to trace a real program's syscalls
- 2
Intermediate
3–6 months of focused hobby workYou can write a tiny kernel that boots on QEMU: it prints to screen, handles a keyboard interrupt, sets up paging, and switches between two tasks. You understand the bootloader → kernel handoff.
- ▸Boot a 'hello world' kernel in QEMU
- ▸Implement interrupt handling and a basic memory allocator
- ▸Cooperative multitasking between two processes
- 3
Advanced
1–2 years of serious workYou contribute to a real kernel (Linux, BSD, Redox) or build a hobby OS with a filesystem, preemptive scheduling, and userspace programs. You can read and reason about real driver code and subsystem internals.
- ▸Land a patch in the Linux kernel or a BSD
- ▸Write a working filesystem and a device driver
- ▸Port your OS to real hardware, not just an emulator
- 4
Too Advanced
Many years; usually a PhD or deep industry trackYou work on kernel subsystems professionally or research novel OS architectures — formal verification (seL4-style), new isolation models, schedulers for heterogeneous or AI hardware, or unikernels.
- ▸Co-author an OSDI/SOSP paper
- ▸Maintain a kernel subsystem
- ▸Design a novel scheduler or memory model
- 5
Beyond
Career-defining, field-shaping workYou invent the OS for a paradigm that doesn't have one yet — AI-native kernels where a model is the scheduler, OSes for quantum or neuromorphic substrates, or fully-verified systems that close the gap between 'tested' and 'proven'.
- ▸Define a category, not just a product
- ▸Verified general-purpose OS at scale
- ▸An OS where AI is a managed resource end-to-end
AI's Role
Two directions. First, AI as a tool to build OSes — scaffolding drivers, parsing kernel panics, generating tests, porting code between architectures. Second, and bigger, AI as something the OS must now manage: local model catalogs, shared inference runtimes (Windows AI Runtime), and scheduling that predicts user intent rather than round-robining blindly.
What AI still can't do
AI cannot be trusted to write kernel code unreviewed — a plausible-looking off-by-one or race condition means data corruption or a panic, not a red squiggle. Hardware-specific assembly and novel architecture decisions still require deep human understanding.
The AI-native future
A kernel that uses a learned model to schedule processes by predicted intent, pre-warms apps before you switch to them, manages AI models as first-class resources alongside RAM and CPU, and reasons about security in terms of whether an action makes sense rather than static permission bits.
Doing the Work
Tools & stack
Cost to start
$0 — everything runs in QEMU on the laptop you already own.
Cost to go deep
Low. A Raspberry Pi or cheap RISC-V board (~$10–80) to run your OS on real hardware; otherwise it stays a software-only pursuit.
Projects ladder
Build a Unix shell
Handle pipes, redirection, background jobs, and signals. Teaches processes and syscalls intimately.
Implement a memory allocator
Write your own malloc/free. Forces you to understand the heap.
Boot a kernel in QEMU
Bootloader → kernel handoff, VGA text output, keyboard interrupt, paging. The classic rite of passage.
Cooperative multitasking
Two tasks yielding to each other via a context switch you wrote by hand.
Filesystem + driver
A working FS and a real device driver, then port to a Raspberry Pi.
Land a Linux kernel patch
Fix a real bug or driver issue and get it merged upstream.
Where to practice
- ·QEMU / Bochs emulators
- ·The OSDev Wiki tutorials
- ·Writing an OS in Rust (Philipp Oppermann's blog series)
- ·xv6 — MIT's teaching OS you can read end-to-end
- ·Linux kernel via a VM + KGDB
People & Community
People to know
Created Unix and C
Created Linux and Git
MINIX; foundational OS textbooks
Led seL4, the first verified kernel
Authored OSTEP, the field's best free textbook
Reverse-engineered Apple Silicon for Linux (Asahi)
Institutions & labs
- ·MIT PDOS, Stanford, UW, UC Berkeley (systems groups)
- ·Linux Foundation; the kernel mailing list (LKML)
- ·Microsoft Research, Google (Fuchsia), Apple
- ·Data61 / CSIRO (seL4)
Where the field gathers
- ·OSDI & SOSP (the top OS research conferences)
- ·EuroSys, USENIX ATC, HotOS
- ·Linux Plumbers Conference, FOSDEM
Communities
Voices to follow
- OSDev Wiki ↗
The hobbyist OS bible.
- Writing an OS in Rust ↗ · Philipp Oppermann
The best modern from-scratch tutorial.
- LWN.net ↗
Deep, authoritative Linux kernel news.
Start on the OSDev Wiki, get a 'hello world' kernel booting in QEMU, and hang out in r/osdev and the OSDev Discord posting your progress. To go pro, pick a 'good first issue' on the Linux kernel or a BSD and submit a patch — the mailing-list review will teach you more than any course.
Career & Economics
Roles
Who hires
Apple, Microsoft, Google, Amazon, NVIDIA, Qualcomm, Red Hat, chip and embedded companies, and any firm with serious infrastructure or hardware.
Compensation reality
Among the best-paid software niches because the talent pool is small and the work is hard. Senior kernel/systems engineers command top-of-band compensation; it rewards depth over breadth.
Funding landscape
Mostly big-company and open-source rather than startups, though OS-adjacent startups (unikernels, confidential computing, novel runtimes, AI-OS infrastructure) get funded in waves.
Is It For You?
You'll love it if
- ✓You want to know how things really work, all the way down
- ✓You enjoy debugging with almost no safety net
- ✓Elegant abstractions over messy hardware delight you
- ✓You're patient and methodical
You'll bounce off it if
- ✕You want fast visible results and quick feedback loops
- ✕Debugging triple-faults and silent memory corruption sounds miserable
- ✕You prefer building user-facing features
Day in the life
Reading dense subsystem code, reproducing a heisenbug that only appears under specific timing, staring at register dumps and page tables, writing careful patches, and arguing correctness on a mailing list. Long stretches of deep focus punctuated by the rush of finally understanding why the machine did what it did.
Hobby · career · calling
A fantastic hobby for the deeply curious (a booting toy kernel is a lifetime achievement), a lucrative and durable career for the patient, and a calling for the few who want to invent the OSes of paradigms that don't exist yet.
Learn It
Books
- Operating Systems: Three Easy Pieces (OSTEP) ↗ · Arpaci-Dusseau
Free, and the best starting point.
- xv6 book · MIT
A complete, readable teaching OS.
- Modern Operating Systems · Tanenbaum
The classic comprehensive text.
Courses
- MIT 6.1810 (Operating System Engineering)
Build on xv6; materials are public.
- Georgia Tech OMSCS — Advanced Operating Systems
Graduate-level, accessible online.
Papers
- The UNIX Time-Sharing System (1974) · Ritchie & Thompson
- seL4: Formal Verification of an OS Kernel (2009)
The verification landmark.
OSTEP (free) → Philipp Oppermann's 'Writing an OS in Rust' (free) → MIT 6.1810 labs on xv6 (free) → a 'good first issue' on the Linux kernel. Total cost: $0.
Connections
Intersections it spawns
Reality Check
Hype vs reality
Less hype than AI, more permanence. Nobody's promising OS dev will make you rich overnight, but the skills compound for decades and never go stale — the fundamentals from 1974 still apply.
Why people quit
The feedback loop is brutal at first: a single wrong byte gives you a silent reboot with no error message. Many bounce off the early difficulty before the mental model clicks.
Controversies
The C-vs-Rust kernel debate is genuinely heated (memory safety vs. decades of C culture). Open-source governance and corporate influence over Linux are perennial tensions.
Geographic hubs
More charted domains