Red Bear OS
c33f6ce762
Round 6 stub scan follow-up: resolves three FIXMEs in the SHM scheme daemon (ipcd/src/shm.rs). * O_RDONLY/O_WRONLY/O_RDWR handling (was line 51): the Handle enum now tracks readable/writable booleans derived from the open flags' O_ACCMODE bits. read() returns EACCES on write-only handles; write() returns EACCES on read-only handles. When no access mode is specified (acc == 0), both read and write are permitted (preserves prior behavior). * Zero-fill on truncate (was line 232): MmapGuard::grow_to now zeroes the byte range [old_len, new_len] on every growth, both in the in-capacity path and the new-allocation path. This ensures ftruncate- extended bytes read as zeros per POSIX SHM semantics, and prevents stale data leakage after a shrink-then-grow cycle. A zero_range helper method centralizes the write_bytes call. * Zero-fill on read (was line 293): the grow_to zero-fill guarantee ensures all bytes within [0, self.len] are properly initialized (zeros or written data), so reads within the logical size always return valid data. The FIXME is removed and a null-base guard was added to read() for defensive safety.
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.