Red Bear OS
946d28d8ad
R002 from NETWORKING-AND-DRIVERS-CODE-ASSESSMENT-2026-07-27.md §3.1: netstack/src/filter/conntrack.rs captured '(is_orig, entry_key)' in an if/else, but the 'if let' arm early-returned on line 293, so is_orig was always true when execution reached the second 'if let' on line 298. The reply-direction state machine (advance_entry_state with is_orig=false, lines 213-242) was effectively unreachable for already-established flows. Fix: flatten the conditional. The reply-side 'if let' now early- returns on match; the fall-through uses the original-direction key directly (no entry_key clone needed since reply_key was already consumed by the first if-let). The 'is_orig' variable is gone; the orig-side path now calls advance_entry_state with is_orig=true explicitly. Reply-direction advances now actually happen for already- established connections, restoring correct TCP/UDP conntrack state-machine behaviour.
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.