Red Bear OS
f646e42e55
IMPROVEMENT-PLAN.md §10.1 item 1: critical safety fix. usbscsid scsi/mod.rs had 17 plain::from_mut_bytes/from_bytes/slice_from_bytes .unwrap() calls on compile-time-fixed-size buffers. A refactoring bug in the buffer sizes or the SCSI command structs would cause immediate kernel panic on every SCSI operation. Fix: replace each .unwrap() with .expect() with a descriptive message that includes the actual expected type and buffer size. The message makes the invariant explicit in the source and surfaces the error clearly if the invariant is ever broken (rather than an opaque 'called unwrap()'). Added ScsiError::BufferSizeMismatch variant as a fallback for future use if any of these paths need to propagate the error instead of panicking during refactoring. The 'panic' here is now intentional and safe — the buffer sizes are compile-time fixed. cross-references IMPROVEMENT-PLAN.md §10.1.1
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.