It has an interesting approach in terms of organizing disk layout. That solves a lot of problems (dependency hell, immutability, reproducibility, automatic changes etc) and seems to be overall better, but it’s a huge paradigm shift and step learning curve so many people get discouraged.
The whole point of NixOS is that it’s “immutable” and “declarative”.
In essence this means that you store the entire system configuration in a bunch of text files in a single directory. So your bootloader configuration, all your installed packages, every system service, every filesystem mounts, and even your partition layout and dotfiles, all of it in a common shared configuration.
There’s even a concept called flakes, which lock the specific version of everything, so if you copy all your config to another computer (or reinstall), then applying the config will restore every system configuration to exactly that state. So if you like how you configured your machine, and want another machine exactly like it, you just copy all your configuration to the other machine, and run the nixos-rebuild command. Now the two machines are configured exactly identically, all the same package, all the same services, all the same configurations, even all the same versions if you make use of flakes.
It also means that you can reason about your entire system setup just by looking at those configs. Is that piece of config in the files? Then that’s how your system is configured. If that piece of config isn’t there, then that is not how your system is configured.
Want to install an application, just add it to the list in your config, and run the nixos-rebuild command. Now you have that installed. Don’t want it anymore? Just remove it from the list, and rerun nixos-rebuild.
On top of that NixOS stores every generation of your config, so even if you break something, you just restart and pick the previous config generation, and your system starts up exactly as it was before you broke it, and you can go and resolve the issue in the config that broke your system.
If you’ve ever done any programming, and made use of a dependency management tool that stores a dependency lock file, this is very similar, but for your entire operating system.
If you’ve ever managed infrastructure via Terraform, then this feels like that, but for your entire system configuration.
Imagine your package manager being a config file. Imagine your mount points, locale, desktop environment, application settings, and virtually every aspect of your system being defined in a single configuration file.
genuinely what is so special about nixos??? i know literally nothing about it and i currently have a spare chromebook i could test it on right now
It’s afair the first immutable distro which is configured by a single config file. Thus easily reproducible.
It has an interesting approach in terms of organizing disk layout. That solves a lot of problems (dependency hell, immutability, reproducibility, automatic changes etc) and seems to be overall better, but it’s a huge paradigm shift and step learning curve so many people get discouraged.
The whole point of NixOS is that it’s “immutable” and “declarative”.
In essence this means that you store the entire system configuration in a bunch of text files in a single directory. So your bootloader configuration, all your installed packages, every system service, every filesystem mounts, and even your partition layout and dotfiles, all of it in a common shared configuration.
There’s even a concept called flakes, which lock the specific version of everything, so if you copy all your config to another computer (or reinstall), then applying the config will restore every system configuration to exactly that state. So if you like how you configured your machine, and want another machine exactly like it, you just copy all your configuration to the other machine, and run the nixos-rebuild command. Now the two machines are configured exactly identically, all the same package, all the same services, all the same configurations, even all the same versions if you make use of flakes.
It also means that you can reason about your entire system setup just by looking at those configs. Is that piece of config in the files? Then that’s how your system is configured. If that piece of config isn’t there, then that is not how your system is configured.
Want to install an application, just add it to the list in your config, and run the nixos-rebuild command. Now you have that installed. Don’t want it anymore? Just remove it from the list, and rerun nixos-rebuild.
On top of that NixOS stores every generation of your config, so even if you break something, you just restart and pick the previous config generation, and your system starts up exactly as it was before you broke it, and you can go and resolve the issue in the config that broke your system.
If you’ve ever done any programming, and made use of a dependency management tool that stores a dependency lock file, this is very similar, but for your entire operating system.
If you’ve ever managed infrastructure via Terraform, then this feels like that, but for your entire system configuration.
Imagine your package manager being a config file. Imagine your mount points, locale, desktop environment, application settings, and virtually every aspect of your system being defined in a single configuration file.