The PRoot Team welcomes, and depends, on contributions from students and collaborators in the open source and academic communities. Contributions can be made in a number of ways, a few examples are:
- Code patches via pull requests
- Documentation improvements
- Bug reports and patch reviews
Please include as much detail as you can. Let us know your host kernel
version, e.g, uname -a, host/guest distribution, e.g. cat /etc/os-release,
and the PRoot/CARE version number. If you get an error please include the full
error and/or traceback. Issues are tracked on GitHub at <https://github.com/proot-me/proot/issues>,
or can also be sent via the mailing list.
Once you are happy with your changes or you are ready for some feedback, push it to your fork and send a pull request. For a change to be accepted it will most likely need to have updated tests and/or documentation. New features require additional tests in order to be included in a future release.
- Contributing to Open Source Projects
- How To Ask Questions The Smart Way
- Indentation Style - Wikipedia
Tracking Linux kernel and ABI changes
PRoot intercepts syscalls via ptrace and translates paths at the syscall ABI level, so kernel changes can directly affect correctness and completeness. Contributors working on core ptrace or syscall handling should monitor:
- linux-api@vger.kernel.org — list where all proposed syscall and ABI changes are reviewed before merging
- LWN.net — in-depth coverage of kernel development
- kernelnewbies.org/LinuxChanges — per-release summaries of user-visible kernel changes
- torvalds/linux:
arch/x86/entry/syscalls/syscall_64.tbl,syscall_32.tbl,include/uapi/linux/ptrace.h— syscall tables and ptrace API