Red Bear OS
a916a6612c
Add control kinds 3/4 (set VT graphics/text mode) and a graphics_vts set. When a VT is claimed by a graphical client, the console `Consumer` for that VT is suspended — cooked bytes stop being delivered to the text console — while the raw device tap (consumer_raw) keeps feeding the compositor. This is the RedBear equivalent of Linux KDSKBMODE(K_OFF)/KD_GRAPHICS silencing the console keyboard + n_tty for a VT owned by a Wayland compositor. Behaviour-preserving by default: graphics_vts is empty until a compositor opts in via ControlHandle::set_vt_mode(vt, true), so text-console delivery is unchanged. Two control kinds are used instead of a bool to keep the ControlEvent ABI unchanged. Full device-grab arbitration (exclusive routing / EVIOCGRAB) and the VT_PROCESS switch-ack handshake remain TODO — the raw broadcast is sufficient for a single compositor. Part of the Linux-aligned input-stack consolidation. Compile-checked for x86_64-unknown-redox; boot-validation pending build-green.
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.