Red Bear OS
b887d2b450
The 0.13 release line contains critical TCP correctness fixes that backport into Red Bear: - RFC 6298 retransmit backoff (was using a non-standard exponential backoff with a different initial value) - zero-window probes (the previous code did not implement them, so connections stalled when the receiver advertised a 0 window) - FIN retransmit in CLOSING state (the prior code only retransmitted FIN from FIN-WAIT-1 and never recovered from a lost second FIN) - SYN crash on unspecified address (the kernel would panic on a SYN with src == 0.0.0.0; the 0.13.1 fix returns a RST) - IPv6 SLAAC support on the wire when the upstream proto-ipv6 feature is enabled (Red Bear already enables proto-ipv6) The code in scheme/ip.rs is already in 0.13.1 form (RawSocket::new takes IpVersion directly, not Option<IpVersion>) and scheme/icmp.rs already uses the 0.13.1 ip_protocol() signature, so the migration is intentionally restricted to the version field. The Cargo.lock will be regenerated by the canonical build (cookbook uses --locked, so the next build-redbear.sh run will refresh the lockfile after the workspace can resolve smoltcp 0.13.1).
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.