Red Bear OS
dcd70a1255
Phase II.X.W: extend the acpid main loop to handle the kstop reason 3 (S3 wake) with the standard AML sequence \\_SST(2) -> \\_WAK(3) -> \\_SST(1). Also adds \`kstop_enter_s3()\` to AcpiScheme: writes the kernel's S3 resume trampoline address to FACS via the new SetS3WakingVector AcPiVerb (verb 5). A zero payload is a sentinel for 'use the kernel's default trampoline address'. The acpid's enter_sleep_state for S3 will: 1. Do the AML prep (\\_TTS(3), \\_PTS(3), \\_SST(3)) - the existing set_global_s_state path. 2. Call kstop_enter_s3(0) to write the trampoline address to FACS. 3. Write 's3' to /scheme/sys/kstop to trigger the kernel's S3 entry path. Hardware-agnostic: works on any x86_64 system with standard ACPI S3 support (Dell, HP, Lenovo, LG Gram 14). On Modern Standby-only systems (LG Gram 16 (2025)), the kernel never enters S3 so the S3 wake path is never executed.
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.