Rust, from First Line to Systems
18 of 30 labs liveStart with no Rust and finish writing the code the rest of the stack is built on.
[ the catalog ]
A path is a line. A course is a station. A lab is a tick. Solid track is built and graded today; dashed track is being laid, and says so.
Start with no Rust and finish writing the code the rest of the stack is built on.
Boot your own kernel, then teach it memory, scheduling, a filesystem, and a shell that answers you.
The same machine, in the language it was written in — boot your own kernel in C and own every byte you hand the hardware.
Build the engine under the query — pages, B-trees, and a log that survives the crash you cause on purpose.
on no line yet · no dates, no promises
one tick = one graded lab. The setup lab each course opens with is not one of them — it sits outside every count on this page.
every completion on every course is an official run of your code — earned, not self-reported.