{"id":181758,"date":"2026-05-27T02:48:02","date_gmt":"2026-05-27T00:48:02","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/reliz-almalinux-9-8-i-10-2"},"modified":"2026-05-27T02:48:02","modified_gmt":"2026-05-27T00:48:02","slug":"reliz-almalinux-9-8-i-10-2","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/reliz-almalinux-9-8-i-10-2","title":{"rendered":"Release of AlmaLinux 9.8 and 10.2","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
The release of AlmaLinux 10.2 has been announced, along with an update for the previous branch\u2014AlmaLinux 9.8. These releases are synchronized with Red Hat Enterprise Linux 9.8 and 10.2, and include all the changes introduced in these versions. Installation images have been prepared for the x86_64_v3, x86_64_v2, ARM64, ppc64le, and s390x architectures in the form of bootable (1 GB), minimal (1.6 GB), and full images (10 GB). Live builds with GNOME, KDE, MATE, and Xfce, as well as images for Raspberry Pi, containers, WSL (Windows Subsystem for Linux), and cloud platforms will be created later.<\/p>\n
The distribution is binary compatible with Red Hat Enterprise Linux whenever possible and can be used as a replacement for RHEL 10.2 and CentOS 10 Stream. Aside from rebranding and the removal of RHEL-specific packages, the following differences from RHEL 10.2 are noted in AlmaLinux 10.2:\n<\/p>\n
\n
A repository of packages compiled for the i686 architecture has been published, as well as Docker container images for 32-bit x86 systems. Red Hat discontinued the formation of 32-bit builds for x86 architecture with the release of RHEL 7 in 2014. In the CentOS 7 branch, the assembly of 32-bit packages continued by the CentOS Linux AltArch SIG team, but starting with the CentOS 8 branch, the creation of such builds ceased. The revival of i686 architecture builds in AlmaLinux was motivated by the desire to allow the execution of older applications available only as executables for 32-bit systems. These builds may also be useful for creating 32-bit environments for testing code in continuous integration systems and for running containers for 32-bit programs.\n
Support for the Btrfs file system has been restored. The ability to partition storage devices using Btrfs has been added to the installer, the kernel module btrfs.ko has been installed, the set of btrfs-progs utilities has been returned, and work has been done to adapt the data storage management stack to work with Btrfs. The functionality of the packages bcc, buildah, cockpit, ignition, libblockdev, libguestfs, osbuild, osbuild-composer, podman, pykickstart, python-blivet, skopeo, udisks2, and virt-v2v in environments with Btrfs has been verified. Red Hat declared the Btrfs file system as deprecated in the release of RHEL 7.4 (2017) and fully ceased its support in the RHEL 8 branch.\n<\/li>\n
By default, the CRB (CodeReady Builder) package repository is enabled, which includes a collection of packages not provided by default in Red Hat Enterprise Linux, such as developer applications, additional libraries and bindings, as well as packages with debugging data, documentation, header files, static builds, and code samples (packages \u2018-devel\u2019, \u2018-example\u2019, \u2018-doc\u2019, and \u2018-static\u2019). Among other packages, CRB includes libraries used as dependencies by packages from the repository. \nEPEL (Extra Packages for Enterprise Linux). <\/p>\n<\/li>\n
Packages for installing NVIDIA drivers and the CUDA stack have been created. The drivers can be used in UEFI Secure Boot configurations. Kernel modules from the official set of proprietary drivers from NVIDIA cannot be loaded in UEFI Secure Boot mode, as they are not signed with a digital signature from the distribution. This limitation has been circumvented by using open kernel modules provided by NVIDIA, based on which a custom package nvidia-open-kmod has been created with modules signed with the digital signature of AlmaLinux. A separate package almalinux-release-nvidia-driver has been prepared with the configuration of the external repository supported by NVIDIA, from which CUDA drivers and proprietary components of the NVIDIA driver operating in user space are downloaded. \nThe repository is supported.<\/p>\n<\/li>\n
Separate builds for the second version of the x86-64 microarchitecture (x86-64-v2) have been formed, running parallel to the basic x86-64 builds, which are optimized for the x86-64-v3 microarchitecture used in RHEL 10. Additional support for x86-64-v2 ensures compatibility with CPUs older than Intel Haswell and AMD Excavator, designed before 2013. Besides the standard repositories, x86-64-v2 builds have also been prepared for packages from the EPEL repository.\n<\/li>\n
Server and client implementations of the SPICE protocol have been reinstated, allowing for remote access to desktops operating in a virtual environment under QEMU\/KVM. Unlike VNC and RDP protocols, in SPICE, screen content rendering and audio stream processing are handled on the client side, not on server<\/a>. In RHEL, SPICE support was discontinued in release 9.0.\n<\/li>\n