This article has multiple issues. Please help improve it or discuss these issues on the talk page . (Learn how and when to remove these messages)
|
Developer | NixOS contributors NixOS Foundation [1] [2] |
---|---|
Written in | Nix expression language [note 1] |
OS family | Linux (Unix-like) |
Working state | Current |
Source model | Open source |
Initial release | 0.1 / June 3, 2003 |
Latest release | 24.11 / 30 November 2024 |
Repository | |
Marketing target | General purpose |
Package manager | Nix |
Platforms | i686, x86-64, AArch64 |
Kernel type | Monolithic (Linux kernel) |
License | MIT [3] [note 2] |
Official website | nixos |
NixOS is a free and open source Linux distribution based on the Nix package manager. NixOS uses an immutable design and an atomic update model. [4] Its use of a declarative configuration system allows reproducibility and portability. [5]
NixOS is configured using composable modules, and relies on packages defined in the Nixpkgs project. Package recipes and configurations are written in the purpose-built "Nix language" that ships with the Nix package manager.
This section needs expansion. You can help by adding to it. (December 2023) |
Nix began in 2003 as a research project led by Eelco Dolstra, who sought to develop a system for reliable software deployment. This work culminated in Dolstra's Ph.D. thesis, The Purely Functional Software Deployment Model, which proposed a novel approach to declarative, functional software configuration. His research, supervised by Eelco Visser at Utrecht University, laid the theoretical groundwork for Nix. [6] [7]
In 2006, NixOS was introduced as part of Armijn Hemel's Master's thesis, which explored applying Nix principles to a Linux distribution. This led to the creation of a unique, declarative configuration model that distinguished NixOS from other operating systems. [8]
The NixOS Foundation was established in 2015 in the Netherlands to support projects that implement the purely functional deployment model, ensuring the ongoing development and sustainability of NixOS and its ecosystem. [9]
This section may contain information not important or relevant to the article's subject.(December 2024) |
The first NixOS community wiki was launched around 2010–2011 to centralize documentation and support collaborative knowledge-sharing. However, as community interest in maintaining the wiki waned, outdated and incorrect information accumulated, reducing its usefulness. [10]
In November 2015, Rok Garbas highlighted the decaying state of the wiki in his talk Make Nix Friendlier for Beginners, sparking widespread discussion in the community. While many developers argued that the Nix* manuals were a better repository for official documentation, no immediate solution was implemented. [11]
By mid-2016, spam bots had overwhelmed the wiki due to insufficient protection, leading to its official lockdown in August of that year. In February 2017, a GitHub issue was opened to discuss unlocking the wiki, but the debate resulted in no resolution. Finally, in May 2017, the wiki was permanently disabled, with an archive of its content made available on Archive.org. [12]
To fill the void, Jörg Thalheim (Mic92) launched the nixos-users GitHub wiki in April 2017. Although this platform allowed quick edits and community contributions, it lacked features such as search functionality and a table of contents. Shortly thereafter, Tristan Helmich (fadenb) created a new MediaWiki-based wiki on his own initiative, citing the poor user experience of the GitHub wiki. Felix Richter (makefu) later migrated content from the GitHub wiki to Helmich’s platform, ensuring its sustainability. [13]
In January 2024, a new initiative to establish an official wiki was launched, resulting in the wiki instance currently in use. This revival reflects the community's renewed commitment to maintaining accurate, centralized documentation for NixOS users. [14]
Name | Date |
---|---|
NixOS 13.10 "Aardvark" | October 2013 |
NixOS 14.04 "Baboon" | April 2014 |
NixOS 14.12 "Caterpillar" | December 2014 |
NixOS 15.09 "Dingo" | September 2015 |
NixOS 16.03 "Emu" | March 2016 |
NixOS 16.09 "Flounder" | September 2016 |
NixOS 17.03 "Gorilla" | March 2017 |
NixOS 17.09 "Hummingbird" | September 2017 |
NixOS 18.03 "Impala" | March 2018 |
NixOS 18.09 "Jellyfish" | September 2018 |
NixOS 19.03 "Koi" | March 2019 |
NixOS 19.09 "Loris" | September 2019 |
NixOS 20.03 "Markhor" | March 2020 |
NixOS 20.09 "Nightingale" | September 2020 |
NixOS 21.05 "Okapi" | May 2021 |
NixOS 21.11 "Porcupine" | November 2021 |
NixOS 22.05 "Quokka" | May 2022 |
NixOS 22.11 "Raccoon" | November 2022 |
NixOS 23.05 "Stoat" | May 2023 |
NixOS 23.11 "Tapir" | November 2023 |
NixOS 24.05 "Uakari" | May 2024 |
NixOS 24.11 "Vicuna" | November 2024 |
NixOS 25.05 "Warbler" | May 2025 |
NixOS publishes stable releases twice a year, around the end of May and the end of November. [15] [16] [17]
In NixOS, the entire operating system—including the kernel, applications, system packages, and configuration files—is built by the Nix package manager from a description in the Nix language. Building a new version will not overwrite previous versions. [18]
A NixOS system is configured by writing a specification of the functionality that the user wants on their machine in a global configuration file (typically located in /etc/nixos
). The following is a minimal specification of a machine running an SSH daemon: [19]
{ boot.loader.grub.device="/dev/sda"; fileSystems."/".device="/dev/sda1"; services.sshd.enable=true;}
After changing the specification file, the system can be updated using the nixos-rebuild
command. This does everything necessary to create the new version of the system, including downloading and installing packages, and generating configuration files.
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.
NixOS has a transactional approach to configuration management, making configuration changes such as upgrades atomic. For example, if an upgrade to a new configuration is interrupted by power failure, the system will still be in a consistent state: it will either boot in the old or the new configuration. [20]
If, after a system update, the new configuration is undesirable, it can be rolled back using a special command (nixos-rebuild switch --rollback
). Every system configuration version automatically shows up in 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. [21]
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.
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. It is possible to disable the binary cache and force building from source by using --option substitute false
as an argument. Changing any of the build options from the defaults will also cause packages to be built from source. This gives the flexibility of a source-based package management model, with the efficiency of a binary model. [22]
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.
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. Nix's security model ensures that this is secure, because only the users explicitly trusted by the system configuration are allowed to use build parameters that would allow them to control the content of a derivation's output (such as adding impurities to the sandbox, or using an untrusted substituter).[ clarification needed ] Without those parameters, paths can only be substituted from a substituter trusted by the system, or a local sandboxed build which is implicitly trusted.
NixOS is based on the Nix package manager, which 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 being installed in the package store. This system is also used to manage configuration files, ensuring that newer configurations do not overwrite older ones.
An implication of this is that NixOS does not follow the Filesystem Hierarchy Standard. The only exceptions are that a /bin/sh symlink is created to the version of bash in the Nix store (e.g. /nix/store/s/5rnfzla9kcx4mj5zdc7nlnv8na1najvg-bash-4.3.43/
), 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 /nix/store/s2sjbl85xnrc18rl4fhn56irkxqxyk4p-sshd_config
. Not using global directories such as /bin is part of what allows multiple versions of a package to coexist.
Jesse Smith, reviewing NixOS 15.09 for DistroWatch Weekly in 2015, [23] wrote:
I very much like the way NixOS takes the worry out of upgrading packages by placing each change in its own "generation" and I found, from the end user's point of view, NixOS worked just the same as any other Linux distribution. Setting up NixOS is not for beginners, and I do not think NixOS is intended to be used as a general purpose desktop operating system. But what NixOS does do is give us a useful playground in which to examine the Nix package manager and I think this is very interesting technology which deserves further exploration and adoption by additional distributions.
A 2022 review of NixOS 21.11 "Porcupine" in Full Circle magazine concluded:
Overall NixOS Gnome 21.11 impresses as serious, neat and elegant. If you are a fan of the unmodified Gnome desktop, then you will find a lot to like here. The downside of this distribution is the steep learning curve for package management, including updates and the like. No matter which distribution you come from, you will have much to learn to be able to make Nix work well for you on the command-line. [24]
NixOS 22.11 "Raccoon" reviewed by Liam Proven at The Register:
Compared to reports of NixOS from just two or three years ago, we found it was very simple to get it installed and working. This suggests that the tools are maturing well and reaching a certain level of polish, but from a first-time perspective we have no prior baseline to compare against. This is very much not a traditional distro, or even a traditional Unix, but it works and we can see the appeal. [25]
NixOS 23.11 "Tapir" reviewed by Jesse Smith at DistroWatch:
NixOS is a rare gem in that I don't think I ran into any errors while I was using it. The distribution was stable, it worked well with my hardware, and I didn't run into a single issue while running it. I feel NixOS is well worth a try, especially if you're a system administrator and want to deploy (or maintain) identical distributions across multiple machines. [26]
A Linux distribution is an operating system that includes the Linux kernel for its kernel functionality. Although the name does not imply product distribution per se, a distro, if distributed on its own, is often obtained via a website intended specifically for the purpose. Distros have been designed for a wide variety of systems ranging from personal computers to servers and from embedded devices to supercomputers.
A package manager or package-management system is a collection of software tools that automates the process of installing, upgrading, configuring, and removing computer programs for a computer in a consistent manner.
Gentoo Linux is a Linux distribution built using the Portage package management system. Unlike a binary software distribution, the source code is compiled locally according to the user's preferences and is often optimized for the specific type of computer. Precompiled binaries are available for some packages. Gentoo runs on a wide variety of processor architectures.
GoboLinux is a Linux distribution whose most prominent feature is a reorganization of the traditional Linux file system. Rather than following the Filesystem Hierarchy Standard like most Unix-like systems, each program in a GoboLinux system has its own subdirectory tree, where all of its files may be found. Thus, a program "Foo" has all of its specific files and libraries in /Programs/Foo
, under the corresponding version of this program at hand. For example, the commonly known GCC compiler suite version 8.1.0, would reside under the directory /Programs/GCC/8.1.0
.
Portage is a package management system originally created for and used by Gentoo Linux and also by ChromeOS, Calculate, and Funtoo Linux among others. Portage is based on the concept of ports collections. Gentoo is sometimes referred to as a meta-distribution due to the extreme flexibility of Portage, which makes it operating-system-independent. The Gentoo/Alt project was concerned with using Portage to manage other operating systems, such as BSDs, macOS and Solaris. The most notable of these implementations is the Gentoo/FreeBSD project.
Arch Linux is an independently developed Linux distribution designed with a rolling-release model. The default Arch Linux installation is intentionally minimal, and is configured by the user during installation so they may add only what they require. Arch is the basis for a multitude of other distributions, such as Manjaro, EndeavourOS, and Parabola.
Dependency hell is a colloquial term for the frustration of some software users who have installed software packages which have dependencies on specific versions of other software packages.
TrueOS is a discontinued Unix-like, server-oriented operating system built upon the most recent releases of FreeBSD-CURRENT.
Squashfs is a compressed read-only file system for Linux. Squashfs compresses files, inodes and directories, and supports block sizes from 4 KiB up to 1 MiB for greater compression. Several compression algorithms are supported. Squashfs is also the name of free software, licensed under the GPL, for accessing Squashfs filesystems.
Software remastering is software development that recreates system software and applications while incorporating customizations, with the intent that it is copied and run elsewhere for "off-label" usage. The term comes from remastering in media production, where it is similarly distinguished from mere copying.
Nix is a cross-platform package manager for Unix-like systems, and a tool to instantiate and manage those systems, invented in 2003 by Eelco Dolstra.
According to the Free Software Foundation Latin America, Linux-libre is a modified version of the Linux kernel that contains no binary blobs, obfuscated code, or code released under proprietary licenses. In the Linux kernel, those types of code are mostly used for proprietary firmware images. While generally redistributable, they do not give the user the freedom to audit, modify, or, consequently, redistribute their modified versions. The GNU Project keeps Linux-libre in synchronization with the mainline Linux kernel.
Salix OS is a multi-purpose Linux distribution based on Slackware.
Kiwix is a free and open-source offline web browser created by Emmanuel Engelhart and Renaud Gaudin in 2007. It was first launched to allow offline access to Wikipedia, but has since expanded to include other projects from the Wikimedia Foundation, public domain texts from Project Gutenberg, many of the Stack Exchange sites, and many other resources. Available in more than 100 languages, Kiwix has been included in several high-profile projects, from smuggling operations in North Korea to Google Impact Challenge's recipient Bibliothèques Sans Frontières.
GNU Guix is a functional cross-platform package manager and a tool to instantiate and manage Unix-like operating systems, based on the Nix package manager. Configuration and package recipes are written in Guile Scheme. GNU Guix is the default package manager of the GNU Guix System distribution.
Subgraph OS was a Debian-based project designed to be resistant to surveillance and interference by sophisticated adversaries over the Internet. It has been mentioned by Edward Snowden as showing future potential.
postmarketOS is an operating system primarily for smartphones, based on the Alpine Linux distribution.