This repository contains the source code for the Writing an OS in Rust series at os.phil-opp.com.
If you have questions, open an issue or chat with us on Gitter.
Where is the code?
The code for each post lives in a separate git branch. This makes it possible to see the intermediate state after each post.
The code for the latest post is available here.
You can find the branch for each post by following the
(source code) link in the post list below. The branches are named
XX is the post number, for example
post-03 for the VGA Text Mode post or
post-07 for the Hardware Interrupts post. For build instructions, see the Readme of the respective branch.
You can check out a branch in a subdirectory using git worktree:
git worktree add code post-10
The above command creates a subdirectory named
code that contains the code for the 10th post ("Heap Allocation").
The goal of this project is to provide step-by-step tutorials in individual blog posts. We currently have the following set of posts:
- A Freestanding Rust Binary (source code)
- A Minimal Rust Kernel (source code)
- VGA Text Mode (source code)
- Testing (source code)
- Introduction to Paging (source code)
- Paging Implementation (source code)
- Heap Allocation (source code)
- Allocator Designs (source code)
First Edition Posts
The current version of the blog is already the second edition. The first edition is outdated and no longer maintained, but might still be useful. The posts of the first edition are:
- A Minimal x86 Kernel (source code)
- Entering Long Mode (source code)
- Set Up Rust (source code)
- Printing to Screen (source code)
- Allocating Frames (source code)
- Page Tables (source code)
- Remap the Kernel (source code)
- Kernel Heap (source code)
- Cross Compile Binutils
- Cross Compile libcore
- Set Up GDB
- Handling Exceptions using Naked Functions
This project, with exception of the
blog/content folder, is licensed under either of
- Apache License, Version 2.0 (LICENSE-APACHE or https://www.apache.org/licenses/LICENSE-2.0)
- MIT license (LICENSE-MIT or https://opensource.org/licenses/MIT)
at your option.
For licensing of the
blog/content folder, see the
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.