• init32.S has some unclear error message that could be written better.
• Add generation of the full screen error text, instead of hard coding it for each error.
• Maybe reference PowerD instead of PowerNex in the errors.

The dup runtime test fails with:

$ make TARGET=dup run                                                                                                                                                                                   
make[1]: Entering directory '/share/src/nanovms/master01/contgen'                                                                                            

I think you need to specify what's on your mind for that OS, and what are your next steps, so people can help, and also maybe choosing a way of communicating is a good thing also

Currently, anyone who wants to do anything with skiftOS has to look through the source code. Probably header files, and the issue with that is those don't have docs.

Currently, there is no documentation on custom APIs. (most important may very well be widgets) Also, if you want to port a program, even if it would other wise work on skiftOS, you would have to figure out how to add it, base

I'd really like to be able to say I have 100% comprehensive documentation for every publicly-exposed symbol in the SOS source code.

Rust gives us the #[deny(missing_docs)] attribute, which will fail compilation if it hits an item without documentation comments. I'd really like to say that the kernel can compile with t

The proxy does not show any usefull info when run without any parameter and seems to have not help message. This would really be useful for new users / forgetful people.

$ proxy
fopen: No such file or directory
fopen: No such file or directory

$ proxy --help
fopen: No such file or directory
fopen: No such file or directory

$ proxy -h
fopen: No such file or director

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

Improve readme information for new users/those not familiar with DOS. Add pcjs based support to demo running DOS from browser.

We need more detailed help for commands. This is going to be solved by some of the commands planned to be implemented in the "New Commands" issue, but making this separate issue so that people can give their views if they need some better help in some specific command.

These are the commands mentioned in the new commands issue

Check out kernel/kernel/kshell.c and kernel/libk/string.c... Replace the 'local' string algorithms in kshell with string.c ones. Also check if string.c/string.h implements all the the standard string functions

I was in a folder, and so I wanted to go in an another folder directly located in 0:/.
It keeps the last directory.