Currently, the uefi-services crate contains a panic handler, while this is useful, It is a problem if you are doing printing yourself as you can't use your own printer for panics. The best option would be to make the panic handler optional using cfg_attr()

Thank you for your time!

We don't currently have an explicit test for futexes. We could use an exhaustive test that stresses both the futex interface as well as correctness on single and multiple-core instances. The test should run under both a Linux host and nanos as a parity check.

Here is a list of commands to implement to make the skift shell usable.
(The source code of uname is a good example of how commands should be written.)

• chgrp
• chown
• chmod
• cp (missing options)
• rw (replacement for dd https://sortix.org/rw/)
• df
• ln
• ls
• mkdir
• mkfifo
• mknod
• mktemp
• mv (not complete)
• realpath

Although a new inline assembly syntax asm! was announced in Rust on 2020/06/08[1], KRaBs still uses llvm_am!.

[1] New inline assembly syntax available in nightly

According to the blog, the asm! macro should be safer and easier to use. This is expected to become the mainstream of inline assembly in the future, so

display_bsod internally calls the map_framebuffer syscall to map the framebuffer, because we . were lazy and didn't want to duplicate code. However this syscall retrieves the current process to map it in its process memory.

When we're panicking during early boot, CURRENT_PROCESS is None and this panics in the panic handler.

We should instead do a second function that maps it in the k