315
The Netherlands joins Europe's gradual migration from Windows to Linux on government PCs
(www.xda-developers.com)
this post was submitted on 25 Sep 2026
315 points (99.7% liked)
Linux
15060 readers
137 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I wonder why NixOS. I've never used it, so my surface level understanding guesses that it's related to the declarative config, but we have Ansible/Chef/Puppet.
Pretty sure it's because NixOS is reproducible. You can send your configs to your friend and they'll get a file-for-file identical copy of NixOS to yours (obviously except the user files)
I never used it too, but it feels like something so nice for research labs
Or for a fleet of hardware that you control and want to have predictable outcomes.
NixOS goes deeper than Ansible/Chef/Puppet. Those options use a declarative config, but they operate on a mutable system - in particular a system with a mutable package manager. They try to run the necessary operations to change the system state to match the config. But it's not guaranteed that you get exactly the same state if you roll back and forth between declarative config revisions, especially since there are parts of system state outside the scope of the Ansible/Chef/Puppet config.
OTOH the Nix package manager is immutable down through the package manager, and also through system config files (which are linked to the current config generation in the Nix store). If you use a lock file then the NixOS config describes the exact state of every package, and of every managed config file.
Ah, that's cool. Super useful for a sysadmin.