Where most of the rust thoughts go Wiki
Follow Brown Rust Book: https://rust-book.cs.brown.edu/ch04-02-references-and-borrowing.html
Rust for rustasceans: rust for rustasceans
For each concept:
read → implement → test → fix → repeat
Also play Turing Complete for hardware intuition.
- Memory map iterator
- ELF header parser
- Page table entry (bitflags)
- Bump allocator
- Slab allocator
- Packet parser (Ethernet/IP)
- Virtual file table (inode style)
If I can write these confidently → I’m ready for kernel subsystems.
Testing is the real skill I’m learning.
Kernel developers debug with invariants, not print statements.
Always keep a watcher running:
cargo install cargo-watch
cargo watch -x test
Workflow:
save file → tests run → fix immediately
Never continue while tests are red.
Run a single test:
cargo watch -x "test <name>"
Run all tests:
just test
Run one:
just t read_one
Auto-test on save:
just watch
Fast checks:
just check
just clippy
Deep debugging:
just miri
- memory layout
- aliasing
- lifetimes
- binary parsing
- allocators
- resource tracking