NixOS

NixOS is a Linux distribution built on top of the Nix package manager. It uses declarative configuration and allows reliable system upgrades. Two main branches are offered: current Stable release and Unstable following latest development. Although NixOS started as a research project, it is a fully functional and usable operating system. NixOS has tools dedicated to DevOps and deployment tasks.
History.
NixOS started as a research project by Eelco Dolstra in 2003.
The Stichting NixOS was founded in 2015 and aims to support projects like NixOS that implement the purely functional deployment model.
Versions.
NixOS follows a cadenced releasing, twice a year. This used to happen around March and September but, starting with 21.05, NixOS targets May and November instead. Each version number has the following format: "YY.MM".
For example: "20.03" is the version released around March 2020.
Besides that, each version is named, such as “Markhor” for the release 20.03.
Features.
Declarative system configuration model.
In NixOS, the entire operating system – the kernel, applications, system packages, configuration files, and so on – is built by the Nix package manager from a description in a functional build language. This means that building a new configuration cannot overwrite previous configurations.
A NixOS system is configured by writing a specification of the functionality that the user wants on their machine in a global configuration file. For instance, here is a minimal configuration of a machine running an SSH daemon:
 boot.loader.grub.device = "/dev/sda";
 fileSystems."/".device = "/dev/sda1";
 services.sshd.enable = true;
After changing the configuration file, the system can be updated using the codice_1 command. This command does everything necessary to apply the new configuration, including downloading and compiling packages and generating configuration files.
Reliable upgrades.
Since Nix files are pure and declarative, evaluating them will always produce the same result, regardless of what packages or configuration files are on the system. Thus, upgrading a system is as reliable as reinstalling from scratch.
Atomic upgrades.
NixOS has a transactional approach to configuration management making configuration changes such as upgrades atomic. This means that if the upgrade to a new configuration is interrupted – say, the power fails half-way through – the system will still be in a consistent state: it will either boot in the old or the new configuration. In other systems, a machine might end up in an inconsistent state, and may not even boot anymore.
Rollbacks.
If after a system update the new configuration is undesirable, it can be rolled back using a special command (codice_2). Every system configuration version automatically shows up at the system boot menu. If the new configuration crashes or does not boot properly, an older version can be selected. Rollbacks are lightweight operations that do not involve files being restored from copies.
Reproducible system configurations.
NixOS's declarative configuration model makes it easy to reproduce a system configuration on another machine. Copying the configuration file to the target machine and running the system update command generates the same system configuration (kernel, applications, system services, and so on) except for parts of the system not managed by the package manager such as user data.
Source-based model, with binaries.
The Nix build language used by NixOS specifies how to build packages from source. This makes it easy to adapt the system to user needs. However, building from source being a slow process, the package manager automatically downloads pre-built binaries from a cache server when they are available. This gives the flexibility of a source-based package management model with the efficiency of a binary model.
Consistency.
The Nix package manager ensures that the running system is consistent with the logical specification of the system, meaning that it will rebuild all packages that need to be rebuilt. For instance, if the kernel is changed then the package manager will ensure that external kernel modules will be rebuilt. Similarly, when a library is updated it ensures that all the system packages use the new version, even packages statically linked to it.
Multi-user package management.
There is no need for special privileges to install software in NixOS. In addition to the system-wide profile, every user has a dedicated profile in which they can install packages. Nix also allows multiple versions of a package to coexist, so different users can have different versions of the same package installed in their respective profiles. If two users install the same version of a package, only one copy will be built or downloaded, and Nix's security model ensures that this is secure.
Implementation.
NixOS is based on the Nix package manager that stores all packages in isolation from each other in the package store.
Installed packages are identified by a cryptographic hash of all input used for their build. Changing the build instructions of a package modifies its hash and that will result in a different package installed in the package store. This system is also used to manage configuration files ensuring that newer configurations are not overwriting older ones.
An implication of this is that NixOS doesn't follow the Filesystem Hierarchy Standard. The only exceptions are a symlink /bin/sh to the version of bash in the Nix store (like this: codice_3); and while NixOS does have an /etc directory to keep system-wide configuration files, most files in that directory are symlinks to generated files in /nix/store such as codice_4. Not using global directories such as /bin is part of what allows multiple versions of a package to coexist.
Reception.
Jesse Smith reviewed NixOS 15.09 for DistroWatch Weekly. Smith wrote:
DistroWatch Weekly also has a review of NixOS 17.03, written by Ivan Sanders.