Red Bear OS
30a8db93e0
Complete, self-contained Phase 7 / CORE-C12 module: - Packet type and worker_loop helper for the per-NIC read path with proper error handling on worker exit. - ReaderPool::spawn takes a Vec<File> and spawns one worker thread per file. Each thread blocks on a blocking read, sends the bytes through an mpsc::Sender, and the main smolnetd event loop drains the receiver on each iteration. - drain (non-blocking) and recv (blocking) methods on the receiver. Both return cleanly when the channel disconnects (worker exited). - Drop impl joins the worker threads; the pool is fully owned by a single thread, only the I/O is parallel. - Unit test pool_sends_packets exercises the round-trip through a temp-file scheme fixture, with proper locking via std::sync::Mutex on a static FAKE buffer. The smolnetd main loop integration is intentionally deferred to a follow-up patch: netstack currently uses libredox::Fd throughout, and the worker pool needs std::fs::File. Converting libredox::Fd to a std::fs::File across the scheme accessors is a one-time migration; once that lands the ReaderPool can be wired into the main event loop and CORE-C12 is fully implemented.
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.