NixOS

Last updated
NixOS
NixOS logo.svg
Developer NixOS contributors
NixOS Foundation [1] [2]
Written in Nix expression language [note 1]
OS family Linux (Unix-like)
Working stateCurrent
Source model Open source
Initial release0.1 / 3 June 2003;21 years ago (2003-06-03)
Latest release 24.11 / 30 November 2024;50 days ago (30 November 2024)
Repository
Marketing targetGeneral purpose
Package manager Nix
Platformsfully supported: x86-64, AArch64 [3] ; limited support: i686 [4]
Kernel type Monolithic (Linux kernel)
License MIT [5] [note 2]
Official website nixos.org

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. [6] Its use of a declarative configuration system allows reproducibility and portability. [7]

Contents

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.

History

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. [8] [9]

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. [10]

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. [11]

Wiki

NixOS currently has both an official wiki located at wiki.nixos.org, and an unofficial user's wiki at nixos.wiki.

History

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. [12]

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. [13]

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 the Internet Archive. [14]

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 wiki. [15]

In January 2024, a new initiative to establish an official wiki was launched. This resulted in the official wiki currently in use, which was launched on 1 April 2024. [16] [17]

Release version history

NameDate
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. [18] [19] [20]

Features

NixOS graphical installer Nixos-installer.png
NixOS graphical installer

Declarative configuration model

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. [21]

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: [22] 

{   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.

Reliable and atomic 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.

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. [23]

Rollbacks

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. [24]

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 binary cache

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. [25]

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. 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.

Implementation

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.

Reception

Jesse Smith, reviewing NixOS 15.09 for DistroWatch Weekly in 2015, [26] 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. [27]

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. [28]

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. [29]

Notes

  1. ↑ Various other programming languages are used throughout NixOS (as of December 2023).
  2. ↑ Various other licenses are used for software included with NixOS, for example the Linux kernel is licensed under the GNU GPL version 2.0 (as of December 2023)

See also

Related Research Articles

<span class="mw-page-title-main">Linux distribution</span> Operating system based on the Linux kernel

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.

<span class="mw-page-title-main">Package manager</span> Software tools for handling softwares packages

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.

<span class="mw-page-title-main">APT (software)</span> Free software package management system

Advanced Package Tool (APT) is a free-software user interface that works with core libraries to handle the installation and removal of software on Debian and Debian-based Linux distributions. APT simplifies the process of managing software on Unix-like computer systems by automating the retrieval, configuration and installation of software packages, either from precompiled files or by compiling source code.

<span class="mw-page-title-main">GoboLinux</span> Linux distribution

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.

<span class="mw-page-title-main">Slax</span> Linux distribution

Slax is a LiveCD Linux distribution developed by Tomáš Matějíček and based on upstream customizable Linux distributions. Packages can be added by apt package manager or can be prepared as modules. The tagline for Slax refers to itself as "your pocket operating system".

<span class="mw-page-title-main">Arch Linux</span> Rolling release Linux distribution

Arch Linux is an open source, rolling release Linux distribution. Arch Linux is kept up-to-date by regularly updating the individual pieces of software that it comprises. Arch Linux is intentionally minimal, and is meant to be configured by the user during installation so they may add only what they require.

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.

<span class="mw-page-title-main">TrueOS</span> Unix-like, desktop-oriented operating system

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.

<span class="mw-page-title-main">Software remastering</span> Type of software development

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.

<span class="mw-page-title-main">RPM Package Manager</span> Package management system

RPM Package Manager (RPM) is a free and open-source package management system. The name RPM refers to the .rpm file format and the package manager program itself. RPM was intended primarily for Linux distributions; the file format is the baseline package format of the Linux Standard Base.

<span class="mw-page-title-main">Tiny Core Linux</span> Lightweight Linux distribution

Tiny Core Linux (TCL) is a minimal Linux kernel based operating system focusing on providing a base system using BusyBox and FLTK. It was developed by Robert Shingledecker, who was previously the lead developer of Damn Small Linux. The distribution is notable for its small size and minimalism; additional functions are provided by extensions. Tiny Core Linux is free and open-source software licensed under the GNU General Public License version 2.

systemd Suite of system components for Linux

systemd is a software suite that provides an array of system components for Linux operating systems. The main aim is to unify service configuration and behavior across Linux distributions. Its primary component is a "system and service manager" — an init system used to bootstrap user space and manage user processes. It also provides replacements for various daemons and utilities, including device management, login management, network connection management, and event logging. The name systemd adheres to the Unix convention of naming daemons by appending the letter d. It also plays on the term "System D", which refers to a person's ability to adapt quickly and improvise to solve problems.

Alpine Linux is a Linux distribution designed to be small, simple, and secure. It uses musl, BusyBox, and OpenRC instead of the more commonly used glibc, GNU Core Utilities, and systemd. This makes Alpine one of few Linux distributions not to be based on the GNU Core Utilities or glibc.

OpenWrt is an open-source project for embedded operating systems based on Linux, primarily used on embedded devices to route network traffic. The main components are Linux, util-linux, musl, and BusyBox. All components have been optimized to be small enough to fit into the limited storage and memory available in home routers.

<span class="mw-page-title-main">GNU Guix</span> Purely functional package manager for the GNU system

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.

postmarketOS Free and open-source operating system for smartphones, based on Alpine Linux

postmarketOS is an operating system primarily for smartphones, based on the Alpine Linux distribution.

References

  1. ↑ "Community - nixos.org". Archived from the original on 2022-09-23. Retrieved 2022-09-23.
  2. ↑ "NixOS/nixos-foundation - Github". GitHub . Archived from the original on 2022-09-23. Retrieved 2022-09-23.
  3. ↑ "Download Nix & NixOS". nixos.org. Retrieved 2024-12-24.
  4. ↑ RaitoBezarius (2024-01-02). "Limited cache availability for i686 (32 bits x86) architecture". discourse.nixos.org. Retrieved 2024-12-24. […] we are removing the 32 bits ISO on the NixOS homepage, NixOS tests […]
  5. ↑ "nixpkgs/COPYING at master · NixOS/nixpkgs · GitHub". Github.com. Retrieved 2015-09-19.
  6. ↑ "What Is an Immutable Linux Distro, and Should You Use One?". HowToGeek.com. 6 December 2023. Archived from the original on 2023-12-07. Retrieved 2023-12-07.
  7. ↑ "DistroWatch.com: NixOS". Distrowatch.com. Retrieved 2015-09-19.
  8. ↑ Dolstra, Eelco (2003). "Integrating Software Construction and Software Deployment" (PDF). Software Configuration Management. Lecture Notes in Computer Science. Vol. 2649. pp. 102–117. doi:10.1007/3-540-39195-9_8. ISBN   978-3-540-14036-8. Archived from the original (PDF) on 2019-04-21.
  9. ↑ Dolstra, Eelco (2006). The Purely Functional Software Deployment Model (PDF) (Ph.D.). Archived from the original (PDF) on 2019-06-09.
  10. ↑ Dolstra, Eelco. "Purely Functional System Configuration Management". www.usenix.org. Retrieved 2024-03-04.
  11. ↑ "Stichting NixOS Foundation". Nixos.org. Retrieved 2015-09-19.
  12. ↑ "NixOS Wiki: History". NixOS Wiki. Retrieved 2024-11-28.
  13. ↑ Garbas, Rok (2015). "Make Nix Friendlier for Beginners". media.ccc.de.
  14. ↑ "NixOS Wiki Archive" . Retrieved 2024-01-01.
  15. ↑ Helmich, Tristan. "MediaWiki for NixOS" . Retrieved 2024-01-01.
  16. ↑ "NixOS Wiki: History". NixOS Wiki. Retrieved 2024-11-28.
  17. ↑ "NixOS Wiki:News". NixOS Wiki. Retrieved 2025-01-19.
  18. ↑ "Governance". Nixos.org. Archived from the original on 2020-08-16. Retrieved 2020-08-28.
  19. ↑ "Nix RFCS (Request for Comments)". GitHub . 17 December 2021.
  20. ↑ "Release Announcements". Nixos.org. Retrieved 2023-12-09.
  21. ↑ Dolstra, Eelco; Hemel, Armijn (2007-05-07). Purely Functional System Configuration Management (PDF). 11th USENIX workshop on Hot topics in operating systems. San Diego, California, USA: USENIX Association. Archived (PDF) from the original on 2020-07-10. Retrieved 2023-07-19.
  22. ↑ "About NixOS". Nixos.org. Retrieved 2015-09-19.
  23. ↑ van der Burg, Sander; Dolstra, Eelco; de Jonge, Merijn (2008-10-20). Atomic Upgrading of Distributed Systems (PDF). 1st International Workshop on Hot Topics in Software Upgrades. Nashville, Tennessee, USA: Association for Computing Machinery. doi:10.1145/1490283.1490294. ISBN   978-1-60558-304-4. Archived (PDF) from the original on 2021-11-13. Retrieved 2023-07-19.
  24. ↑ NixOS Manual - Rolling Back Configuration Changes, Nixos.org
  25. ↑ Dolstra, Eelco (2005-11-07). Secure Sharing Between Untrusted Users in a Transparent Source/Binary Deployment Model (PDF). 20th IEEE/ACM International Conference on Automated Software Engineering. Long Beach, California, USA: Association for Computing Machinery. doi:10.1145/1101908.1101933. ISBN   978-1-58113-993-8. Archived (PDF) from the original on 2021-11-13. Retrieved 2023-07-19.
  26. ↑ DistroWatch Weekly, Issue 637, 23 November 2015
  27. ↑ Hunt, Adam (28 October 2022). "Review - NixOS" (PDF). Full Circle magazine . Archived (PDF) from the original on 28 October 2022. Retrieved 28 October 2022.
  28. ↑ Proven, Liam. "NixOS 22.11 'Raccoon': Like a proof of concept you can do things with OSes".
  29. ↑ Smith, Jesse. "NixOS 23.11".
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.