Red Bear OS
3a3af8253e
CRITICAL F001 (NETWORKING-AND-DRIVERS-CODE-ASSESSMENT-2026-07-27.md §3.1): BufferPool::get_buffer previously recycled buffers via unsafe set_len without zeroing, exposing prior packet data between unrelated flows (information disclosure). Now zero-fills via Vec::fill(0) before set_len. CRITICAL F1.6 (§3.3): xHCI phys_addr_to_index used `>` instead of `>=`, allowing index == len (one past end) which would panic in `&self.trbs[index]`. Fixed to `>=` with bounds check invariant documented. DEF-P0-7 + DEF-P0-7 (§3.1): rtl8139d and rtl8168d panicked on BAR lookup failure, taking down the entire driver subsystem. Now return Option from map_bar and gracefully exit (process::exit(1)) with an error log when no memory BAR is found. The kernel retains the PCI device so the failure is observable in the kernel log. DEF-P0-6 (§3.1): e1000d read_reg and write_reg had no bounds check, allowing out-of-range MMIO access. Added debug_assert! mirroring the ixgbed pattern: register <= 0x1FFFC && register % 4 == 0. Catches typos and off-by-one register table bugs in debug builds without runtime cost in release. Part of the systematic fix for CRITICAL code defects per §15.4 Implementation Status roadmap.
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.