Courses · Operating Systems in Rust
[ boot & bare metal ]From an empty disk to a kernel that catches faults and takes interrupts.
[ memory ]Own the machine's RAM — frames, page tables, then a working heap.
08The physical frame allocatorneeds a plan →09Page tables: map, translate, unmapneeds a plan →10The kernel heap: Box, Vec and Stringneeds a plan →[ scheduling ]More than one thing at a time, first by cooperation and then by force.
11Tasks & a cooperative schedulerneeds a plan →12Preemptive multitaskingneeds a plan →[ user mode ]Drop to ring 3, cross the syscall boundary, give each program its own world.
13Ring 3 & the first syscallneeds a plan →14Loading a program & per-process address spacesneeds a plan →[ filesystem ]A disk you can read, then files and directories on top of it.
15Block devices & a RAM diskneeds a plan →16VFS & SimpleFS: a real filesystemneeds a plan →[ the shell ]The part you type into — and the proof the rest of it works.
17The keyboard line editorneeds a plan →18The shell: a system you can useneeds a plan →Labs unlock as you complete them — finish one to open the next. Same checks as sboot test — we compute the verdict.
[ q ]What do I need on my machine?
The course's first lab sets up the toolchain and tells you what your machine needs — nothing to install before you start.
[ q ]What makes a verified completion meaningful?
Same checks as sboot test — we compute the verdict. That’s what makes it count.
[ q ]Who owns the code I write?
You do. sboot start unpacks it into a folder on your machine and every line stays with you.
[ q ]What does it cost?
Nothing to start — Rust for Beginners is free, every lab of it, and the first 2 labs of Rust for Systems; the rest of the catalog unlocks with a plan. See the plans for what a subscription adds; completed labs stay yours to read even if you cancel.