AlmaLinux Shows Advantages of ABI Compatibility After RHEL Restricted Source Code Access
4 14"AlmaLinux OS charted a new path in 2023 when Red Hat restricted source code access to Red Hat Enterprise Linux," remembers Linux Magazine. "Rather than pursue 1:1 compatibility with RHEL like other Enterprise Linux alternatives, the AlmaLinux OS Foundation chose application binary interface (ABI) compatibility, which guarantees that applications and kernel modules that work on RHEL will work on AlmaLinux OS." No longer constrained by the 1:1 promise, AlmaLinux can offer new features, or add back deprecated ones, while still remaining a stable, drop-in replacement for RHEL... The release of AlmaLinux OS 10.2 in May 2026 reveals just how far AlmaLinux has come....
When RHEL 10 increased the x86-64-v2 architecture baseline to x86-64-v3, many older server platforms (and some new ones) were left in the lurch. These older servers couldn't support the modern CPU feature sets in x86-64-v3, including AVX2 CPU instructions. AlmaLinux recognized that many community members employed older hardware that relied on x86-64-v2. While x86-64-v3 is enabled by default in AlmaLinux OS 10 and AlmaLinux OS Kitten 10, an additional x86-64-v2 build is also available. The x86-64-v2 build works best for environments that rely on standard OS packages or that can rebuild any additional packages required by x86-64-v2. For users with older hardware, the additional x86-64-v2 build allows continued use of current hardware, saving money and keeping servers from the landfill. AlmaLinux OS 10 is actively supported through 2030 with security support through 2035, significantly extending the life of older hardware....
Many legacy applications and containerized workloads still run on i686, a 32-bit computer processor architecture belonging to the Intel x86 family, including software that only ships as i686, CI pipelines that require a specific 32-bit glibc, and seemingly normal looking containers that require a 32-bit environment. RHEL 10 completely removed 32-bit application support and multilib libraries after deprecating support in earlier releases... AlmaLinux OS 10.2 has added package repos and official container images for 32-bit x86 (but not a 32-bit kernel or installer)...
NVIDIA GPUs, ubiquitous in modern computing, have been a pain point for Linux users. Getting the closed-source NVIDIA drivers has required extra steps and manual installation. When NVIDIA released an open source version of their graphics driver, AlmaLinux integrated the drivers, along with the associated CUDA components, into the AlmaLinux repository starting with AlmaLinux OS 9 and 10. AlmaLinux also signs the open source drivers, allowing secure boot with the NVIDIA drivers they ship. Unlike RHEL users, AlmaLinux users now have native support, allowing them to skip manual installation. AlmaLinux users can now enjoy a fully integrated NVIDIA experience.
In addition, "Thanks to ABI compatibility, AlmaLinux can sometimes deliver patches more quickly than RHEL," the article points out. And it lists other points where AlmaLinux OS 10.2 diverges from RHEL 10:
- Re-enabling frame pointers disabled by default in RHEL and CentOS Stream to provide system-wide, real-time tracing and profiling to diagnose and optimize code.
- Enabling both kernel and userspace components that allow installation of AlmaLinux on a Btrfs filesystem
- Adding SPICE support dropped in RHEL 9, allowing users to interact with a virtual machine's desktop remotely instead of just from the host server.
- Restoring support for older storage and network drivers disabled upstream, including Adaptec, Dell PERC, HP, Mellanox, QLogic, Emulex, LSI, and Broadcom.
4 comments
Check it out (Score: 5, Informative)
by markdavis ( 642305 ) on Saturday November 07, 2026 @12:14PM (#66414349)
I am glad I moved my servers to AlmaLinux. It has been working out really well over the last few years. They were also fast to offer mitigation information and updated packages for each of the high-profile vulnerabilities this year.
If you are worried about what level your processor supports just run this:
$ /lib64/ld-linux-x86-64.so.2 --help | grep -A4 'glibc-hwcaps directories'
Look for the word "supported" on each level. Mine shows this on my large Xeon 6254 (Alma) servers:
x86-64-v4 (supported, searched)
x86-64-v3 (supported, searched)
x86-64-v2 (supported, searched)
At home on my AMD Ryzen 7 3700X desktop (Mint) I get:
x86-64-v4
x86-64-v3 (supported, searched)
x86-64-v2 (supported, searched)
So I have v3 support, but not v4. Hopefully that will be good enough for a long time coming...
Re:Check it out (Score: 5, Informative)
by 93 Escort Wagon ( 326346 ) on Saturday November 07, 2026 @01:56PM (#66414433)
We switched our servers and workstations to AlmaLinux after IBM pulled the rug out from under us with 8. I've been very happy with both the product itself and with the people behind it.
Re:Wait a second... (Score: 5, Insightful)
by thecombatwombat ( 571826 ) on Saturday November 07, 2026 @12:47PM (#66414377)
It is, but basically only in the barest most minimally technically legal sense.
Only paying customers have access, and of course they can choose who gets to be a paying customer. Once you get access though, it still is open source, you can still publish derivative works and all. This is technically still GPL compliant and has at least held up for three years now.
In real short, the goal was to cut off Oracle, but they went pretty scorched-earth about it.
Re:Wait a second... (Score: 5, Informative)
by caseih ( 160668 ) on Saturday November 07, 2026 @01:58PM (#66414435)
This was discussed extensively over the last few years.
Disclaimer: lengthy mansplaning post follows for the one or two slashdotters interested but who haven't followed this long-running controversy.
Until a few years ago, RH had a public git repository of their rpm spec files, and probably also their patch sets (can't quite remember). Fairly abruptly they shut down that public repository saying that the repo and folks using it to build RHEL clones didn't provide anything of value to the community (really passive aggressive). This caught a lot of people by surprise and it really was a poke in the eye of the community.
But going back even further, Red Hat's support contracts have always caused heartburn for free software supporters, particularly with regards to the GPL. A RH support contract grants access to SRPM files for the entire distro to their customers, along with of course the actual RPMS. But the wording of the support contract says you cannot use those files on non-supported installations. Meaning they don't want you to pay for one server and then use the downloaded files to update your whole cluster, even though the source code license, particularly in the case of the GPL, explicitly grants such permission. Many free software advocates have complained that although RH abides by the GPL technically, they are using contract law to end run around it.
So far as I know, no actual customers of RH have ever been threatened with contract cancellations over this, and to this day Rocky Linux and Oracle both use these RH-downloaded SRPMs to build their distros. I'm not sure to what extend RH actively pursues the accounts used to download by Rocky and Oracle.
RH's defense is that the upstream CentOS Stream system is public and free to use by the community to build on. This is what Alma Linux does and it works very well while maintaining compatibility with RHEL. The only downside is it's harder convert an existing install between RHEL and AlmaLinux. Back in the old CentOS days it was easy. I'd bring up a server on CentOS, test it in beta for a few months/year, then before bringing it into production I'd finally roll it over into a supported RHEL instance.