Software ecosystem
FreeBSD
FreeBSD provides the upstream operating-system foundation for CheriBSD, while upstreaming work determines which CHERI-related changes can become broadly maintained.
Why it matters
The relationship provides broad software coverage and a path for comparing conventional and capability-aware system behaviour.
In brief
FreeBSD provides the upstream operating-system foundation from which CheriBSD was developed. Its kernel, userland, ports collection and permissively licensed code base offered a realistic system for adapting C and C++ software to CHERI.
Separate upstream FreeBSD from CheriBSD when recording status. A change may exist in a CHERI research branch, be proposed upstream, or have landed in a FreeBSD release; each state implies a different maintenance and deployment risk.
Key considerations
1. Baseline
Use FreeBSD behaviour and interfaces to understand what CheriBSD preserves or changes.
2. Ports
Track which applications and libraries build and run under the selected CHERI ABI.
3. Upstream
Distinguish CheriBSD research changes from features accepted into upstream FreeBSD and plan maintenance accordingly.
Evidence and caveats
FreeBSD does not become CHERI-capable simply by running on a related architecture; use CheriBSD and its documented toolchain for CHERI protection.
Treat build, test, integration, upstream and maintained support as distinct states. Name the target and last verified date.