Red Bear OS
b9e2ec31d5
Phase 7 of the systematic plan: proptest-driven property-based testing for the firewall and conntrack state machines. filter/table.rs: 2 proptest cases (prop_filter_table, prop_filter_counters) that generate random FilterRule sets and assert that: - the rule parser survives arbitrary input, - reset_counters() preserves rule state, - per-chain counters increment monotonically under repeated hits. filter/conntrack.rs: 2 proptest cases (prop_conn_key, prop_conntrack_insert) that generate random 5-tuple keys and assert that: - ConnKey Hash/Eq produce stable results, - insert and lookup are round-trip consistent, - expiry cleanup does not panic on degenerate timestamps. Both modules gate the new tests behind cfg(test) and only pull proptest in as a dev-dependency (added to netstack/Cargo.toml). This commit does not change the smoltcp 0.13.1 API call site in scheme/ip.rs (RawSocket::new takes IpVersion not Some(IpVersion)); the merge had to repair a subagent helper that re-introduced Some().
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.