michaelkuc6/blog_os
1
0
Fork 0
mirror of https://github.com/phil-opp/blog_os.git synced 2025-12-17 06:47:49 +00:00
Code Issues Projects Releases Wiki Activity

Merge pull request #439 from phil-opp/integration-tests

Browse Source 
New post about integration testing
This commit is contained in:
Philipp Oppermann
2018-06-15 10:30:24 +02:00
committed by GitHub
parent 3372966664 837d1502e9
commit 01ac5b5ea0
16 changed files with 807 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
blog/content/second-edition/posts/02-minimal-rust-kernel/index.md
View File

@@ -315,7 +315,13 @@ Now that we have an executable that does something perceptible, it is time to tu
[section about booting]: #the-boot-process
To make things easy, we created a tool named `bootimage` that automatically downloads a bootloader and combines it with the kernel executable to create a bootable disk image. To install it, execute `cargo install bootimage` in your terminal. After installing, creating a bootimage is as easy as executing:
To make things easy, we created a tool named `bootimage` that automatically downloads a bootloader and combines it with the kernel executable to create a bootable disk image. To install it, execute the following command in your terminal:
```
cargo install bootimage --version 0.4.0
```
After installing, creating a bootimage is as easy as executing:
```
> bootimage build --target x86_64-blog_os.json
@@ -323,7 +329,7 @@ To make things easy, we created a tool named `bootimage` that automatically down
The tool also recompiles your kernel using `cargo xbuild`, so it will automatically pick up any changes you make.
After executing the command, you should see a file named `bootimage.bin` in your crate root directory. This file is a bootable disk image. You can boot it in a virtual machine or copy it to an USB drive to boot it on real hardware. (Note that this is not a CD image, which have a different format, so burning it to a CD doesn't work).
After executing the command, you should see a file named `bootimage.bin` in your `target/x86_64-blog_os/debug` directory. This file is a bootable disk image. You can boot it in a virtual machine or copy it to an USB drive to boot it on real hardware. (Note that this is not a CD image, which have a different format, so burning it to a CD doesn't work).
#### How does it work?
The `bootimage` tool performs the following steps behind the scenes:
@@ -371,17 +377,11 @@ By default it invokes the exact same QEMU command as above. Additional QEMU opti
[Readme file]: https://github.com/rust-osdev/bootimage/blob/master/Readme.md
### VirtualBox
You can also [convert the raw disk image to a VDI] to load it in [VirtualBox].
[convert the raw disk image to a VDI]: https://blog.sleeplessbeastie.eu/2012/04/29/virtualbox-convert-raw-image-to-vdi-and-otherwise/
[VirtualBox]: https://www.virtualbox.org/
### Real Machine
It is also possible to write it to an USB stick and boot it on a real machine:
```
> dd if=bootimage.bin of=/dev/sdX && sync
> dd if=target/x86_64-blog_os/debug/bootimage.bin of=/dev/sdX && sync
```
Where `sdX` is the device name of your USB stick. **Be careful** to choose the correct device name, because everything on that device is overwritten.