An unofficial NixOS fork that creates a reproducible, declarative FreeBSD distribution using the Nix package manager.
NixBSD is an unofficial fork of NixOS that replaces the Linux kernel with the FreeBSD kernel, creating a reproducible and declarative BSD-based operating system. It uses the Nix package manager to manage system configurations, allowing users to define their entire OS state in code for consistent deployments. The project aims to bring the benefits of NixOS—like atomic upgrades and isolated dependencies—to the FreeBSD ecosystem.
System administrators, DevOps engineers, and developers interested in reproducible infrastructure who prefer FreeBSD's kernel and licensing but want Nix's declarative configuration management. It's also for NixOS users curious about BSD compatibility.
Developers choose NixBSD to get the reliability and features of FreeBSD combined with the powerful, declarative system management of Nix. It offers a unique open-source alternative for those seeking reproducible BSD systems without manual configuration drift.
An unofficial NixOS fork with a FreeBSD kernel
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Allows the entire OS configuration to be defined in code, enabling reproducible builds and consistent deployments, as emphasized in the key features.
Uses the FreeBSD kernel with BSD licensing and features like ZFS and jails, providing a robust base while maintaining Nix's management benefits.
Leverages Nix for dependency isolation and atomic upgrades, ensuring system reliability and easy rollbacks, core to the project's value proposition.
Includes built-in tooling to create and run virtual machine images from configurations, facilitating easy testing without physical hardware, as shown in the README.
The project is explicitly experimental, lacking stability and long-term support, which the README acknowledges by noting upstream integration is unlikely soon.
Building VM images can take over 8 hours and require over 30GiB of disk space for closure info, making it impractical for resource-constrained environments.
The binary cache substituter requires trusting an unofficial source, posing potential security risks due to possible malicious modifications, as warned in the README.
Focused only on FreeBSD with no active work for other BSDs, and upstream changes are unlikely, restricting broader ecosystem adoption and compatibility.