NixOS
A Linux distribution built on the Nix package manager. Its core features include declarative system configuration, reproducible builds, and atomic upgrades with rollback support, allowing the entire system state to be described as code.
Timeline (last 90 days)
NixOS suits users who frequently reinstall systems, manage multiple machines, or have requirements for long-term environmental maintainability, and does not suit users who want out-of-the-box usability and are unwilling to learn a new paradigm.
NixOS has a steep learning curve; beginners need to understand concepts such as derivations and flakes, and a common community complaint is that documentation is scattered and error messages are cryptic.
A system generation contains the exact versions of the kernel, initrd, system services and all dependencies, and is written as a complete boot entry into the GRUB or systemd-boot menu.
NixOS generates an immutable system generation on each system build or update, and old generations are fully retained in the boot menu.
The core of NixOS is writing the entire system state into a declarative configuration file (configuration.nix), managing the system by describing the state the system should be in rather than through step-by-step operations.
NixOS system upgrades are atomic operations: either they fully succeed or they fully fail, with no intermediate state.
Organizations such as GNOME, KDE, the Software Freedom Conservancy, Fedora and NixOS are also alleged to show similar politicization tendencies.
Nix is a package manager and operating system configuration framework with reproducible builds as its core design philosophy, fully declaring and isolating all dependencies of each software package to ensure consistent installation results on any machine.
In an immutable OS, the system partition is read-only at runtime and updates are completed through atomic image replacement; SteamOS 3.0, Fedora Silverblue, and NixOS all adopt this design.
NixOS's declarative configuration is implemented through the Nix package manager, with the system's packages, configuration files, and service parameters all written into a configuration.nix text file.
12 more timeline events
All Facts (20)
NixOS is a Linux distribution known for its declarative configuration and reproducible builds, describing the entire system state as code through the Nix package manager.
60%UnverifiedNixOS suits users who frequently reinstall systems, manage multiple machines, or have requirements for long-term environmental maintainability, and does not suit users who want out-of-the-box usability and are unwilling to learn a new paradigm.
50%UnverifiedNixOS has a steep learning curve; beginners need to understand concepts such as derivations and flakes, and a common community complaint is that documentation is scattered and error messages are cryptic.
50%UnverifiedNixOS system upgrades are atomic operations: either they fully succeed or they fully fail, with no intermediate state.
50%UnverifiedA system generation contains the exact versions of the kernel, initrd, system services and all dependencies, and is written as a complete boot entry into the GRUB or systemd-boot menu.
50%UnverifiedNixOS generates an immutable system generation on each system build or update, and old generations are fully retained in the boot menu.
50%UnverifiedThe core of NixOS is writing the entire system state into a declarative configuration file (configuration.nix), managing the system by describing the state the system should be in rather than through step-by-step operations.
50%UnverifiedOrganizations such as GNOME, KDE, the Software Freedom Conservancy, Fedora and NixOS are also alleged to show similar politicization tendencies.
50%UnverifiedNix is a package manager and operating system configuration framework with reproducible builds as its core design philosophy, fully declaring and isolating all dependencies of each software package to ensure consistent installation results on any machine.
50%UnverifiedIn an immutable OS, the system partition is read-only at runtime and updates are completed through atomic image replacement; SteamOS 3.0, Fedora Silverblue, and NixOS all adopt this design.
50%UnverifiedNixOS's declarative configuration is implemented through the Nix package manager, with the system's packages, configuration files, and service parameters all written into a configuration.nix text file.
50%UnverifiedNixOS supports atomic system updates and multi-generation rollbacks, allowing one-click switching to the last known working state from the boot menu.
50%UnverifiedNixOS supports atomic upgrades and rollbacks, allowing the system to revert to the previous stable version with a single operation if an update fails.
50%UnverifiedCompared to traditional choices such as Ubuntu and Debian, NixOS has a steeper learning curve.
50%UnverifiedNixOS describes the complete system state through the /etc/nixos/configuration.nix file, and after running nixos-rebuild switch, the system converges to that description.
50%UnverifiedNixOS adopts a declarative system configuration paradigm where users describe the desired state of the system in the Nix language; configurations can be versioned, reproduced, and rolled back, but the learning curve is extremely steep.
50%UnverifiedLarge language models (such as ChatGPT, Claude, and Gemini) can help users write Nix configuration files, allowing users to bypass the need to learn the Nix language itself.
50%UnverifiedNixOS is based on the Nix functional package manager and declaratively defines the entire operating system with a single Nix expression, achieving system-level reproducibility, but with a very steep learning curve.
50%UnverifiedOmarchy's choice of Arch over NixOS means it is less thorough in system-level reproducibility than NixOS, but in exchange offers lower cognitive load and broader ecosystem compatibility.
50%UnverifiedThe Netherlands is advancing the construction of an alternative software ecosystem based on NixOS in order to reduce dependence on Microsoft products.
50%