"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.

Read more of this story at Slashdot.

- In 2022 Altair Engineering open sourced "OpenRadioss", an industry-leading finite element solver under the GNU AGPL License, reports Phoronix. - Siemens acquired Altair Engineering last year - Siemens closes access to OpenRadioss. "Siemens didn't just end the project but they shutdown the GitHub repository that hosted the open-source code and removed other resources that had built around it," writes Phoronix, before announcing a new open-source community fork: Radioss has been an industry-leading solver for analyzing crashes, blasts, and other purposes. Altair creating OpenRadioss was a huge milestone for the technical computing industry. It also had other effects like for myself in finally being able to benchmark with this (Open)Radioss code for CPU performance testing compared to the expensive licensing on Radioss itself... Siemens argues the OpenRadioss closure is for consolidating efforts: "After four years of successful community-driven research, Siemens is entering a new chapter for the Radioss solver. To accelerate innovation and provide the robust support our global users require for production-grade simulation, we are consolidating our efforts." It was Brian Clemens. founder/VP Rocky Linux and the Rocky Enterprise Software Foundation who launched the community fork of OpenRadioss — to be called OpenCourant. Its web site announces they'll be "carrying forward the OpenRadioss code base under the GNU AGPL, in the open, where it belongs." Phoronix writes in a follow-up: OpenCourant is based on the last publicly known open-source OpenRadioss snapshot before Siemens shut it down and removed access to the Git repository... OpenCourant continues with the OpenRadioss GNI AGPLv3 licensing and will be run as part of the Rocky Enterprise Software Foundation. They have run into a small issue though with part of OpenRadioss consisting of binary dependencies and not having the very latest versions prior to Siemens' removal of the repository. Details on that via this discussion thread for anyone that happens to have recent OpenRadioss binaries. In other open source news, Kagi is ending their development work on the Orion Browser for Linux and Windows, reports the site Linuxiac — but Kagi "plans to open-source both versions so other developers or organizations can keep them going."

Read more of this story at Slashdot.

Long-time Slashdot reader Andreas(R) announces Northstar, a "minimalist" web browser written entirely from scratch in C — now available in version 1.0.11: One window, one page, one process — about 160,000 lines of original C, small enough for one person to read and audit end-to-end. It carries no upstream browser engine: no Gecko, no WebKit, no Blink. It is free software under the GNU General Public License, version 3 or later, and it runs on Linux, macOS and Windows... Compliance is not inherited from an upstream engine; it is measured, section by section, against the specification text... Private by construction. No telemetry, no update pings, and no AI assistant or AI-style web APIs. Safe browsing checks a top-level navigation's host against a local SHA-256 blocklist before it is fetched — the check never leaves your machine. Cookies, storage and the cache are partitioned by origin. It's logo reminds me of the old Netscape logo. (And I love the "Best viewed in..." GIF at the upper-right of its web site.)

Read more of this story at Slashdot.

"F-Droid, a third-party app repository that only distributes free and open-source software packages for Google's Android mobile platform, on Thursday announced version 2.0 of its Android app," reports The Register. Though they also note "a big banner across the top of the F-Droid site" pointing to a site describing pending changes from Google that threaten the future of F-Droid... [D]evelopers who want their apps broadly distributed outside the official Google Play Store will need to register with Google and verify their identities. Google's Full Distribution option includes paying a one-time $25 fee, handing over a copy of a government-issued ID to verify one's identity, and conforming to Google's terms of service. Google also offers a free Limited Distribution option that doesn't require government ID verification but restricts distribution to 20 authorized devices, while apps from unverified developers can still be installed by users who enable Android's advanced installation flow. The potential death warrant hanging over its head hasn't stopped the F-Droid team from rolling out a bunch of new features for an app it says it intends to keep working on for years to come... The team also credited the EU's many Digital Markets Act decisions against Google for making the installation experience smoother for users. F-Droid can now use a unified installation service for its apps thanks to the availability of a pre-approval API that allows users to approve an installation when they request it, rather than waiting until the app has finished downloading. That, said the F-Droid team, "brings the F-Droid install experience on official Android devices much closer to what the built-in app store can provide." Additionally, F-Droid 2.0 can fetch and install app updates automatically, which it now does by default. All of those changes, however, won't matter much if Google pushes ahead undeterred with its plans to force registration onto non-Play Store developers. F-Droid's announcement on Thursday makes it seem that the team isn't going to go quietly. F-Droid has gone 10 years without a major update, notes Ars Technica — and spent over a year developing F-Droid 2.0: The new F-Droid client was redesigned from scratch in Kotlin Compose, which is the standard for modern Android apps. This makes the store much more responsive, and there's optional support for Android's Material theming. The interface has also been cleaned up considerably, making the most important functions easier to access and hiding some others in overflow menus... Unlike the Play Store, F-Droid doesn't track your taps and installs to push ads and suggestions — it helps you find things and gets out of the way. F-Droid now includes a huge number of categories, drilling down to specialized niches like firewalls, password managers, and VPNs. You can see all these groups in the search tab. There are also higher-level categories listed on the main Discover page. When searching for apps, F-Droid will now be able to return results based on app descriptions rather than just names. "One of the goals of the rewrite was to lower the barrier for new contributors," F-Droid said in their announcement. "We are excited to begin rolling out F-Droid 2.0 to users over the coming weeks after 14 test releases." (And if you want the 2.0 release right now, it's available on the versions page.)

Read more of this story at Slashdot.

Targeting students and beginners, Adafruit released "CircuitPython" in 2017 (as a derivative of the MicroPython microcontroller-optimized programming language). Now Adafruit managing director Phillip Torrone (also long-time Slashdot reader ptorrone) brings this update: Adafruit has published CircuitPython Turbo, a workflow that compiles selected Python functions into native machine code on a computer, then loads them onto compatible microcontroller boards. It builds on MicroPython's Native and Viper emitters. In a documented Metro RP2040 fixed-point Mandelbrot test, Viper cut computation time from 8.335 seconds to 0.423 seconds, a 19.71x speedup over bytecode. The rest of the application stays in Python. The guide includes benchmarks, source code and hardware demos. The speedup is for the measured computation, not the whole application. "Turbo support is now included in the latest official CircuitPython builds for RP2040 and RP2350 boards..." explains Torrone's announcement at Adafruit.com. "The new Turbo in CircuitPython helps when the board spends time calculating: making neopixel effects, drawing fractals, processing audio, filtering sensor readings, or preparing lots of pixels. Those projects can get smoother animation, quicker responses, or room to do more things at once." With Turbo, it's easier, better, and now even faster to make LED light up costumes that also reacts to sound at the same time, a sensor dashboard with animated graphics, or a tiny game doing physics while drawing the screen. Turbo speeds up the busy Python parts. It won't make a slow sensor or display connection faster... Your computer turns selected functions into instructions the chip can run directly. Python still handles the rest. We have measured speedups, real display captures, and examples you can pull apart to see what happened. None of this arrived alone. CircuitPython, MicroPython, PyMCU, compiler tools, open hardware, and people sharing their work gave us pieces to connect. The Bao experiments take that idea somewhere else, handing calculations to four helper cores. Now we get to make those paths easier to use, compare results, and find the next useful thing. Maybe that's smoother animation, a responsive instrument, or an idea we haven't tried yet. That's what I like about open source. Someone shares a piece, someone else sees a possibility, and we get to keep building it together.

Read more of this story at Slashdot.