Red Bear OS
5d1ed3178d
The Phase 7 subagent added proptest blocks in filter/table.rs and
filter/conntrack.rs that did not compile against proptest 1.4
in Cargo.toml. The 'rules in ...' tuple syntax and the
'Ipv6Address::from_bytes' call are proptest 1.5+ / smoltcp 0.13+
features that aren't available in the actual installed versions.
The fuzz targets I added used 'EthernetProtocol::from(u8, u8)',
'Ipv4Packet::protocol()', and 'UdpPacket::length()' methods that
are not in the installed smoltcp 0.13.1.
This commit reverts those additions and deletes the fuzz
directory entirely. The original 31 netstack unit tests are
preserved. The Phase 7 fuzzer and proptest work is now [DEFERRED]
until the smoltcp API surface is verified and proptest is bumped
to 1.5+ (or the test syntax is rewritten for 1.4).
Verified: filter/{table,conntrack}.rs revert to their HEAD state,
and netstack/Cargo.toml no longer has the broken
proptest dev-dependency. Cargo.lock is regenerated by the
upcoming build.
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.