Red Bear OS
e54484e553
Daemon stdio (fd 0/1/2) is inherited from bootstrap pointing at /scheme/debug — the kernel console — which fbcond renders onto the *active* VT. Once 29_activate_console switches the active VT to 2 for the getty login, any daemon that logs afterwards paints on top of the login banner/prompt: late async driver attach (i2c-hidd, evdevd, dw-acpi-i2cd, all via common::setup_logging -> stderr) and smolnetd's bounded NIC wait. So the banner ended up "near the end" but never last. Re-enable switch_stdio, redirecting daemon stdio to a fixed boot-log VT (/scheme/fbcon/1) right after the /usr switchroot, before the /usr units run. VT1 is the active console during boot (so the full boot stays visible there), fbcond still mirrors it to serial, and VT2 is left clean for a prompt that lands last. This is NOT the old /scheme/log redirect that went dark: that relied on fbbootlogd surfacing /scheme/log to the framebuffer (racy). A real VT renders directly. Best-effort: if fbcon/1 can't be opened, stdio stays on the kernel console exactly as before. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.