Red Bear OS
1769b083ab
- init: add condition_path_exists so optional-daemon units (dbus, seatd, thermald, evdevd) are silently skipped when their binary is absent in a minimal image, instead of emitting [FAILED] 'No such file or directory' on the bare target. Boot-critical units omit the field and still hard-fail. - ahcid: an empty ATAPI/optical drive (QEMU's default DVD-ROM, most bare-metal optical bays) failed READ CAPACITY and logged 4 ERROR lines every boot; register it with a zero block count as a normal no-media state and drop the HBA register dump to debug level. - netstack: a machine with no NIC (bare, or an unsupported NIC) logged an ERROR and exited non-zero; treat 'no network adapter' as a normal idle state (info + clean exit). - dhcpd: cut the socket timeout 30s -> 8s so the network stage fails fast when no DHCP server answers instead of stalling boot.
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.