Red Bear OS
10b3ab9713
Several downstream crates (acpid for SMBIOS scanning, redox-drm, GPU drivers) hold the physmap error in a map_err adapter. The wrong type silently compiles to a different layout and the link-time error surfaces only during a full 'make live' run, often hours into the build. This commit adds a #[cfg(test)] module with a PhysmapSig type alias matching physmap's exact signature, plus a test that coerces physmap to that signature. If physmap's error type drifts (e.g. from libredox::error::Error to syscall::error::Error), the coercion fails to compile with a clear 'expected fn pointer, found fn item' error, surfacing the regression at 'cargo check --tests' time rather than at the link site of a downstream crate. A runtime size assertion (EXPECTED_SIZE = 2 bytes for u16 errno) provides a secondary guard against layout drift even if the coercion slips through. Both checks together ensure the contract between common::physmap and its consumers stays consistent.
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.