{"id":120937,"date":"2024-12-11T21:46:08","date_gmt":"2024-12-11T19:46:08","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/beta-vypusk-distributiva-almalinux-10-0-sinhronizirovannogo-s-rhel-10"},"modified":"2024-12-11T21:46:08","modified_gmt":"2024-12-11T19:46:08","slug":"beta-vypusk-distributiva-almalinux-10-0-sinhronizirovannogo-s-rhel-10","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/beta-vypusk-distributiva-almalinux-10-0-sinhronizirovannogo-s-rhel-10","title":{"rendered":"Beta release of the AlmaLinux 10.0 distribution, synchronized with RHEL 10.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
The AlmaLinux project has announced the testing of the beta version of the AlmaLinux 10.0 distribution, which is synchronized with the new branch of Red Hat Enterprise Linux 10 and includes all proposed changes. The distribution is, as much as possible, binary-compatible with Red Hat Enterprise Linux and can be used as a replacement for RHEL 10 and CentOS 10 Stream. Installation images have been prepared for x86_64, x86_64_v2, ARM64 (aarch64), IBM PowerPC (ppc64le), and IBM Z (s390x) architectures. <\/p>\n
You can familiarize yourself with the new features of AlmaLinux 10 in the overview of changes proposed in RHEL 10-beta. The functionality of AlmaLinux 10 mirrors that of RHEL 10, except for the rebranding and the following differences: <\/p>\n
\n
Separate builds have been created for the second version of the x86-64 microarchitecture (x86-64-v2), which are provided alongside the basic x86-64 builds that are optimized for the x86-64-v3 microarchitecture used in RHEL 10. The additional support for x86-64-v2 ensures compatibility with CPUs older than Intel Haswell and AMD Excavator, designed before 2013.\n
The use of the %rbp processor register has been reinstated as the base pointer for the stack frame, containing return addresses and function variables (frame pointer). Using the frame pointer allows for the use of additional capabilities for system tracing and profiling in the distribution. <\/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. <\/li>\n