Red Bear OS
181eb63dd2
DEF-P0-11 (Finding 1.7: option collision) from NETWORKING-AND-DRIVERS-CODE-ASSESSMENT-2026-07-27.md §3.4: SocketT trait methods get_sock_opt and set_sock_opt previously took a single 'name' parameter. The dispatch in scheme/socket.rs now reads metadata[1] as level and metadata[2] as name, but the trait didn't have the level parameter. This commit updates the trait and all impls (socket.rs stub, tcp.rs, udp.rs) to take (level, name) as separate parameters. The impls ignore level for now (each impl only handles its own protocol family), but the parameter is there so future per-level dispatch (e.g. 'IP_TTL only valid at IPPROTO_IP') can reject early with ENOPROTOOPT.
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.