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

Rename first-edition subfolder to edition-1

Browse Source
This commit is contained in:
Philipp Oppermann
2020-12-16 14:36:34 +01:00
parent f6416c1e6b
commit 4a9ea6c503
103 changed files with 1077 additions and 135 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -83,7 +83,7 @@ rtl = true
به دلیل این اشکالات ما تصمیم گرفتیم از GRUB یا استاندارد Multiboot استفاده نکنیم. با این حال، ما قصد داریم پشتیبانی Multiboot را به ابزار [bootimage] خود اضافه کنیم، به طوری که امکان بارگذاری هسته شما بر روی یک سیستم با بوت‌لودر GRUB نیز وجود داشته باشد. اگر علاقه‌مند به نوشتن هسته سازگار با Multiboot هستید، [نسخه اول] مجموعه پست‌های این وبلاگ را بررسی کنید.
[نسخه اول]: @/first-edition/_index.md
[نسخه اول]: @/edition-1/_index.md
### UEFI

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

@@ -80,7 +80,7 @@ x86には2つのファームウェアの標準規格があります："Basic Inp
これらの欠点を考慮し、私達はGRUBとMultiboot標準規格を使わないことに決めました。しかし、あなたのカーネルをGRUBシステム上で読み込めるように、私達の[bootimage]ツールにMultibootのサポートを追加することも計画しています。Multiboot準拠なカーネルを書きたい場合は、このブログシリーズの[第1版][first edition]をご覧ください。
[first edition]: @/first-edition/_index.md
[first edition]: @/edition-1/_index.md
### UEFI

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

@@ -76,7 +76,7 @@ To make a kernel Multiboot compliant, one just needs to insert a so-called [Mult
Because of these drawbacks we decided to not use GRUB or the Multiboot standard. However, we plan to add Multiboot support to our [bootimage] tool, so that it's possible to load your kernel on a GRUB system too. If you're interested in writing a Multiboot compliant kernel, check out the [first edition] of this blog series.
[first edition]: @/first-edition/_index.md
[first edition]: @/edition-1/_index.md
### UEFI

4
blog/content/second-edition/posts/05-cpu-exceptions/index.md
View File

@@ -456,9 +456,9 @@ blog_os::interrupts::test_breakpoint_exception... [ok]
## Too much Magic?
The `x86-interrupt` calling convention and the [`InterruptDescriptorTable`] type made the exception handling process relatively straightforward and painless. If this was too much magic for you and you like to learn all the gory details of exception handling, we got you covered: Our [“Handling Exceptions with Naked Functions”] series shows how to handle exceptions without the `x86-interrupt` calling convention and also creates its own IDT type. Historically, these posts were the main exception handling posts before the `x86-interrupt` calling convention and the `x86_64` crate existed. Note that these posts are based on the [first edition] of this blog and might be out of date.
[“Handling Exceptions with Naked Functions”]: @/first-edition/extra/naked-exceptions/_index.md
[“Handling Exceptions with Naked Functions”]: @/edition-1/extra/naked-exceptions/_index.md
[`InterruptDescriptorTable`]: https://docs.rs/x86_64/0.12.1/x86_64/structures/idt/struct.InterruptDescriptorTable.html
[first edition]: @/first-edition/_index.md
[first edition]: @/edition-1/_index.md
## What's next?
We've successfully caught our first exception and returned from it! The next step is to ensure that we catch all exceptions, because an uncaught exception causes a fatal [triple fault], which leads to a system reset. The next post explains how we can avoid this by correctly catching [double faults].