Skip to content

Commit a1a135a

Browse files
committed
Link to the new post_n tags
1 parent 4feb812 commit a1a135a

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

blog/content/post/01-multiboot-kernel.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ This post explains how to create a minimal x86 operating system kernel. In fact,
1717
I tried to explain everything in detail and to keep the code as simple as possible. If you have any questions, suggestions or other issues, please leave a comment or [create an issue] on Github. The source code is available in a [repository][source code], too.
1818

1919
[create an issue]: https://github.com/phil-opp/blog_os/issues
20-
[source code]: https://github.com/phil-opp/blog_os/tree/multiboot_bootstrap/src/arch/x86_64
20+
[source code]: https://github.com/phil-opp/blog_os/tree/post_1/src/arch/x86_64
2121

2222
Note that this tutorial is written mainly for Linux. For some known problems on OS X see the comment section and [this issue][mac os issue]. If you want to use a virtual Linux machine, you can find instructions and a Vagrantfile in Ashley Willams's [x86-kernel repository].
2323

blog/content/post/02-entering-longmode.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ In the [previous post] we created a minimal multiboot kernel. It just prints `OK
2121
I tried to explain everything in detail and to keep the code as simple as possible. If you have any questions, suggestions, or issues, please leave a comment or [create an issue] on Github. The source code is available in a [repository][source code], too.
2222

2323
[create an issue]: https://github.com/phil-opp/blog_os/issues
24-
[source code]: https://github.com/phil-opp/blog_os/tree/entering_longmode/src/arch/x86_64
24+
[source code]: https://github.com/phil-opp/blog_os/tree/post_2/src/arch/x86_64
2525

2626
## Some Tests
2727
To avoid bugs and strange errors on old CPUs we should check if the processor supports every needed feature. If not, the kernel should abort and display an error message. To handle errors easily, we create an error procedure in `boot.asm`. It prints a rudimentary `ERR: X` message, where X is an error code letter, and hangs:

blog/content/post/03-set-up-rust.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ In the previous posts we created a [minimal Multiboot kernel][multiboot post] an
2020
This blog post tries to set up Rust step-by-step and point out the different problems. If you have any questions, problems, or suggestions please [file an issue] or create a comment at the bottom. The code from this post is in a [Github repository], too.
2121

2222
[file an issue]: https://github.com/phil-opp/blog_os/issues
23-
[Github repository]: https://github.com/phil-opp/blog_os/tree/set_up_rust
23+
[Github repository]: https://github.com/phil-opp/blog_os/tree/post_3
2424

2525
## Installing Rust
2626
We need a nightly compiler, as we will use many unstable features. To manage Rust installations I highly recommend [rustup]. It allows you to install nightly, beta, and stable compilers side-by-side and makes it easy to update them. To use a nightly compiler for the current directory, you can run `rustup override add nightly`.

0 commit comments

Comments
 (0)