Red Bear OS
9d8ad861ce
The netcfg scheme's 'ifaces' subtree had 21 hardcoded 'eth0' literals — one in the routing tree path and 20 in device lookups. This made any non-eth0 interface (wlan0, enp3s0, etc.) invisible to netcfg's ifaces config path. The 'ifaces' routing tree is statically routed (compile-time key in the dispatch! macro), so a full schema refactor to runtime-keyed map is out of scope for this minimal change. Instead, this commit: 1. Introduces DEFAULT_IFACE: &str = 'eth0' const at the top of src/scheme/netcfg/mod.rs (with a docstring explaining the architectural choice and the follow-up path). 2. Replaces all 21 hardcoded 'eth0' literals with the DEFAULT_IFACE constant. The routing tree path uses DEFAULT_IFACE in the dispatch! macro expansion; the device lookups use DEFAULT_IFACE in devices.borrow().get(DEFAULT_IFACE). This is a pure refactor — no behavior change for the default 'eth0' case. Future work: convert the routing tree to runtime-keyed so a system with wlan0 as primary can serve the ifaces subtree at /ifaces/wlan0/... Found by the Round 12 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.