Red Bear OS
54e89a337a
fbcond blocked indefinitely in open_display_v2() while handing the console over to the real graphics driver: boot stopped at "fbcond: Performing handoff" and never reached the "Opened new display" that follows a successful open. fbcond is single-threaded and owns the console, so while it waited there it stopped draining console writers. getty, login and the login shell all blocked on their writes, which made the failure look like a slow or hung shell -- the stall point just tracked whichever process next wrote to the console. If the graphics driver was itself waiting on the console, the two deadlocked outright and the console never came back. The wait comes from the scheme-open handshake: inputd signals the handoff as soon as the driver registers its path, but the driver may not be serving its scheme yet, and O_NONBLOCK does not bound the open (it governs later reads). Split the two halves in inputd's ConsumerHandle: display_path_v2() only does an fpath on our own handle and returns promptly, while open_display_path_v2() carries the blocking open. fbcond now resolves the path inline and hands the open to a worker thread, then picks the result up from the event loop via poll_pending_handoff(). Console output produced meanwhile is buffered in pending_writes (already the behaviour while the display is unmapped) and flushed once the new display is mapped.
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.