What is this?
Source code for the 'Writing an OS in Rust' blog series at os.phil-opp.com - step-by-step posts that build a small x86-64 operating system kernel in Rust.
Source code for the 'Writing an OS in Rust' blog series at os.phil-opp.com - step-by-step posts that build a small x86-64 operating system kernel in Rust.Is it just a blog, or do I get runnable code too?Both: every post on the site comes with its own working code, stored in a separate git branch of this repo, so you can run the exact code state described in that post.
Both: every post on the site comes with its own working code, stored in a separate git branch of this repo, so you can run the exact code state described in that post.How do I get the code for a specific post?Follow the (source code) link next to a post, or check out its branch directly - branches are named post-XX (post-03 is VGA Text Mode, post-07 is Hardware Interrupts). Build instructions are in each branch's own README.
Follow the (source code) link next to a post, or check out its branch directly - branches are named post-XX (post-03 is VGA Text Mode, post-07 is Hardware Interrupts). Build instructions are in each branch's own README.Is the series finished?It is still a work in progress: the second edition has 12 posts and currently ends with Async/Await in the Multitasking section. The older first edition is no longer maintained.
It is still a work in progress: the second edition has 12 posts and currently ends with Async/Await in the Multitasking section. The older first edition is no longer maintained.Do I need to know Rust before starting?The posts are step-by-step, but you write Rust from the very first one ('A Freestanding Rust Binary'), so basic Rust knowledge is effectively required. OS-development concepts themselves are taught from zero.
The posts are step-by-step, but you write Rust from the very first one ('A Freestanding Rust Binary'), so basic Rust knowledge is effectively required. OS-development concepts themselves are taught from zero.Where does the resulting OS actually run?The kernel targets x86-64 bare metal - it runs directly on hardware or in an emulator like QEMU, not inside an existing OS like Linux or Windows.
The kernel targets x86-64 bare metal - it runs directly on hardware or in an emulator like QEMU, not inside an existing OS like Linux or Windows.Can I reuse the code in my own projects?Yes - the code is dual-licensed under Apache-2.0 and MIT, so you can pick either. The blog/content folder is licensed separately (see blog/content/README.md).
Yes - the code is dual-licensed under Apache-2.0 and MIT, so you can pick either. The blog/content folder is licensed separately (see blog/content/README.md).What topics do the posts cover?Four sections: Bare Bones (freestanding binary, minimal kernel, VGA text mode, testing), Interrupts (CPU exceptions, double faults, hardware interrupts), Memory Management (paging, heap allocation, allocator designs) and Multitasking (async/await).
Four sections: Bare Bones (freestanding binary, minimal kernel, VGA text mode, testing), Interrupts (CPU exceptions, double faults, hardware interrupts), Memory Management (paging, heap allocation, allocator designs) and Multitasking (async/await).Where should a beginner start?At the first Bare Bones post, 'A Freestanding Rust Binary'. Posts build on each other in order, and each one has a matching post-XX branch in this repo with its code.
At the first Bare Bones post, 'A Freestanding Rust Binary'. Posts build on each other in order, and each one has a matching post-XX branch in this repo with its code.Can I keep several posts' code side by side without switching branches?Yes - the README suggests git worktree, which checks a branch out into a subdirectory; the example command puts the code for post-10 (Heap Allocation) into a folder named code.
Yes - the README suggests git worktree, which checks a branch out into a subdirectory; the example command puts the code for post-10 (Heap Allocation) into a folder named code.Why does GitHub list the language as HTML if this is a Rust OS?The repo root hosts the blog site itself; the actual Rust kernel code lives in the per-post branches, so the main page shows the website rather than the kernel sources.
The repo root hosts the blog site itself; the actual Rust kernel code lives in the per-post branches, so the main page shows the website rather than the kernel sources.What are similar projects?lytlnyblOS, How-to-Make-a-Computer-Operating-System, os01, os-tutorial, raspberry-pi-os, linux-insides, vinix, reactos
lytlnyblOS, How-to-Make-a-Computer-Operating-System, os01, os-tutorial, raspberry-pi-os, linux-insides, vinix, reactosWhich topics is it in?assembly-language, osdev, qemu, x86-64, blog, operating-system, kernel, low-level, systems-programming, async, course, computer-science
assembly-language, osdev, qemu, x86-64, blog, operating-system, kernel, low-level, systems-programming, async, course, computer-science