Archives
/
cfenollosa_os-tutorial
mirror of https://github.com/cfenollosa/os-tutorial
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'f67abb437d'
${ noResults }
cfenollosa_os-tutorial/README.md

2.1 KiB
Raw Blame History

os-tutorial

How to create an OS from scratch!

I have always wanted to learn how to make an OS from scratch. In college I was taught how to implement advanced features (pagination, semaphores, memory management, etc) but:

  • I never got to start from my own boot sector
  • College is hard so I don't remember most of it.

Inspired by this document and the OSDev wiki, I'll try to make short step-by-step READMEs and code samples for anybody to follow.

Features

  • This course is a code tutorial aimed at people who are comfortable with low level computing.
  • There is little theory. Yes, this is a feature. Google is your theory lecturer.
  • The lessons are tiny and may take 5-15 minutes to complete. This is the only way to learn. Grabbing a whole OS, even if small like Minix or TempleOS, is too overwhelming.
  • New lessons will be added about every week, at the same pace that I learn the concept

How to use this tutorial

  1. Start with the first folder and go down in order. They build on previous code, so if you jump right to folder 08, you may find a lot of stuff which is not related to what folder 08 is about.

  2. Read each README first. Especially the first line, which details the concepts you should be familiar with before reading the code.

  3. Read the README. It is very concise. The only theory is the required to understand the code and there are tips on what to look at when you open the code file(s)

  4. Look at the code examples. Some times you may be able to write them yourself just from the hints on the README.

  5. Experiment with them and try to break things. Try to change pointers and registers and see what happens. You know, the usual.

TL;DR: First read the README on each folder, then decide if you will implement it yourself or just read the provided code files.

Contributing

I'm still learning this. For the moment, please restrict your contributions to fixing possible bugs or improving existing documents. I'm not yet ready to accept enhancements.