Browse Source

Update an example for future direction after finishing part 2

tags/0.0.1
Tu Do 3 years ago
parent
commit
6aac386e78
1 changed files with 1 additions and 1 deletions
  1. 1
    1
      README.md

+ 1
- 1
README.md View File

@@ -27,7 +27,7 @@ After completing this book, at the very least:

> You give a poor man a fish and you feed him for a day. You teach him to fish and you give him an occupation that will feed him for a lifetime.

This is the guiding principle of the book when writing it. The book does not try to teach you everything, but enough to enable you to learn by yourself. The book itself, at this point, is quite "complete": once you master part 1 and part 2 (which consists of 8 chapters), you can drop the book and learn by yourself. At this pint, a smart reader should be able to continue on his own.
This is the guiding principle of the book when writing it. The book does not try to teach you everything, but enough to enable you to learn by yourself. The book itself, at this point, is quite "complete": once you master part 1 and part 2 (which consists of 8 chapters), you can drop the book and learn by yourself. At this pint, a smart reader should be able to continue on his own. For example, he can continue his journey on [OSDev wiki](http://wiki.osdev.org/Main_Page); or, if he considers developing an OS for fun is impractical, he can continue with a Linux-specific book, such as this free book [Linux Insiders](https://0xax.gitbooks.io/linux-insides/content/), or other popular Linux kernel books.

The book teaches you core concepts, such as x86 Assembly, ELF, linking and debugging on bare metal, etc., but more importantly, where such information comes from. For example, instead of just teaching x86 Assembly, it also teaches you how to use the reference manuals from Intel. Learning to read the official manuals is important because only the hardware manufacturers themselves understand how their hardware work. If you only learn from the secondary resources because it is easier, you will never gain a complete understating of the hardware you are programming for. Have you ever read a book on Assembly, and wonder where does all the information come from? How does the author know everything he says is correct? And how one seems to magically know so much about hardware programming? The book gives a pointer to such questions.


Loading…
Cancel
Save