Philipp Oppermann 381627bbbb Delete code from master branch
The code for each post now lives in the `post-XX` branches where `XX` is the post number.
2019-02-08 10:19:13 +01:00
2019-02-08 10:19:13 +01:00
2019-02-08 10:19:13 +01:00
2019-02-08 10:19:13 +01:00
2018-10-20 18:33:41 +02:00
2019-01-22 16:58:55 +01:00
2019-02-08 10:19:13 +01:00
2018-01-19 14:49:04 +01:00

Blog OS

Build Status Join the chat at https://gitter.im/phil-opp/blog_os

This repository contains the source code for the Writing an OS in Rust series at os.phil-opp.com.

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. 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 third post ("VGA Text Mode").

You can find the code for the latest post here.

For build instructions, see the Readme of the post branches.

Checking out the Code in a Subdirectory

To check out the code in a subdirectory use git worktree:

git worktree add code post-10

This creates a subdirectory named code that contains the code for the latest post ("Advanced Paging").

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

Testing

Interrupts

Memory Management

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:

Bare Bones

Memory Management

Exceptions

Additional Resources

License

The source code is dual-licensed under MIT or the Apache License (Version 2.0). This excludes the blog directory.

Description
Languages
HTML 96.5%
SCSS 1.5%
CSS 1.2%
JavaScript 0.4%
Python 0.2%