vasilito
9871d79aa4
Phase 4.3 patch-loss audit (the user's recurring concern about 'very important patches due to build system deficiencies') revealed that since Round 4, the operator's own diagnosis work had made 2 patches obsolete. Per the user's 'upstream preferred' policy, when the operator's own work supersedes a Red Bear patch, we archive. P0-canary (operator-superseded): - Original: Phase 1.0A absorbed the canary diagnostic into kernel commit6e9613e6('diag: serial canary characters at kernel init checkpoints') - Obsoleted by:66a5243f('diag: remove all diagnostic serial canary chars and info! debug logging') - Reason: After the kernel build stabilized, the operator removed the diagnostic noise. The canary's purpose (early-boot serial output) is no longer needed. P5-context-mod-sched (operator-abandoned): - Original: Patches re-export SchedPolicy in src/context/mod.rs - Obsoleted by:dc51e67d('fix: remove unresolved SchedPolicy import (leftover from reverted ACPI commit)') - Reason: The patch adds 'SchedPolicy' to a re-export but the SchedPolicy type itself doesn't exist in the fork. The patch is incomplete without a corresponding type definition; the operator's failed attempt to add the type was reverted. Both moves follow AGENTS.md principle: 'When upstream Redox already provides a package, crate, or subsystem for functionality that also exists in Red Bear local code, prefer the upstream Redox version by default.' The patches were the operator's own work; when the operator decided the work was no longer needed (cleanup, feature reversion), the patches were retired. 'Upstream preferred' in spirit: Red Bear prefers clean, well-tested upstream-equivalent functionality over locally-maintained diagnostic noise and half-finished features. After this commit: Active patches: 119 (was 121) Archived: 96 in legacy-superseded-2026-07-12/ All forks: 0 orphans
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.