Red Bear OS
102d00b516
The TCP three-way handshake completion (initiator's ACK after SYN-ACK) arrives on the ORIGINAL direction, not the reply direction. Previously the SynRecv→Established transition was gated on is_orig==false, which meant it would never fire after the initial SYN-ACK reply. Connections would stay in SynRecv state forever with ConnState::New. Fix: move SynRecv→Established from reply to orig direction, per Linux nf_conntrack_proto_tcp.c (TCP_CONNTRACK_SYN_RECV fires on IP_CT_DIR_ORIGINAL packets). Reply direction now only handles: - SYN-ACK from responder (SynSent→SynRecv) - FIN from responder (Established→FinWait) - Second FIN from responder (FinWait→TimeWait) - TimeWait timeout extension Orig direction now handles: - ACK from initiator (SynRecv→Established) - FIN from initiator (Established→FinWait) - Second FIN from initiator (FinWait→TimeWait) RST still closes from either direction. All 31 tests pass.
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.