Release of the NixOS 19.03 distribution using the Nix package manager

[: ru]

Took place distribution release Nix OS 19.03based on a package manager nix and provides a number of its own developments that simplify the configuration and maintenance of the system. For example, NixOS uses a single system configuration file (configuration.nix), provides the ability to quickly roll back updates, supports switching between different system states, supports installation of individual packages by individual users (the package is placed in the home directory), simultaneous installation of several versions of one program is possible. . Full size installation image with KDE - 1 GB, an abbreviated console version - 400 MB.

All innovations:

  • The composition includes the desktop environment Pantheon, developed Elementary OS project (enable via services.xserver.desktopManager.pantheon.enable);
  • The module with the Kubernetes container orchestration system, which is divided into separate components, has been significantly redesigned. To increase security, TLS and RBAC are enabled by default;
  • Added options to systemd.services to run services in a chroot environment;
  • Added installation image for Aarch64 architecture with support
    UEFI;

  • Updated versions of distribution components, including CPython 3.7 (was 3.6);
  • Added 22 new services, including CockroachDB, bolt, lirc,
    roundcube, weechat and knot.

When using Nix, packages are installed in a separate /nix/store directory tree or a subdirectory in the user's directory. For example, a package is installed as /nix/store/f3a4h95649f394358bh52d4vf7a1f3-firefox-66.0.3/ where "f3a4h9..." is the unique package ID used to control dependencies. Packages are designed as containers containing the components necessary for the application to work.

It is possible to determine dependencies between packages by scanning the hash identifiers in the directory of installed packages to find the presence of already installed dependencies. It is possible both to download ready-made binary packages from the repository (when installing updates to binary packages, only delta changes are downloaded), or build from source with all dependencies. The collection of packages is presented in a special repository Nixpkgs.

Sourceopennet.ru

[:in]

Took place distribution release Nix OS 19.03based on a package manager nix and provides a number of its own developments that simplify the configuration and maintenance of the system. For example, NixOS uses a single system configuration file (configuration.nix), provides the ability to quickly roll back updates, supports switching between different system states, supports installation of individual packages by individual users (the package is placed in the home directory), simultaneous installation of several versions of one program is possible. . Full size installation image with KDE - 1 GB, an abbreviated console version - 400 MB.

All innovations:

  • The composition includes the desktop environment Pantheon, developed Elementary OS project (enable via services.xserver.desktopManager.pantheon.enable);
  • The module with the Kubernetes container orchestration system, which is divided into separate components, has been significantly redesigned. To increase security, TLS and RBAC are enabled by default;
  • Added options to systemd.services to run services in a chroot environment;
  • Added installation image for Aarch64 architecture with support
    UEFI;

  • Updated versions of distribution components, including CPython 3.7 (was 3.6);
  • Added 22 new services, including CockroachDB, bolt, lirc,
    roundcube, weechat and knot.

When using Nix, packages are installed in a separate /nix/store directory tree or a subdirectory in the user's directory. For example, a package is installed as /nix/store/f3a4h95649f394358bh52d4vf7a1f3-firefox-66.0.3/ where "f3a4h9..." is the unique package ID used to control dependencies. Packages are designed as containers containing the components necessary for the application to work.

It is possible to determine dependencies between packages by scanning the hash identifiers in the directory of installed packages to find the presence of already installed dependencies. It is possible both to download ready-made binary packages from the repository (when installing updates to binary packages, only delta changes are downloaded), or build from source with all dependencies. The collection of packages is presented in a special repository Nixpkgs.

Source: opennet.ru

[:]

Add a comment