From 4f87dd7be07bda5fa6d0912fdff2247428da50c8 Mon Sep 17 00:00:00 2001 From: 0xAX Date: Tue, 10 Feb 2015 22:58:32 +0600 Subject: [PATCH] Update linux-bootstrap-1.md --- Booting/linux-bootstrap-1.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/Booting/linux-bootstrap-1.md b/Booting/linux-bootstrap-1.md index cc18dd3..ea5dc52 100644 --- a/Booting/linux-bootstrap-1.md +++ b/Booting/linux-bootstrap-1.md @@ -133,7 +133,14 @@ We will see: ![Simple bootloader which prints only `!`](http://oi60.tinypic.com/2qbwup0.jpg) -In this example we can see that this code will be executed in 16 bit real mode and will start at 0x7c00 in memory. After the start it calls the [0x10](http://www.ctyme.com/intr/rb-0106.htm) interrupt which just prints `!` symbol. It fills rest of 510 bytes with zeros and finish with two magic bytes 0xaa and 0x55. +In this example we can see that this code will be executed in 16 bit real mode and will start at 0x7c00 in memory. After the start it calls the [0x10](http://www.ctyme.com/intr/rb-0106.htm) interrupt which just prints `!` symbol. It fills rest of 510 bytes with zeros and finish with two magic bytes `0xaa` and `0x55`. + +Although you can see binary dump of it with `objdump` util: + +``` +nasm -f binary boot.nasm +objdump -D -b binary -mi386 -Maddr16,data16,intel boot +``` A real-world boot sector has code for continuing the boot process and the partition table... instead of a bunch of 0's and an exclamation point :) Ok, so, from this moment BIOS handed control to the bootloader and we can go ahead.