cargo build
Updating crates.io index
Compiling compiler_builtins v0.1.36
Compiling core v0.0.0 (/Users/itq/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/src/rust/library/core)
Compiling rustversion v1.0.7
Compiling bootloader v0.9.22
Compiling x86_64 v0.13.6
Compiling rustc-std-workspace-core v1.99.0 (/Users/itq/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/src/rust/library/rustc-std-workspace-core)
Compiling bitflags v1.3.2
Compiling bit_field v0.10.1
Compiling volatile v0.4.5
error[E0658]: const generics are unstable
--> /Users/itq/.cargo/registry/src/github.com-1ecc6299db9ec823/volatile-0.4.5/src/lib.rs:686:21
|
686 | impl<R, A, T, const N: usize> Volatile<R, A>
| ^
|
= note: see issue #74878 <https://github.com/rust-lang/rust/issues/74878> for more information
= help: add `#![feature(min_const_generics)]` to the crate attributes to enable
Compiling bit_field v0.9.0
error: aborting due to previous error
For more information about this error, try `rustc --explain E0658`.
error: could not compile `volatile`
To learn more, run the command again with --verbose.
warning: build failed, waiting for other jobs to finish...
error: build failed
I'm stuck with this error
I tried adding
#![feature(min_const_generics)] to src/main.rs and src/lib.rs but didn't help.
@lubingyucn: There is no formal process for adding a translator. You can just create a new translation and open a pull request, then we look for someone else that also speaks the language for a review. To avoid duplicated work, it's a good idea to open a draft PR very early to show other people what you're working on.
We don't have a clear rule on that yet, but I think you should be fluent in the language and know all relevant grammatical rules
Hello !
I have a quick question. I just finished the external interrupt handling chapter of the tutorial, and a question went in my mind.
Given that I am not using an US layout keyboard (I am using an AINSI layout), is there any chance that in the following parts, the USB protocol will be implemented ?
btw, I love the tutorial. Very explanatory and easy to follow. Thanks
Hi, great to hear that you like the tutorials! To use a different keyboard layout, you need to change the mapping of the scancodes. The
pc-keyboard crate already supports different layouts: https://docs.rs/pc-keyboard/0.5.1/pc_keyboard/layouts/index.html . I'm sure that the crate maintainer will be happy to merge a PR to add more layouts if yours isn't supported yet.
Thank you !
A quick other thing. I do know how difficult it is to make a tutorial of this scale, but when do you think that the next chapter will be available ?
A quick other thing. I do know how difficult it is to make a tutorial of this scale, but when do you think that the next chapter will be available ?
I'm currently working on a major refactor of the series, based on a new version of the
bootloader crate. The goal is to simplify the build process, add support for booting on UEFI machines, and use the APIC for interrupt handling. Afterwards, I'm planning to add more posts again, but don't expect this anytime soon.
alright np. Nice to hear that. I'll continue on my owm trying out some stuff to make a simple UNIX like system but I don't expect much haha. OS programming is quite challenging lmao
Cool :). Yeah, it can be a bit challenging at times. If you have discord, I recommend joining the #os-dev channel on the Rust Community Server. It's a good place to ask questions! https://discord.gg/rust-lang-community
Hi all, I'm new to Rust and I wanted to give it a try by following this tutorial. I get stuck with running
cargo bootimage. It croaks with the following error: note: rust-lld: error: undefined symbol: _rest_of_bootloader_start_addr
any clue of what this may be?
Compiling bootloader v0.9.23 (/Users/vscolari/.cargo/registry/src/github.com-1ecc6299db9ec823/bootloader-0.9.23)
error: linking withrust-lldfailed: exit status: 1
i'm on MacOs
he has the same issue
Looks like it's a regression in the Rust compiler. See https://github.com/rust-osdev/bootimage/issues/87#issuecomment-1272867264 for details. I recommend to use an older nightly until the issue is fixed.
Hi @Dreadlord1981! Thanks, great to hear that you like it :). The next step for the blog will be a new third edition, which will do a few things differently (UEFI support, APIC instead of PIC, pixel framebuffer instead of VGA text mode). Unfortunately, I'm a bit short on time right now, so I can't really give you an estimate when it will be ready...
How easy would it be to port it to ARM? Will you eventually make a bootloader for ARM (Esp TI sitara)?
I am trying to find an easy hack able ground up OS for that platform
The big idea is to connect multiple processors and share threads among them
Hi, I don't have any plans to create an ARM bootloader right now. ARM is quite different than x86 in many aspects, so porting the tutorial is not that easy. The fundamental concepts (e.g. page tables, interrupts, etc.) are similar though
What kind of ARM core do you have? There are different classes of processors that provide different levels of abstraction. For example, Cortex-M cores do not have a memory management unit, which makes them unsuitable for general purpose operating systems.
More specifically
Sitara AM437x from TI
I think you should be able to create a full OS on that. I'm not aware of any Rust tutorials for that processor, though..
Hello everyone :)
I'm following the tutorial to build a minimal kernel
error: failed to run rustc to learn about target-specific information but I've this error on windows powershell
Caused by:
process didn't exit successfully: rustc - --crate-name ___ --print=file-names --target \\?\C:\workspace\blog_os\x86-64-blog-os.json --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro --print=sysroot --print=cfg (exit code: 1)
--- stderr
error: target file "\\?\C:\workspace\blog_os\x86-64-blog-os.json" does not exist
Someone had the issue ?
Are you sure that you passed the correct file name for the target? On the blog we use the file name "x86_64-blog_os.json", which is slightly different than your "x86-64-blog-os.json" target (hyphens instead of underscores).
Hey, I'm trying to set up a Rust book similar to this one, with varying versions that all build on one another. I wanted to ask, how does the infrastructure for this project work? How do those separate branches all get collated into one main target version that gets deployed to the actual blog? So far, I'm using
mdbook and keeping all the versions in the same folder, but it's already getting incredibly tedious. If someone could point me to some resources on how the blog author did this/some templates/other info, I'd greatly appreciate it.
Hi @naiveai: We use post-XX branches for the code, which are merged into each other. So if we e.g. change some code in post-04, we merge it into post-05 afterwards, then post-05 into post-06, and so on. We have a script for that, so we only need to do it manually when there are conflicts.
The blog text is independent of the post-XX branches, so we have to keep it in sync with the code manually.
The blog text is independent of the post-XX branches, so we have to keep it in sync with the code manually.
@vishnukumarkalidasan: We don't have a blog_os version with ACPI/APIC support yet, but it is planned. We just released a new v0.11 version of the bootloader together with some migration guides. Among other things, these guides outline the necessary steps to get the APIC working.
Hello, I am trying to make a rust kernel with the latest version of the bootloader (currently 0.11.0). When I try to print to the framebuffer via a logger (is the same code that is in the logger of the bootloader) I get an error when using init_logger():error[E0597]:
--> kernel/src/main.rs:19:18
|
19 | let buffer = framebuffer.buffer_mut();
| ^^^^^^^^^^^^^^^^^^^^^^^^ borrowed value does not live long enough
20 | init_logger(buffer, info);
| ------------------------- argument requires that
21 | loop {}
22 | }
| -
framebuffer does not live long enough--> kernel/src/main.rs:19:18
|
19 | let buffer = framebuffer.buffer_mut();
| ^^^^^^^^^^^^^^^^^^^^^^^^ borrowed value does not live long enough
20 | init_logger(buffer, info);
| ------------------------- argument requires that
framebuffer is borrowed for 'static21 | loop {}
22 | }
| -
framebuffer dropped here while still borrowed
I don't understand this error because framebuffer isn't dropped because main is a divergent function.
Thanks in advance for the answers.