Red Bear OS
6694b5af9e
V2GraphicsHandle::from_file() unwrapped/asserted the DumbBuffer capability, but the display fd is O_NONBLOCK and the graphics driver often has not finished coming up at handoff time — so from_file failed with EAGAIN and the assert panicked fbcond. Since fbcond owns the console and serial mirror, its death froze the whole boot right after 'Performing handoff' with no login prompt. Return an error from graphics-ipc when the driver does not yet report DumbBuffer, and have fbcond log-and-return so the handoff is retried when the driver publishes its surface, instead of panicking. (Change found as uncommitted work in the fork; committing to preserve it and unblock the clean-fork build gate.)
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.