runloop_internal makes a call to thread_pause to take care of time accounting. This kind of violates a tacit understanding that the core parts of the kernel are independent of unix, which is one of what could be multiple syscall interfaces exposed to threads. Consider adding another frame method - like FRAME_PAUSE - for a callback (thunk) from the scheduler, and remove the unix-specific includes a

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

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