Red Bear OS
aedc416f0c
The bootstrap's start.rs used libredox::call::openat which resolved to the bootstrap's own redox_openat_v1 in initfs.rs, calling syscall::openat (SYS_OPENAT). This let the kernel allocate POSIX FDs 0,1,2 for stdin/stdout/stderr, but the userspace FILETABLE was never updated. Later, exec.rs called auth.dup(b'cur-context') via redox_rt::sys::dup, which asked the empty FILETABLE for a free slot (returning 0), then passed it to SYS_DUP_INTO. The kernel rejected it with EEXIST because posix_fdtbl[0] was already occupied by stdin. Fix: use syscall::openat_into to directly specify FD slots 0,1,2 in start.rs, and use syscall::dup_into with a computed FD index for cur-context in exec.rs. Both bypass the FILETABLE, which is only populated later by redox_rt::initialize_freestanding.
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.