From 94d87308f40a57422bd008d5a116457613a92b91 Mon Sep 17 00:00:00 2001 From: Philipp Oppermann Date: Sun, 9 Apr 2023 13:52:58 +0200 Subject: [PATCH] Fix typo --- blog/content/edition-3/posts/02-booting/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/content/edition-3/posts/02-booting/index.md b/blog/content/edition-3/posts/02-booting/index.md index cacfcc4a..aba14f9c 100644 --- a/blog/content/edition-3/posts/02-booting/index.md +++ b/blog/content/edition-3/posts/02-booting/index.md @@ -530,7 +530,7 @@ After creating a bootable disk image for our kernel, we are finally able to run Before we learn how to run it on real hardware, we start by running it inside the [QEMU] system emulator. This has multiple advantages: -- We can't break anything: Our kernel has full hardware access, so that a bug might have serious consequences on read hardware. +- We can't break anything: Our kernel has full hardware access, so that a bug might have serious consequences on real hardware. - We don't need a separate computer: QEMU runs as a normal program on our development computer. - The edit-test cycle is much faster: We don't need to copy the disk image to bootable usb stick on every kernel change. - It's possible to debug our kernel via QEMU's debug tools and GDB.