phil-opp / blog_os

Writing an OS in Rust
http://os.phil-opp.com
Apache License 2.0
15.82k stars 1.09k forks source link
kernel operating-system rust x86-64

Blog OS

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 post-XX where 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").

Posts

The goal of this project is to provide step-by-step tutorials in individual blog posts. We currently have the following set of posts:

Bare Bones:

Interrupts:

Memory Management:

Multitasking:

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:

Click to expand **Bare Bones:** - [A Minimal x86 Kernel](https://os.phil-opp.com/multiboot-kernel.html) ([source code](https://github.com/phil-opp/blog_os/tree/first_edition_post_1)) - [Entering Long Mode](https://os.phil-opp.com/entering-longmode.html) ([source code](https://github.com/phil-opp/blog_os/tree/first_edition_post_2)) - [Set Up Rust](https://os.phil-opp.com/set-up-rust.html) ([source code](https://github.com/phil-opp/blog_os/tree/first_edition_post_3)) - [Printing to Screen](https://os.phil-opp.com/printing-to-screen.html) ([source code](https://github.com/phil-opp/blog_os/tree/first_edition_post_4)) **Memory Management:** - [Allocating Frames](https://os.phil-opp.com/allocating-frames.html) ([source code](https://github.com/phil-opp/blog_os/tree/first_edition_post_5)) - [Page Tables](https://os.phil-opp.com/modifying-page-tables.html) ([source code](https://github.com/phil-opp/blog_os/tree/first_edition_post_6)) - [Remap the Kernel](https://os.phil-opp.com/remap-the-kernel.html) ([source code](https://github.com/phil-opp/blog_os/tree/first_edition_post_7)) - [Kernel Heap](https://os.phil-opp.com/kernel-heap.html) ([source code](https://github.com/phil-opp/blog_os/tree/first_edition_post_8)) **Exceptions:** - [Handling Exceptions](https://os.phil-opp.com/handling-exceptions.html) ([source code](https://github.com/phil-opp/blog_os/tree/first_edition_post_9)) - [Double Faults](https://os.phil-opp.com/double-faults.html) ([source code](https://github.com/phil-opp/blog_os/tree/first_edition_post_10)) **Additional Resources:** - [Cross Compile Binutils](https://os.phil-opp.com/cross-compile-binutils.html) - [Cross Compile libcore](https://os.phil-opp.com/cross-compile-libcore.html) - [Set Up GDB](https://os.phil-opp.com/set-up-gdb) - [Handling Exceptions using Naked Functions](https://os.phil-opp.com/handling-exceptions-with-naked-fns.html) - [Catching Exceptions](https://os.phil-opp.com/catching-exceptions.html) ([source code](https://github.com/phil-opp/blog_os/tree/catching_exceptions)) - [Better Exception Messages](https://os.phil-opp.com/better-exception-messages.html) ([source code](https://github.com/phil-opp/blog_os/tree/better_exception_messages)) - [Returning from Exceptions](https://os.phil-opp.com/returning-from-exceptions.html) ([source code](https://github.com/phil-opp/blog_os/tree/returning_from_exceptions))

License

This project, with exception of the blog/content folder, is licensed under either of

at your option.

For licensing of the blog/content folder, see the blog/content/README.md.

Contribution

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.