We removed ads from OSNews. Donate to our fundraiser to ensure our future!

We all managed to survive another month, so here we are, with another monthly update from Haiku, covering the month of July. It’s been a rather short month, it being the middle of Summer and all, but there’s still some significant stuff in here. For instance, a whole slew of fixes arrived for su and other multiuser commands, mostly for the benefit of SSH sessions. A central theme in July seems to have been filesystems, as FAT16 was added to the known filesystem types in the Storage Kit, quite a few fixes were implemented for NFSv4, and a number of filesystems saw bugfixes to fix issues in rsync, and much more.

Another central theme is apparently a port of DOSEMU, for which a number of bugfixes, changes, and improvements were implemented that could, in turn, also benefit other possible ports. And of course, there’s much, much more that happened, for which you’ll have to dive into the full progress report.

We removed ads from OSNews. Donate to our fundraiser to ensure our future!

We’re not done with the AROS news quite yet, as Andrzej Subocz published another update with the latest news from the AROS community. Some of it we already covered, but a lot it we haven’t. For instance, there’s the initial version of a partitioning tool for AROS, called QuickPart. For now, it’s in read-only mode, but once it’s complete, it will allow users to do, well, partitioning. Work has also begun on porting SDL2 to AROS, replacing the aging SDL 1.2 version currently available.

On top of all that, there’s a lot of work on new and improved network drivers for the 64bit version, an extensive amount of changes and improvements to the build system, C library, datatypes, and much more. Subocz’ full report has many more details, so head on over and read up.

We removed ads from OSNews. Donate to our fundraiser to ensure our future!

The Hurd, the collection of services that run atop the GNU Mach microkernel, has been in development for a very, very long time. The Hurd is intended to serve as the kernel for the GNU Project, but with the advent of Linux and its rapid rise in popularity, it’s the Linux kernel that became the defacto kernel for the GNU Project, a combination we’re supposed to refer to as GNU/Linux. Unless you run Alpine, of course. Or you run any other modern Linux distribution, which probably contains more non-GNU code than it does GNU code, but I digress.

The Hurd is still in development, however, and one of the more common ways to use The Hurd is by installing Debian GNU/Hurd, which combines the Debian package repositories with The Hurd. Debian GNU/Hurd 2025 was released yesterday, and brings quite a few large improvements and additions.

This is a snapshot of Debian “sid” at the time of the stable Debian “Trixie” release (August 2025), so it is mostly based on the same sources. It is not an official Debian release, but it is an official Debian GNU/Hurd port release.

↫ Samuel Thibault

About 72% of the Debian archive is available for Debian GNU/Hurd, for both i386 and amd64. This indeed means 64bit support is now available, which makes use of the userland disk drivers from NetBSD. Support for USB disks and CD-ROM was added, and the console now uses xkb for keyboard layout support. Bigger-ticket items are working SMP support and a port of the Rust programming language. Of course, there’s a ton more changes, fixes, improvements, and additions as well.

You can either install Debian GNU/Hurd using the Debian installer, or download a pre-installed disk image for use with, say, qemu.

Earlier today, I made the decision to remove all advertising from OSNews. From here on out, you will no longer see any ads, cookie banners, and other ad-related privacy-invasive technologies on this website. While this means a hit to my income, making OSNews even more reliant on our Patreon supporters and Ko-Fi donors, it genuinely feels liberating. I should’ve made this decision years ago. Read on for how you can support us, and our big fundraiser.

I have always been open and honest about my dislike for the modern online advertising industry. It’s incredibly privacy-invasive, a massive security risk, generally lacking in taste, and genuinely intrusive. As such, despite running ads on OSNews, I have always advocated for the concept of “your computer, your rules”, meaning only you, the user, gets to decide what gets run on your computer and displayed on your screen. This includes the use of ad-blockers.

I have a Pi-Hole, and you can pry it from my cold, dead hands.

Because of this, maintaining ads on OSNews became untenable. Everything about the ads on our site, from the actual ads themselves to the annoying cookie banners talking about “our 1500 partners”, gave me the ick, as the young, hip people say, and I’ve been considering turning them off for a long time. Today, after yet another reader rightfully pointing out how absurd our cookie banner was, I finally made the call. One email to our owner, David Adams, later, and we’re now entirely ad-free, for everyone.

This is a hit to my income, and as such, I kindly ask anyone capable of doing so to support the continued existence of OSNews. How can you support OSNews?

• You can become an OSNews Patreon, and get some comment bling if you so desire.
• You can make individual donations through Ko-Fi. For this purpose, I’ve set an incredibly ambitious, long-term fundraiser goal of €5000.
• You can buy our merch! T-shirts, mugs, sweaters – with amazing designs and top-notch quality.

We’ve been online since 1997, meaning soon we’ll be hitting our 30-year anniversary. Very few websites can boast about such a long, uninterrupted existence, and despite all the changes both the industry and the world at large have gone through, OSNews is still here, doing what it has always done. The removal of ads means we’re even more dependent on you, dear readers, but I’m confident in saying that we’ll make it another 30 years.

Thank you for all your continued support over the decades, and let’s keep going. Without icky ads.

Almost three weeks ago, Mozilla released Firefox 141 that, among other features like memory optimizations for Linux and a built-in unit converter, brought controversial AI-enhanced tab groups.

Powered by a local AI model, these groups identify related tabs and suggest names for them. There is even a “Suggest more tabs for group” button that users can click to get recommendations.

Now, several users have taken to the Firefox subreddit to complain about high CPU usage when using the feature, as well as express their disappointment in Mozilla for adding AI to the browser.

↫ David Uzondu at NeoWin

Is anybody even asking for “AI” features in Firefox? Of the six people still left using Firefox, does even one of them want a chatbot in Firefox? Is any Firefox user the type of user to use some nebulous “AI” tool to organize their open tabs? Seeing these kinds of frivolities in Chrome or Edge or whatever makes sense, but in Firefox?

At least they’re easy to disable through about:config – just set both browser.ml.chat.enabled and browser.tabs.groups.smart.enabled to false. I mean, I guess I can understand Mozilla trying to ride the hype bubble, but at least make this nonsense opt-in, instead of asking users to dig around in obtuse config flags.

You click a link in your chat app, your browser with a hundred tabs comes to the front and opens that page. How hard can it be? Well, you probably know by now that Wayland, unlike X, doesn’t let one application force its idiot wishes on everyone else. In order for an application to bring its window to the front, it needs to make use of the XDG Activation protocol.

In essence, an application cannot take focus, it can only receive focus. In the example above, your chat app would request an XDG Activation token from the compositor. It then asks the system to open the given URL (typically launching the web browser) and sends along the token. The browser can then use this token to activate its window.

↫ Kai Uwe

After explaining exactly how this mechanism works, KDE developer Kai Uwe details the issue that not every application yet properly supports the XDG Activation protocol, and some that do have bugs that, say, might make an application discard its token too early. In other words, it’s time to start testing.

You’ll need to use the latest git master brach of KWin, and enable set the “Focus Stealing Prevention” option in Window Management to “Extreme”. When set to “Extreme”, KWin will exclusively activate windows that request activation with a valid token. They’ve already found and fixed a number of issues in KDE using this method, but more are bound to found, particularly in third-party applications.

They’re planning on turning on KWin’s focus stealing prevention on Wayland with forgiving settings at first, but increase the strictness of the feature as time progresses and issues are fixed.

It seems Microsoft is absorbing GitHub deeper into Microsoft. GitHub’s CEO Thomas Dohmke is stepping down, and GitHub will be integrated into a new department within Microsoft. Which department will become the new stewards of GitHub, and the massive pile of open source code it’s hosting?

You already know.

Still, after all this time, my startup roots have begun tugging on me and I’ve decided to leave GitHub to become a founder again. GitHub and its leadership team will continue its mission as part of Microsoft’s CoreAI organization, with more details shared soon. I’ll be staying through the end of 2025 to help guide the transition and am leaving with a deep sense of pride in everything we’ve built as a remote-first organization spread around the world.

↫ Thomas Dohmke

GitHub will become part of a new “AI” engineering group inside Microsoft, led by a former Facebook executive, Jay Parikh. As The Verge notes, this new group includes platform and development tools and Dev Div teams, “with a focus on building an AI platform and tools for both Microsoft and its customers”. In other words, Microsoft is going to streamline taking your code and sucking it up into its “AI” slop machines.

If you’re hosting code on GitHub, the best time to move it somewhere else was yesterday, but if you haven’t yet, the second best time is today. Unless you want your code to be sucked up into Microsoft and regurgitated to sloppify Windows and Office, you should be moving your code to GitHub alternatives.

Over the years, we’ve seen a good number of interfaces used for computer monitors, TVs, LCD panels and other all-things-display purposes. We’ve lived through VGA and the large variety of analog interfaces that preceded it, then DVI, HDMI, and at some point, we’ve started getting devices with DisplayPort support. So you might think it’s more of the same. However, I’d like to tell you that you probably should pay more attention to DisplayPort – it’s an interface powerful in a way that we haven’t seen before.

↫ Arya Voronova at HackADay

DisplayPort is a better user experience in every way compared to HDMI. I am so, so sad that HDMI has won out in the consumer electronics space, with all of its countless anti-user features as detailed in the linked article. I refuse to use HDMI when DisplayPort is available, so all of my computers’ displays are hooked up over DP. Whenever I did try to use HDMI, I always ran into issues with resolution, refresh rates, improper monitor detection, and go knows what else. Plug in a DP cable, and everything always just works.

Sadly, in consumer electronics, DisplayPort isn’t all that common. Game consoles, Hi-Fi audio, televisions, and so on, all push HDMI hard and often don’t offer a DisplayPort option at all. It takes me back to the early-to-late 2000s, when my entire audio setup was hooked up using optical cables, simply because I was a MiniDisc user and had accepted the gospel of optical cables. Back then, too, I refused to buy or use anything that used unwieldy analog cables. Mind you, this had nothing to do with audio quality – it was a usability thing.

If anyone is aware of home audio devices and televisions that do offer DisplayPort, feel free to jump into the comments.

Debian has released its latest version, Debian 13 “trixie”.

This release contains over 14,100 new packages for a total count of 69,830 packages, while over 8,840 packages have been removed as obsolete. 44,326 packages were updated in this release. The overall disk usage for trixie is 403,854,660 kB (403 GB), and is made up of 1,463,291,186 lines of code.

↫ Debian 13 release announcement

I’m never quite sure what to say about new Debian releases, as Debian isn’t exactly the kind of distribution to make massive, sweeping changes or introduce brand new technologies before anyone else. That being said, Debian is a massively important cornerstone of the Linux world, forming the base for many of the most popular Linux distributions.

At some point, you’re going to deal with Debian 13.

AOL routinely evaluates its products and services and has decided to discontinue Dial-up Internet. This service will no longer be available in AOL plans. As a result, on September 30, 2025 this service and the associated software, the AOL Dialer software and AOL Shield browser, which are optimized for older operating systems and dial-up internet connections, will be discontinued.

↫ AOL support document

I’ve seen a few publications writing derisively about this, surprised dial-up internet is still a thing, but I think that’s misguided and definitely a bit elitist. In a country as large as the United States, there’s bound to be quite a few very remote and isolated places where dial-up might be the best or even only option to get online. On top of that, I’m sure there are people out there who use the internet so sparingly that dial-up may suit their needs just fine.

I genuinely hope this move by AOL doesn’t cut a bunch of people off of the internet without any recourse, especially if it involves, say, isolated and lonely seniors to whom such changes may be too difficult to handle. Access to the internet is quite crucial in the modern world, and we shouldn’t be ridiculing people just because they don’t have access to super high-speed broadband.

The Linux Vendor Firmware Service (LVFS), which provides device makers and OEMs with the infrastructure to upload and distribute firmware files to Linux users, as well as support during this process, is taking bold steps to ensure large companies contribute to the project. LVFS is the infrastructure behind fwupd, the tool users actually use to download and install firmware updates.

While Richard Hughes, the maintainer of LVFS, is employed by Red Hat to work on the project, and the Linux Foundation provides the hosting costs, there’s just not enough people and resources dedicated to the project. They’re going to take measures to address this.

This year there will be a fair-use quota introduced, with different sponsorship levels having a different quota allowance. Nothing currently happens if the quota is exceeded, although there will be additional warnings asking the vendor to contribute. The “associate” (free) quota is also generous, with 50,000 monthly downloads and 50 monthly uploads. This means that almost all the 140 vendors on the LVFS should expect no changes.

Vendors providing millions of firmware files to end users (and deriving tremendous value from the LVFS…) should really either be providing a developer to help write shared code, design abstractions and review patches (like AMD does) or allocate some funding so that we can pay for resources to take action for them. So far no OEMs provide any financial help for the infrastructure itself, although two have recently offered — and we’re now in a position to “say yes” to the offers of help.

↫ Richard Hughes

In other words, functionality is going to be reduced for vendors who make extensive use of LVFS, but who don’t provide any financial or development support. I think this is an excellent incentive to get corporations who effectively freeload off a free infrastructure without providing anything in return to step up. It seems the measures are explicitly designed to target only the very few major users of LVFS, leaving the smaller companies unaffected.

Funding in open source is a major issue, and as open source becomes ever more popular and used by more and more large companies with excessive amounts of revenue, the strain on maintainers and developers is going to keep increasing. I’m entirely on board with efforts to encourage funding and contributions, as long as they fall within the confines of the terms of the open source licenses in use.

Choosing human-readable file formats is an act of technological sovereignty. It’s about maintaining control over your data, ensuring long-term accessibility, and building systems that remain comprehensible and maintainable over time. The slight overhead of human readability pays dividends in flexibility, durability, and peace of mind.

These formats also represent a philosophy: that technology should serve human understanding rather than obscure it. In choosing transparency over convenience, we build more resilient, more maintainable, and ultimately more trustworthy systems.

↫ Adële

It’s hard not to agree with this sentiment. I definitely prefer being able to just open and read things like configuration files as if they’re text files, for all the same reasons Adële lists in their article. It just makes managing your system a lot easier, since I means you won’t have to rely on the applications the files belong to to make any changes.

I think this also extends to other areas. When I’m dealing with photo or music library tools, I want them to use the file system and directories in a human-readable way. Having to load up an entire photo management application just to sort some photos seems backwards to me; why can’t I use my much leaner file manager to do this instead? I also want emails to be stored as individual files in directories matching mailboxes inside my email client, just like BeOS used to do back in the day (note that this is far from exclusive to BeOS). If I load up my file manager, and create a new directory inside the root mail directory I designated and copy a few email files into it, my email client should reflect that.

As operating systems get ever more locked down, we’re losing the human-readability of our systems, and that’s not a good development.

A simple instruction-stepped Z80 CPU emulator written in Go, inspired by the cycle-accurate emulation techniques described in floooh’s blog posts.

↫ Zen80 GitHub page

It has support for all documented Z80 instructions, supports most games and applications, and much more.

In 2022, Google launched a major push for gaming Chromebooks, including a version of Steam for ChromeOS. Steam for ChromeOS remained in Google’s nebulous “beta” state ever since, however, and today Google is doing a Google by killing Steam for ChromeOS altogether.

Entering “Steam” into the ChromeOS Launcher starts the install process like before, but there’s now an intermediary message: “The Steam for Chromebook Beta program will conclude on January 1st, 2026. After this date, games installed as part of the Beta will no longer be available to play on your device. We appreciate your participation in and contribution to learnings from the beta program, which will inform the future of Chromebook gaming.”

↫ Abner Li at 9To5Google

Chromebooks are cheap devices for students, and while there are expensive, powerful Chromebooks, I doubt they sell in any meaningful numbers to justify spending any time on maintaining Steam for ChromeOS. Of course, Steam for ChromeOS is just the Linux version of Steam, but Google did maintain a list of “compatible” games, so the company was at least doing something. The list consists of 99 games, by the way.

It’s just another example of Google seemingly having no idea what it wants to do with its operating systems, made worse in this case because Google actually had OEMs make and sell Chromebooks with gaming features. Sure, Android games still exist and can be run on ChromeOS, but I doubt that’s what the six people who bought a gaming Chromebook for actual gaming had in mind when they bought one.