Skip to content

Commit

Permalink
Use relative link and myOS in chainload docs
Browse files Browse the repository at this point in the history
  • Loading branch information
64 committed Jul 11, 2019
1 parent f1fb6d8 commit 8371044
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 4 deletions.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,7 @@ The bootloader crate can be configured through some cargo features:
## Advanced Documentation
See these guides for advanced usage of this crate:

- [Chainloading](https://github.com/rust-osdev/bootloader/blob/master/doc/chainloading.md)
- [Chainloading](doc/chainloading.md)
- Higher Half Kernel - TODO

## License
Expand Down
6 changes: 3 additions & 3 deletions doc/chainloading.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ Chainloading is a technique that allows one bootloader to call another bootloade
Create a file under `iso/boot/grub/grub.cfg` in the root directory of your OS's source tree. In it, put:

```
menuentry "BlogOS" {
menuentry "myOS" {
chainloader (hd1)+1
}
```
Expand All @@ -17,7 +17,7 @@ Next, create the ISO with:
grub-mkrescue -o grub.iso iso
```

Testing with QEMU:
Testing with QEMU (replacing `my_os` with the name of your OS's target):
```
qemu-system-x86_64 -hda grub.iso -hdb target/x86_64-blog_os/debug/bootimage-blog_os.bin
qemu-system-x86_64 -hda grub.iso -hdb target/x86_64-my_os/debug/bootimage-my_os.bin
```

0 comments on commit 8371044

Please sign in to comment.