distribution release , based on the package manager and providing a range of its own developments that simplify system setup and maintenance. For example, NixOS uses a single system configuration file (configuration.nix), allows for quick rollback of updates, supports switching between different system states, allows individual users to install specific packages (packages are installed in the home directory), supports simultaneous installation of multiple versions of the same program, and provides the possibility of reproducible builds. The size of the full with KDE is 1.3 GB, the reduced console version is 560 MB.
Key :
- The installer can be launched by a non-privileged user
nixos instead of root (to obtain root privileges, sudo -i is used without a password); - The Xfce desktop has been updated to version 4.14;
- The package with PHP has been updated to version 7.3. Support for PHP version 7.1 has been discontinued;
- In the GNOME 3 desktop management module, the ability to enable/disable services, applications, and additional packages such as games has been provided. The installed GNOME 3 environment is as close as possible to the original delivery. The installation of the following applications has been discontinued: accerciser, dconf-editor, evolution,
gnome-documents,
gnome-nettool,
gnome-power-manager,
gnome-todo,
gnome-tweaks,
gnome-usage,
gucharmap,
nautilus-sendto, and vinagre. The basic package includes
cheese, geary, gnome-color-manager, and orca. The service services.avahi.enable has been activated; - The versions of distribution components have been updated, including
systemd 242; - The dwm-status service and hardware.printers module have been added;
- Support for Python 2 has been discontinued.
When using Nix, packages are installed in a separate directory tree /nix/store or a subdirectory in the user directory. For example, a package is installed as /nix/store/f3a4…8a143-firefox-69.0.2/, where 'f3a4...' is a unique identifier for the package used for dependency management. Packages are packaged as containers containing the necessary components for application operation.
Dependencies can be defined between packages, with already installed dependencies being identified through scanning hash identifiers in the directory of installed packages. Both ready-made binary packages from the repository can be downloaded (only delta changes are downloaded for updates to binary packages), as well as compilation from source texts with all dependencies included. The collection of packages is presented in a special repository. .
Source: opennet.ru
