Red Bear OS
c5b32f9f6b
Three fixes that turn unconditional panics into recoverable errors:
1. drivers/graphics/vesad/src/main.rs: replaced bare 'panic!()' at
line 132 (unconditional if the event loop exits) with a clean
exit so init can restart vesad or fall back to a different
display driver.
2. drivers/storage/nvmed/src/main.rs: replaced the
'panic!("timeout on init")' timeout with a structured error:
log a message, then process::exit(1) so init can fall back to
another block driver (virtio-blkd, ahcid, etc.). nvmed_init
future still races against the timer future, but a timeout is
no longer a kernel-visible panic.
3. drivers/storage/nvmed/src/nvme/mod.rs: deleted two commented-out
match arms (lines 372-377 and 401-406) that contained
panic!("invalid queue ...") inside /* */ comments. The panics
were correctly disabled to avoid kernel crashes, but the
comments are stale and the queue-error path now silently
continues. Removing the dead comments so a future audit doesn't
resurrect them; the underlying issue (queue errors not
propagated) is tracked for a follow-up.
Found by the Round 13 audit (local/docs/3D-DESKTOP-COMPREHENSIVE-
PLAN.md §10).
Base
Repository containing various system daemons, that are considered fundamental for the OS.
You can see what each component does in the following list:
- audiod : Daemon used to process the sound drivers audio
- bootstrap : First code that the kernel executes, responsible for spawning the init daemon
- daemon : Redox daemon library
- drivers
- init : Daemon used to start most system components and programs
- initfs : Filesystem with the necessary system components to run RedoxFS
- ipcd : Daemon used for inter-process communication
- logd : Daemon used to log system components and daemons
- netstack : Daemon used for networking
- ptyd : Daemon used for pseudo-terminal
- ramfs : RAM filesystem
- randd : Daemon used for random number generation
- zerod : Daemon used to discard all writes and fill read buffers with zero
How To Contribute
To learn how to contribute you need to read the following document:
If you want to contribute to drivers read its README
Development
To learn how to do development with these system components inside the Redox build system you need to read the Build System and Coding and Building pages.
How To Build
It is recommended to build this system component via the Redox build system, you can learn how to do it on the Building Redox page.
To build and test outside the build system, install redoxer then use check.sh script to build or test:
./check.sh- Check build for x86_64./check.sh --arch=ARCH- Check build for specific ARCH (aarch64,i586,riscv64gc)./check.sh --all- Check build for all ARCH./check.sh --test- Check the base system boots up on x86_64
You can also use make install to inspect the content on ./sysroot, or make test-gui to test booting with orbital interactively.