From 3110d1ed478033b0ad381510d723804d5c5674c0 Mon Sep 17 00:00:00 2001 From: Carlos Fenollosa Date: Mon, 29 Sep 2014 11:51:49 +0200 Subject: [PATCH] boot sector with interrupts --- 00-environment/README.md | 2 +- README.md | 14 +++++++++++--- 2 files changed, 12 insertions(+), 4 deletions(-) diff --git a/00-environment/README.md b/00-environment/README.md index fd85aaa..b4c0da6 100644 --- a/00-environment/README.md +++ b/00-environment/README.md @@ -6,4 +6,4 @@ On a mac, [install Homebrew](http://brew.sh) and then `brew install qemu nasm` Don't use the Xcode developer tools `nasm` if you have them installed, they won't work for the most cases. Always use `/usr/local/bin/nasm` Furthermore, on a mac, qemu is split into multiple binaries. You will want -to call `qemu-system-x86_84 *binfile*` +to call `qemu-system-x86_84 binfile` diff --git a/README.md b/README.md index 91a7472..5dc4765 100644 --- a/README.md +++ b/README.md @@ -14,9 +14,14 @@ Inspired by [this document](http://www.cs.bham.ac.uk/~exr/lectures/opsys/10_11/l and the [OSDev wiki](http://wiki.osdev.org/), I'll try to make short step-by-step READMEs and code samples for anybody to follow. -I will not explain the theory. Google is your friend. Learn what assembler is, pagination, interrupts, -segmentation, etc. That is already covered by thousands of PDFs from Universities. This course -is a tutorial, a hands-on, not a real CS lecture. +I will not explain the theory. Google is your friend. +Theory is already covered by thousands of PDFs from Universities +and the Wikipedia. + +This course is a code tutorial, not a real CS lecture. +To make up for the lack of theory, the "lessons" are tiny +and may take 5-15 minutes to complete. Each new concept +is presented on a new lecture. How to use this tutorial @@ -28,6 +33,9 @@ to what folder 08 is about. To see the increments between "lessons", do a diff between folders. +Each lesson README starts with the concepts you should be familiar with +before reading the code. + Second, for each folder, read the README. It is **very concise**. The only theory. is the required to understand the code. Then, look at the code examples. You can try to write them by