Red Bear OS
b16e6ca399
The debounce's inner clear of C_PORT_CONNECTION could hang or be ignored by the hub, and our control transfers have no timeout — so a literal port of Linux's clear-inside-the-loop design deadlocked hub enumeration: the debounce never converged and the reset/attach path was never reached (observed on QEMU as usbhubd logging the port's first status with connection_changed=true and then going silent forever). Judge the 100ms stable window on the connection STATE alone (the same stability property hub_port_debounce_be_connected protects): a stuck or hung change bit can no longer deadlock enumeration — it only re-triggers a poll, and is cleared once, best-effort, after a successful attach (matching Linux port_event's C_PORT_CONNECTION clear). New regression test debounce_stuck_change_bit_still_converges locks the deadlock scenario; 15/15 tests pass.
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.