vasilito
a3b8a34d9c
In drivers/acpid/src/scheme.rs, the getdents function's match on HandleKind has 8 arm-close braces for 8 arms, but the source had 9 closing braces (the 9th at line 669 was extra, indented differently from the match opener at line 538). Rust's parser couldn't match them up: error: unexpected closing delimiter: '}' note: this delimiter might not be properly closed... note: ...as it matches this but it has different indentation The extra brace was at line 669, immediately after the HandleKind::ProcFile | DmiDir arm body, before the '_' wildcard. Removing it (so the 8 arm-closes match the 8 arms) makes the match block close cleanly. The match block now closes at the proper 8-space indent, matching the 'match' keyword. This is a pre-existing bug in the Phase II.X.W commit 'dcd70a1 acpid: Phase II.X.W S3 wake handling + kstop_enter_s3 helper'. The brace was probably added by mistake during one of the Phase II.X.W edits. The Phase II.X.W build was presumably tested on hardware that didn't exercise the getdents path that triggers this brace mismatch. Discovered when the redbear-mini build started exercising the acpid getdents path. Fix: delete the extra brace.
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.