Red Bear OS
fb421083e0
The handoff is one-shot: inputd signals it the moment the real display driver registers its path, but the driver's scheme may not serve the v2 open / capability query for a few more milliseconds. Without a retry, a transient not-ready driver leaves the framebuffer permanently blank — the login prompt is drawn to the framebuffer VT, so the console appears dead even though boot continues on the serial mirror (observed as the 2026-07-20 '-vga std' boot freeze at 'Performing handoff'). Retry the reopen for up to 250 x 10ms; the driver becomes ready well within this bound in practice. On success after retries, log the retry count at info level. If the driver is still not ready after the bound, emit a single explicit warning instead of per-attempt warn spam (the per-attempt message in display.rs is demoted to debug). Serial mirror remains unaffected in the failure case.
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.