NixOS 17.09 released, independently developed GNU / Linux distribution

NixOS 17.09 has been released, in addition to adding many new and upgraded packages, GNOME has been upgraded to 3.24, KDE Plasma upgrades to 5.10, KDE Applications upgrade to 17.08.1, KDE Frameworks upgrade to 5.37.
NixOS is an independent development of the GNU / Linux distribution, which aims to improve the status of system configuration management. In NixOS, the entire operating system, including the kernel, applications, system packages, configuration files, all created by the Nix package manager. Nix stores all packages in a separate way from each other, so there is no directory like / bin, / sbin, / lib, / usr; instead, all packages are stored in / nix / store. Other innovative features of NixOS include reliable upgrades, rollback, reproducible system configurations, binary code based on source file management models, and multiuser package management. Although NixOS is a research project, it is a functional and usable operating system that enables hardware detection, use KDE as the default desktop, and systemd for system service management.
There are the following noteworthy updates:
  • The user handling now keeps track of deallocated UIDs/GIDs. When a user or group is revived, this allows it to be allocated the UID/GID it had before. A consequence is that UIDs and GIDs are no longer reused.
  • The module option services.xserver.xrandrHeads now causes the first head specified in this list to be set as the primary head. Apart from that, it’s now possible to also set additional options by using an attribute set, for example:
    { services.xserver.xrandrHeads = [
          output = "DVI-0";
          primary = true;
          monitorConfig = ''
            Option "Rotate" "right"

    This will set the DVI-0 output to be the primary head, even though HDMI-0 is the first head in the list.

  • The handling of SSL in the services.nginx module has been cleaned up, renaming the misnamed enableSSL to onlySSL which reflects its original intention. This is not to be used with the already existing forceSSL which creates a second non-SSL virtual host redirecting to the SSL virtual host. This by chance had worked earlier due to specific implementation details. In case you had specified both please remove the enableSSL option to keep the previous behaviour.

    Another addSSL option has been introduced to configure both a non-SSL virtual host and an SSL virtual host with the same configuration.

    Options to configure resolver options and upstream blocks have been introduced. See their information for further details.

    The port option has been replaced by a more generic listen option which makes it possible to specify multiple addresses, ports and SSL configs dependant on the new SSL handling mentioned above.


Leave a Reply

Your email address will not be published. Required fields are marked *