OSnews

Many of us are interested in retrocomputing. There's such a rich history of eras and machines to choose from, and countless niches and nuances to get lost in. Some people make it easy for themselves and are into old computers that are readily available at low prices, like the Commodore 64 or mid-'90s Macs, while others make it a bit harder on themselves by focusing on, say, computers from the former Soviet Union or NEC machines from Japan, which are harder to find and probably require a bigger purse, too. And then there's people like me. I'm making things incredibly hard on myself, because I am obsessed with a very specific set of computers - just five machines, to be exact. Surely," I hear you think, collecting a mere five specific machines can't be that hard, no? That's how many spare Pismos I have in a box in case my primary one needs spare parts!" Sadly for me, the five computers I want to own more than any other are not particularly easy to find, and even when you do find one of them, pricing can easily reach the level of a decent used car. Regular OSNews readers will know: I am infatuated with UNIX workstations, or more specifically, UNIX workstations of the early 2000, and even more specifically, the final five models built by the last commercial UNIX vendors. So far, I've managed to get my hands on a mere two of them, but before my time on this earth come to an end, I intend to complete my Holy Quinity of UNIX Workstations. Let's go down the list, roughly ordered by attainability. HP c8000: PA-RISC/HP-UX The HP c8000 is the absolute pinnacle of HP's long-running line of workstations based on the PA-RISC architecture. The first PA-RISC workstation was launched in 1986, and HP would continue to improve the architecture and release new workstations all the way up until 2004, when the c8000 would be their last model. For the c8000, HP actually went all-out: it came with two dual-core PA-RISC processors running between 900MHz and 1.1GHz (depending on configuration), a maximum of 24GB of RAM, and a variety of graphics cards to choose from. It was a veritable swan song for the architecture. HP's commercial UNIX operating system, HP-UX, is even older than PA-RISC, with the first version being released in 1982, and its final version, HP-UX 11i v3 (or 11.31) released in 2007. This final version of HP-UX was updated and supported all the way up until 31 December 2025, but things are actually a bit more complicated than that. The last workstation release of HP-UX for PA-RISC was 11i v1 (released in 2000), while the last workstation release for Itanium workstations was 11i v2 (released in 2005). Do note that HP would provide updates, fixes, and patches to these versions long after the mentioned release dates. Speaking of Itanium, HP's final Itanium workstation was the zx6000, released in 2002, which can pack up to two single-core 1.5Ghz Itanium 2 processors. There's a very real case to be made that the zx6000 should also be part of this list, since it's both a little faster than the c8000 (in its dual 1.5GHz configuration) and runs a newer version of HP-UX. However, since Itanium workstations never really had much of an impact in the market (even HP only ever released two models), and since it lacks the decades of pedigree that comes with PA-RISC, I consider them a mere curiosity. A very cool curiosity that I'd love to own, but a curiosity nonetheless. Anyway, this is one of the two machines I already own. I have a new-in-box (when I bought it a few years ago) HP c8000 with two dual-core 1.0Ghz PA-RISC processors, 8 GB of RAM, and an ATI FireGL X3 AGP graphics card with 256MB, the fastest the c8000 will take. It's also got two SCSCI 74 GB hard drives in a striped RAID for better performance, and I added an LTO 4 tape drive so I could create bootable backups that will restore the machine if anything ever goes wrong. It's running HP-UX 11i v1, with as many of the updates, patches, and fixes I could find - which is one of the major roadblocks for anyone trying to get into HP-UX. Installation media are relatively easy to come by if you know where to look (assuming you know which specific version you need), but any updates, patches, and fixes from roughly later than 2005 are almost impossible to find. Some can be discovered through My HPE Software Center, if you have the patience of an angel and the perseverance of a honey badger (it's a really terrible website), but most things are all locked away behind expensive support contracts or just gone entirely. I've contacted HPE several times in several different ways about the preservation of HP-UX, but they never replied - clearly, they just don't care about the preservation of their legendary UNIX platform or the enthusiast community buying PA-RISC hardware on eBay for personal use and experimentation. Sad, but par for the course. The c8000 is quite easy to find on eBay, but do be aware that the cheap" offerings of around 800 are the versions with just one processor. To get the version with two processors, expect to shell out twice as much. Spare parts and upgrades are readily available, too. Sun Ultra 45: SPARC/Solaris The Sun Ultra 45 needs no introduction here on OSNews, as I published an in-depth article about this machine and all the cool things you can do with it late last year. My Ultra 45 was an incredibly generous gift by Adriaan de Groot, who owned this machine as part of his work on porting KDE to Solaris way back in the day. I then ordered various upgrades to the machine to max it out with two UltraSPARC IIIi processors running at 1.6GHz, 8 GB of RAM, and the Sun XVR-2500 with 256MB, the fastest

Amos B. Batto has published an incredibly detailed look at the state of Linux on smartphones. It's an excellent read you really shouldn't skip. Five years ago, Linux phones looked like they were poised to become a viable alternative to the Android/iOS duopoly that has an iron grip on the mobile phone industry. Sadly, after a brief flash of activity and community engagement with the release of the Purism Librem 5 and the PINE64 PinePhone in 2020, the Linux phone market has generally stagnated. This stagnation occurred partly because of the problems at Purism and PINE64, but also because the available Linux SoC's weren't up to the task of running a modern smartphone, and the hardware industry wasn't providing any good alternatives with good free/open source drivers. In addition, Plasma Mobile and Phosh were still inchoate mobile interfaces at the time, and there wasn't a good distro option to run these interfaces on Android kernels with a normal integrated mobile SoC. The poor performance of the PinePhone and Librem 5 and the problems with the PinePhone Pro and the Librem 5 refunds sapped people's enthusiasm and willingness to take a chance on the next Linux phone. Fortunately, all of these conditions are changing, and I believe that there is now the possibility that Linux could finally become a viable alternative to Google's Android and Apple's iOS in the mobile space, just like desktop Linux has become a viable alternative to Windows and Mac OSX on the PC over the last three decades. This isn't to say that mobile Linux will fundamentally challenge the business of Google or Apple, but the conditions are ripe for a small market to arise for Linux phones, similar to the way that people can currently buy Linux PCs from a number of small companies, such as TUXEDO, System76, Purism, Slimbook, ThinkPenguin, Ubuntushop.biz, Entroware, Star Labs, Juno, Laptop with Linux, Linux Certified, ArkPC, etc. Amos B. Batto I'm not quite as optimistic as Batto, and that's almost exclusively down to how running Android applications through compatibility layers will remain an absolute necessity for anyone trying to use one of these Linux smartphones today. As long as crucial applications and services required to function in a modern society, like banking, messaging, government services, and so on, require the use of an Android application when using a Linux smartphone, I just don't think any significant number of people will be switching over. What's needed is something that will force these crucial services to become available on platforms other than Android and iOS, since I don't think any of them will do so of their own volition. The only way I can see this happening is if the European Union, spurred on by our desire to reduce our dependence on adversarial US companies, mandates that several services marked as crucial must make themselves available on platforms other than Android and iOS. I doubt that will happen, but I honestly don't see Linux smartphones becoming anything more than a mere curiosity you fiddle with at home, while carrying an Android phone or iPhone as your actual phone.

LineageOS has released its first version based on Android 17 - earlier than expected. We've been hard at work rebasing all of our changes and features since Android 17's release in June. Android 17's first release mainly contained iterative improvements and some UI/UX refinements, but due to our previous efforts adapting to Google's heavy refactoring over the last several versions, we were able to rebase onto Android 17's code-base faster than anticipated. Yes you read that right: We're early this year! LineageOS' changelog written by Nolen Johnson This release also includes the latest Android security patches (October 2026), as well as a brand new browser-based USB flash tool to make installation easier. Many of the applications included with LineageOS have also been updated and improved, like its music player, image editor, web browser, and so on. The project also did a full accessibility audit of its installation process and application suite, which has already resulted in severalk accessibility improvements. LineageOS serves as the base for countless custom Android ROMs, so it's great to see the project do this well.

Over the years, I learned about many gotchas and strange differences between keyboard handling on Mac and Windows - pertinent especially to web apps, which use the same codebase to cater to both. I thought it might be helpful to someone if I compile them all in one place. Marcin Wichary I knew most of these, but it's still nice to have such a reference at hand when needed.

In this article. I am going to explain the different steps the I/O manager follows when initializing an I/O operation starting from determining the right target, choosing the right path and finally sending the request to be processed by the right drivers. To make it easier I choose to focus on read requests only since the major steps are common by all types of requests. Win-Ware A very in-depth look at Windows' I/O Manager.

At OSNews, we love us a hobby operating system project. I started a small experiment: writing a very basic kernel in Swift, and running on QEMU. The goal is obviously not to replace Linux or any other popular kernel, but just to have fun and understand what is required to make a program run without an operating system underneath it. Actually I made a similar experiment years before with arOS 10 years ago. For the moment, the kernel does only one thing: it prints a message through QEMU and then waits forever, which is enough for a first deep dive. Carette Antonin This is effectively a hello world" kernel, as it doesn't actually do much else at this point. Still, there's a ton of details in the article for the aspiring kernel developers among you.

Whenever Microsoft starts messing with something like the search function in Windows, a lot of people are going to be holding their breath and expecting the worst. Well, get ready, because they're redesigning the whole thing. In July, we shared how we are improving the Windows Search Box with less clutter and more control. We introduced a calmer home screen, removed promotional content from web results, and gave you more choice over whether web and Microsoft Store suggestions appear. Today, we're carrying those investments forward with a new Windows Search experience built on WinUI 3. This modern foundation makes Windows Search faster and more efficient with resources, while delivering an even more streamlined and focused design. Anshul Rawat at the Windows Blogs The company claims this new version of search is faster and uses less memory, which, if true, are very welcome improvements. It's also just a single column of results now, and they're adding inline previews for things like weather and files on your machine, as well as for answers to all kinds of queries you might normally go to an online search engine for. You can now also use search to perform all kinds of tasks in Windows, like turning on dark mode, managing windows, and so on. All of this can be done using relatively natural language, and Microsoft claims they've implemented better detection of typing errors and synonyms, which is quite welcome. Weirdly enough, though, it's not yet integrated into the Start menu, since it's a preview just for testers, but that's something they're working on for future releases. Judging by the videos and screenshots, I'm actually kind of positively surprised. This looks quite decent and nice, and if the promised performance improvements actually materialise, this may actually be an upgrade to search worth looking forward to. Of course, this is still Microsoft, so it's just as likely they'll screw up somewhere between now and when this goes live to regular users. Still, I think it looks decent.

Chimera Linux is a relatively new Linux distribution, and quite a unique on at that, as it combines the core tools from FreeBSD, the LLVM toolchain, and the Musl C library instead of the usual suspects. Despite being relatively new, it still has some serious pedigree as the project was started by Nina q66", who was part of the Void Linux team. At Void, she maintained the various PowerPC/POWER ports of the distribution until Chimera became her sole focus. Nina published a detailed blog post today about how the Chimera team builds the tooling for their distribution, as well as the goals it's trying to achieve. It covers everything from a bit of personal history, the rationale behind the project, who it's catering to, how its tooling works and why, and the infrastructure they've built that underpins it all. There's a lot to process here, with one of the most interesting little details - at least to me, as someone who has two POWER9 machines - the fact that Chimera started with the ppc64le target only. The article is an incredibly interesting look at not just the how of Chimera, but also the why, which makes for some really fascinating reading.

KDE contributor and developer Niccolo Venerandi has published an article about COSMIC, System76's brand new desktop environment. It's been almost a year since I've last tried COSMIC; though development since then has mostly been centered around stability (going from late alpha to stable releases now!) there have been a fair bit of user-facing changes too which I adore. I thus have to ask myself: should I switch to COSMIC? The answer obviously is no, but that's just because I got addicted to KDE Plasma, so let's try to be more objective here. Niccolo Venerandi Honestly, this is one of the best reviews" I've seen of COSMIC, and paints System76's hard work in a really positive light. Venerandi spots countless really nice touches he'd love to see adopted by KDE, while also hitting on what I agree is COSMIC's biggest shortcoming at this point: there's basically no ecosystem around it. COSMIC uses its own Rust-based toolkit instead of GTK or Qt, but of course, there's very few other applications that actually use said toolkit. The end result is that if you run COSMIC, you're going to have to supplement it with countless GTK and Qt application, none of which will inherit all the nice features, touches, and graphics from COSMIC. This isn't really a complaint about COSMIC itself or the work its developers are putting into it, but more a fact of life for such a new desktop environment using an otherwise unpopular (as of right now) toolkit. This may very well change in the future, but for now, if you choose to run COSMIC, you're going to have to accept a very inconsistent and messy desktop. This won't matter to everyone, but it sure does matter to me, and it's the one reason why at this point I have zero interest in running COSMIC. I really hope this changes in the future - competition is good - but it's going to be a long road.

Speaking of Windows and performance, how about that RAM crisis? Microsoft is feeling the squeeze too, and is apparently doing work up and down the Windows stack to improve its memory consumption. Microsoft's Windows chief Pavan Davuluri has admitted that the rising cost of memory is pushing the company to make Windows 11 use less RAM. Microsoft is working on the Windows memory manager, memory compression, WinUI 3 and WebView2, and has made memory optimization for 8GB and above" an official priority for the rest of 2026. Abhijith M B at Windows Latest This might be the only positive consequence of the RAM crisis.

To this day, Windows retains full support for the old MS-DOS 8.3 filename limitation, and it does this by creating 8.3 aliases for files with longer names. Apparently, this has a measurable effect on performance, so naturally, people are going to turn it off to make their Windows installations perform better. According to the user, this resulted in noticeably smoother scrolling in Tile view. They subsequently repeated the process on several folders they regularly use and reported that searching through files became much faster. The user also claimed that external hard drives became faster and that browsing an Android directory over USB or FTP behaved more like a regular Windows folder, including when copying large numbers of music files. Sayan Sen at Neowin You can disable this legacy feature in Windows per volume or globally, but Microsoft is warning users not to do so. Even in 2026, applications and registry entries may depend on 8.3 filenames being available, so removing them can lead to unexpected outcomes. It's just one of those things you wouldn't expect to still be around or have a measurable impact in the days of fast SSDs, but there's enough credibly evidence out there to suggest that yes, it actually does negatively affect performance. If you're doing a lot of file operations in Windows, it might be worthwhile to do some testing of your own to see if you can speed things up. Or, you know, you can just not use a house of cards disguised as a serious operating system.

Apple's macOS has a Full Disk Access permission, designed to allow backup applications full access to, well, the disk, so they can perform their job properly. Apple posted a notice on its website that it's going to further restrict this permission, because some applications were abusing this permission to gain access to users' messages, emails, and so on, which it obviously isn't intended for. What kind of applications, you may ask? Going forward, we will introduce additional controls to ensure that users who genuinely wish to grant an app this extraordinary level of access can only do so with very explicit user action. Addressing this is critical. As AI agents become increasingly capable and autonomous, the risks associated with this level of access will grow substantially. We are committed to ensuring users clearly understand these risks before granting such access, so they can make informed decisions about their own data and privacy. Announcement from Apple This was prompted by a story a few weeks ago, where Facebook's Muse AI" tool was apparently reading people's private messages and other data, and even sent messages on users' behalf, without informing its users. It's incredibly naive to think Facebook software in 2026 would not do creepy things, so I'm honestly not at all surprised. It makes sense in Apple's worldview to further restrict permissions in response, but I'm sure more experienced macOS users are not going to like this.

The KDE project recently brought back its classic Oxygen and Air themes, but what if you prefer something... A little older? A modern recreation of the classic KDE 3 desktop experience for KDE Plasma 6, built entirely using Qt 6 and Qt Quick, with full support for Wayland and fractional scaling. Klassik GitHub page Neat.

I like squirrels. Apparently, there's a SquirrelOS. It's a small hobby OS learning project from five years ago, developed by Immanuel Daviel A. Garcia. A simple DOS like OS made in Assembly and C with a ported version of Stephen Brennan's Shell. SquirrelOS GitHub page Why do I like squirrels? I don't know man, they're just cute.

Google launched its Googlebooks platform a week ago, and a lot of people were wondering what this meant for Chrome OS and Chromebooks. Since Googlebooks and its Android-based Googlebook OS lack the management frameworks markets like schools require, Chromebooks will continue to be available for now, until such time Googlebooks catch up in that regard. However, in a support document, Google states that update support for all Chromebook devices will end in 2034: ChromeOS devices will continue to receive regular updates and security patches through mid-2034. For qualifying devices purchased today whose 10-year support lifecycle extends beyond 2034, Google is committed to supporting your transition to Googlebook OS, with many devices offering direct migration paths. Google support document Google promised 10 years of updates for all Chromebooks, and it's now breaking that promise for anyone buying a Chromebook between now and whenever the last Chromebook rolls off the production line. Sadly, we live in a world where corporations are free to make and break whatever promises they want virtually free of consequences, and as society we're so used to it that anti-consumer behaviour like this barely elicits a shrug. Google does state that many newer commercial Chromebook models will be capable of upgrading to Googlebook OS", but that, too, is just another promise - and a vague, one at that - so who knows how many devices will actually be capable of upgrading out in the real world. On top of that, we have no idea if Googlebooks will just be yet another in a long line of quickly abandoned Google tablet/laptop projects, further adding to the uncertainty. Stuff like this should not be legal.

In June 2008 Apple announced Mac OS X Snow Leopard, proudly boasting that it would have no new features". Instead of piling on new things, Snow Leopard aimed to build on the success of its predecessor, Leopard, opting to focus on under-the-hood performance and stability improvements throughout the system. 18 years later, Apple is taking a similar approach with macOS 27. Golden Gate aims to fix the missteps of last year's Tahoe, promising an expansive set of improvements and a more responsive and delightful experience". Does it hold up? Here are just some of the bugs I've encountered in my daily use over the past couple of weeks. Chester at SquareOrbits I'm getting some real Windows 11 vibes from this long list of bugs and issues, further underlining my perception that Apple completely lost the plot when it comes to Mac OS X (in the past) and MacOS (today). These are not the kind of things you'd find in the heydays of Mac OS X, back when I was a devout user, and makes me glad I abandoned ship long, long ago (around the time of the Intel transition). I don't see stuff like this in GNOME or KDE, and while not nearly as bad as Windows 11, the cracks are obvious. I am by no means an expert at how Apple is run and how it organises itself, but as a layperson I do wonder if the company is simply trying to do too much - too many different platforms, too many different crucial components it all develops internally, too many different markets to please. Things are going to fall through the cracks when you try to keep this many plates spinning.

A brand new Tcl/Tk release, in the form of Tcl/Tk 9.1. The new features in Tcl are a bit difficult for me to properly parse as a non-developer, but Tk's improvements are easy to understand: it brings supports for screen readers, initial supports for bidirectional and RTL scripts, improved listbox selection colours, and more. It also happens to drop support for Windows XP appearances, if that's something that matters to you.

Microsoft has announcedWSL containers for developers who aren't already using Docker, Podman, or Rancher on their Windows workstations. WSL containers is now generally available! Check out this blog post to learn more about this overall feature enabling seamless access to Linux containers on Windows via the new wslc.exe" command. This new Linux container platform comes with multiple architectures changes compared to WSL, which we'll detail in this post. Pierre Boulay at the Microsoft Dev Blogs If you already have WSL installed, you can run wsl -update to get this new container feature, or you can download it straight from GitHub.

Over the last few days and weeks or so, a few of the people I follow and interact with on Fedi have been talking about centralising information, tools, applications, and expertise from the Motif (and Xt, Xlib, and X11) ecosystem. There's a ton of information, resources, and actively maintained applications out there, but it's all spread out and sometimes difficult to find, and so Thomas Adam - one of the core developers of FVWM, among other things, as well as creator of CoW (FVWM for Wayland, more or less) - has created an effort to centralise all of this. Motif Central brings together information about Motif, Xt, Xlib and X11: how they fit together, how to program with them, and where to find the manuals, examples and historical material that explain them. Begin with the X programming stack, build your first Motif application, or explore the programming resources. The history pages describe the libraries' origins, while the archive guide helps you navigate older documentation. MotifCentral There's been a whole flurry of activity around Motif lately, including the updated and maintained fork we talked about a few weeks ago. The people loosely collaborating on MotifCentral also submitted patches to CDE to make sure it works on the new Motif fork, with the CDE developers setting up a build pipeline for easier testing. Making sure CDE, the classic Motif desktop environment, works well with the maintained Motif fork quite a few people seem to be rallying around is a worthwhile effort. We're still quite far from a complete(-ish) modern Motif ecosystem, but it's very heartwarming to see just how many people are actually still interested in it. My perhaps misguided hope is that we can somehow get to a modernised Motif/CDE desktop environment and applications, making it possible to more easily run a modern Motif environment on Linux and the BSDs. One may dream.

Windows 11 received its September update on the 8th of this month, and within days Microsoft had acknowledged or investigated problems involving Remote Desktop, USB audio, Linux and WSL-based apps like Claude Cowork, and enterprise domain issues. Windows Latest also found File History failures, Explorer.exe crashes, and AMD GPU instability, with an emergency update following on September 14 that still did not fix everything. This got us curious, and we looked back across the nine monthly updates released from January through September 2026 and, rather unsurprisingly, Windows 10 update history isn't infected with nearly as many bugs as that of Windows 11. Abhijith M B at Windows Latest Of course, Windows 10 also isn't getting nearly as much attention from Microsoft, but that's kind of the whole point, isn't it? Whenever Microsoft touches something, especially over the last 5 years or so, it's one cascade of failures after the other, eroding trust in Windows' updates even more (if that's even possible). In that light, why would you want to use Windows 11 and all the headaches that come with it, when Windows 10 is right there, still being supported, albeit without the latest bells and whistles that only seem to break Windows 11 anyway? If you really do need or want to use Windows, consider switching back to Windows 10 whenever the usual Windows reinstallation time draws near. You won't lose much, but will gain quite a bit in the process. Of course, this won't be a responsible or usable choice forever, but at this point in time, I definitely think it's the optimal choice for quite a few people.

One of the unwritten rules of the Internet seems to be that whenever something Amiga-related is mentioned, at least one Amiga fan (myself included) must show up and try to explain the concept of screens. Amiga screens can have different resolutions, we'll tell you, and one can drag them, we'll say, and other Amiga users rally in agreement, while non-Amiga users probably still don't get what's so great about screens. Until now, when this text has been written, in the hope of converting unsuspecting normies into full-blown Amiga screen lovers. Carl Svensson A deeply technical look at not just how the Amiga managed to achieve this stunning functionality way back in the '80s on machines with 7MHz and less RAM than a keyfob, but also how this functionality can be useful. I've always found the concept of screens on the Amiga quite interesting, and Svensson's article does a great job at demystifying the whole concept. Of course, expect a lot of lovely Amiga OS screenshots.

It's time for an overview of another month of Redox OS progress, and over the month of August - they're a bit late, don't believe the publication date - they've implemented multicore support for ARM, and considerably improved the I/O performance for the NVMe driver, RedoxFS, and RAMFS by implementing a ring buffer communication API. There's also initial support for NUMA-based memory management, QEMU is now working on Redox, and much more. Of course, there's also the usual long list of improvements to the kernel, relibc, drivers, and more.

Can you run an operating system with a graphical user interface and applications on the Atari Jaguar? Well, you can. A long time running idea and work-in-progress, I'd like to finally announce the current version of JagOS Spot' for the Atari Jaguar, running from the RetroHQ GameDrive. I'm slow at releasing things and try not to announce in-progress stuff due to lack of free time but would like to push this along. Maybe it'll motivate me to work on it more if the interest is there or just release it as-is if not. The idea is based on the unreleased Atari Jaguar Painter Computer prototype, that a merged Falcon with Jaguar chipset-based computer would have found its way into consumer hands after the Falcon030. Clint Thompson The screenshots and YouTube video are quite impressive, but as it's not actually released, it's difficult to really say anything more about this project for now. I hope there's enough interest to get this project's code out there so it can be further improved and expanded.

Qualcomm, yesterday, promising Linux support for the new Snapdragon X2 processors: Linux on Snapdragon X2 Series is moving from early bring-up toward a more complete upstream developer experience. Core support is landing, Hexagon NPU and Adreno GPU work is progressing, and real laptops with Snapdragon X2 Series processors are already beginning to boot Linux. Qualcomm's promises from 2026 Interesting, but I feel like I've heard these exact words before. Qualcomm, two years ago, promising Linux support for the then-new Snapdragon X processors: It's been our priority not only to support Linux on our premium-tier SoCs, but to support it pronto. In fact, within one or two days of publicly announcing each generation of Snapdragon 8, we've posted the initial patchset for Linux kernel support. Snapdragon X Elite was no exception: we announced on October 23 of last year and posted the patchset the next day. That was the result of a lot of pre-announcement work to get everything up and running on Linux and Debian. Qualcomm's empty promises from 2024 These promises were not at all kept. Two years later, Linux support for Snapdragon X laptops is still spotty, broken, and limited, confined to just a few bespoke Ubuntu builds, which don't even offer full support either. It's a complete mess, effectively unusable, and highlights once again that big technology companies are compulsive liars. I have little faith in these new promises, but who knows - maybe this time it'll be different. Probably not, though.

Raymond Chen, longtime Microsoft employee and author of the very popular The Old New Thing blog, published an interesting post about the Win32 scrollbar. It turns out there's actually quite a few interesting shortcuts and useful hidden features, like clicking inside a scrollbar while holding down shift will make the content jump to that point. Halfway through the article, though, Chen laments how nobody really uses proper Win32 scrollbars anymore. Sadly, almost nobody uses Win32 scroll bars any more. Everybody uses frameworks that provide their own custom scroll bars. Raymond Chen And as you might expect, none of these scrollbars work like the Win32 one, making even something as basic as the scrollbar a fragmented mess. He doesn't just blame things like Electron, either, as Microsoft's own WinUI framework, which is used for most new" Windows UI developed by Microsoft for Windows 11, also uses custom scrollbars that do not work like the Win32 one does. Great, so by the time I learn about a shortcut for scroll bars (Shift+click), the ecosystem has fragmented so much that I can't even rely on it working. Raymond Chen Modern computing is depressing.

The Solaris branch for paying customers has been updated to SRU95. Oracle Solaris 11.4 SRU95 updates a broad set of platform, runtime, developer, networking, desktop, and open source components. Notable updates include Ansible Core to 2.21.1, Apache HTTP Server to 2.4.67, Apache Tomcat to 9.0.120, BIND to 9.20.23, Django to 5.2.15, Elixir to 1.20.1, Erlang to 28.5.0.2, Firefox to 140.10.0esr, Go to 1.25.11, ImageMagick to 7.1.2-27, MySQL 8.4 to 8.4.10, NSS to 3.125, OpenSSH to 10.4p1, Rust to 1.96.0, SQLite to 3.53.2, Thunderbird to 140.10.0esr, and Vim to 9.2.0513. Additional updates include CMake, CUPS, Cython, GnuTLS, libarchive, libexpat, pip, rsync, and a range of Python modules, X11 libraries, graphics libraries, printing components, and desktop utilities. Colin Kavanagh at the Oracle Solaris Blog One of the major changes is the deprecation and removal of NTLM authentication of local users; only NTLMv2 is supported now for security reasons. This release also brings GCC 16, with GCC 13 being removed in the next version. The detailed release notes go into some of the more low-level, esoteric changes in Solaris 11.4 SRU 95.

It is impossible to go anywhere in a technology space online without hitting a wave of commentary about how stupid GDPR is. It was written by bureaucrats who don't understand the amazing potential of unrestricted technology. These US-based critiques almost always lean on the oldest trick in cyberlibertarianism: we don't have time to regulate, we must simply adapt and ride the wave. Nobody has time for government. Of all GDPR's consequences, none gets more attention than the cookie banner, which critics present as the inevitable result of government meddling. Blaming GDPR for the cookie banner is like blaming the health inspector for the roaches. The banner is deliberate vandalism, a dark pattern engineered to exhaust you before you can learn anything about the surveillance apparatus humming behind the OK." Ironically the banner designed to hide the machine has taught the public more about the machine than a thousand podcasts ever will. Even non-technical people stop at your data is shared with 996 partners." Mat Duggan There is so much misinformation about the cookie banner, it's honestly quite hard to believe it's not deliberately spread. You don't need a cookie banner for functional cookies, so as long as you don't share your users' data with anyone else, you don't need a cookie banner at all. On top of that, most cookie banners you encounter are actually not compliant with the GDPR at all, because they don't present a single-click option to block your data from being shared with those 996 partners. What the cookie banner has done is inform millions - maybe even billions - of people the world over of just how insipid the online advertising and data harvesting industry really is. It put the issue on the map, and by now, everyone, no matter their level of computer literacy, is fully aware of what's happening to their data every time they see one of these (non-compliant) banners. No else had the guts to do this - except for the European Union. The wider GPDR has set the baseline for online privacy protections, and while we have a long way to go before we've fully solved this issue, the EU at least gave us a good point to jump off from. Smoking and asbestos weren't banned in a day, either.

A few months ago, Google announced it was going to put Android on laptops (and eventually, desktops), serving as eventual replacements for Chromebooks. Unlike those, though, these new Android laptops wouldn't be low-quality, cheap, underpowered devices for school children to spill milk on, but devices actually competitive with Windows and macOS laptops. Today, the company finally allowed the press to use these new things. Google describes Googlebook as a totally fresh approach to computing," bringing together Android, ChromeOS, Gemini, and premium laptop hardware from major manufacturers. The idea is to create a laptop that feels more natural to use for Android phone users while retaining what makes a desktop OS useful, such as a full Chrome browser, desktop apps, a proper file manager, Linux support, and a full terminal environment. Google is also trying to solve some of the biggest problems Android users have had when moving between their phone and laptop, and make the two devices feel like part of the same ecosystem. Adamya Sharma at Android Authority I've been looking at some of the videos of people using and playing with these new Android laptops, and to be honest, I'm not impressed. I'm seeing quite a bit of jank, a complete lack of consistency, and apparently, a lack of Android applications optimised for desktop use. The close integration with your Android phone are nice, but of course, this also means another dollop of slimy lock-in, as I highly doubt Google will make it easy or even possible at all for, say, iPhones or other platforms to integrate quite as nicely as Android devices will. Worse yet, there's the elephant in the room: for just how long will Google care about this new platform? These laptops start at $900 and go all the way up to $1300 (and will be considerably more expensive here in Europe), which is a lot to ask for something Google might get bored of and abandon in a few years' time. Ten or more years ago, in a slightly more innocent time, I might've been excited about Google bringing Android to laptops and desktops, but in 2026, I just can't be bothered to care. Also, and this doesn't really matter, but Googlebook OS"?

The GIMP will never magically become software beloved by artists-not without radically changing its culture, and making the artists the ones who call the shots. The GIMP will remain what it has always set out to be: a tinkerer's toolbox, more concerned with the purity of its software politics than with garnering a loyal userbase of photographers and designers. But because everyone insisted to poise it as a viable Photoshop killer, Linux is left with an obvious hole in its software offering, a hole nobody managed to fill with their own challenger. Aria Salvatrice Excellent article, and spot-on conclusion.

Passkeys are a fantastic technology. Since they are bound to the site they are created for, they cannot be phished by a hacker's fake login screen. If a site suffers a data breach, passkeys are asymmetric and cannot be recovered from the server-side details. This leads to passkeys being the perfect fit for a corporate environment, but a poor fit for personal security. To an individual, the greatest risks are instead permanent account lockout, automated account bans, and device loss. By using passkeys, you gain better security against man-in-the-middle attacks but face the higher probability scenario of losing access to your accounts. Phishing through the standard login flow is eliminated by passkeys, but it creates a false sense of security. An account's security is still dictated by the weakest recovery method: SMS, email links, security questions, and so on. If these recovery methods aren't enabled, then the risk of permanent lockout remains for the user. Ethan Hawksley I've always felt something was off about passkeys, and have never used them. They've become - or were always intended to be - tools for further lock-in by especially Google and Apple, tying their entire usage flow to their respective operating systems. They also don't seem to work well if you often work on devices not your own, which is a major hassle. None of these shortcomings come into play when using a traditional password manager, even if they require more manual work. Just let me use a password manager with random password generation, instead of trying to force passkeys down my throat.

Speaking of unsexy programming, we've got a new Java release. Featuring thousands of performance, stability, security, and productivity improvements, Java 27 (Oracle JDK 27) provides a strong foundation for continued Java innovation. To help organizations prepare for more secure communications in a post-quantum world, Java 27 advances its post-quantum cryptography (PQC) capabilities with hybrid key exchange for TLS 1.3. Oracle press release The OpenJDK release page has more information.

Look, nobody's going to argue .NET is sexy, but the truth of the matter is that it's quite popular in less visible circles, so any new release is going to have a big impact on a ton of people and product. In other words, performance improvements in .NET 11 are going to matter. In contrast, .NET 11 is actually one higher, one louder. The sections that follow are full of real improvements. A bounds check removed, an allocation that no longer happens, a lock that isn't taken, a loop that runs in fewer cycles than it did a year ago, a comparison folded to a constant here, a redundant check hoisted out of a loop there, a couple of instructions fused into one, a syscall sidestepped, an array copy handed off to SIMD, and on and on. That's how real performance work goes, accumulating gain after gain, each compounding on the last, until the whole thing is measurably, provably louder. And so, in this post, as I've done in past years with .NET 10, .NET 9, .NET 8, .NET 7, .NET 6, .NET 5, .NET Core 3.0, .NET Core 2.1, and .NET Core 2.0 before it, we'll take an unhurried tour through hundreds of them. Stephen Toub at Microsoft's Dev Blogs My eyes glaze over at all of this, but even here on OSNews, there's going to be countless people working with .NET at their jobs.

GNOME 51 has been released, with a whole slew of new features and improvements. Most notably, at least in my experience, will be the work done on GNOME's graphics stack, which seems to stutter and jitter more than KDE's on the same hardware - at least in my experience. In particular, GNOME's compositor, Mutter, has improved frame scheduling for smoother animations, even under load. This hopefully addresses the stutters I generally experience when using GNOME. They've also done a lot of work on the Settings, Maps, Calendar, Web, and other applications. Of note to many will be the array of improvements to GNOME's file manager, including better performance, although I doubt it will convince those of us who aren't particular fans of Nautilus in general. They've also improved the remote desktop experience by, among other things, adding support for smart cards and improving support for Kerberos. GNOME 51 will make its way to your distribution of choice soon enough.

Ubuntu has been replacing core utilities with Rust rewrites, and it's now completed the process. cp,mvandrmwere held back ontheir GNU versions inUbuntu 26.04 LTS due to a crop ofTOCTOU (time-of-check to time-of-use) issues that needed to be fixed in theuutilsversions. With those issues resolved upstream,Ubuntu 26.10 finishes the job. The Stonking Stingray' ships a full set of Rust core utilities, which encompasses common command-line tools like ls,cat,chmod and du. Joey Sneddon at OMG! Ubuntu I'm definitely not qualified enough to make any useful remarks about this, but the idea of replacing such foundational, battle-tested utilities with brand new ones, even when written in a memory-safe language, does make feel a little hesitant. Still, at least this way Ubuntu users can work out any issues so that if and when other distributions - like the one I use, Fedora - follows suit.

When I used Windows for a month because you people paid me to do so, the utter lack of consistency in the way applications and the operating system itself looks, feels, and behaves was a major sticking point. It turns out, though, that I was only scratching the surface of just how bad things really are on Windows. Case in point: the new WinUI Notepad application that replaced the classic Win32 one. I had no idea just how bad it really is. It's been seven weeks since I last complained about something in Windows on this blog. That feels like too long, so here's a post about menus - specifically, the menu bar in the modern version of Notepad in Windows 11. That menu bar has, unfortunately, quite a few regressions compared to the menu bar in the old Win32 version of Notepad. Reupen Shah I'm not going to spoil any of it, because there's no way you'd believe any of it without the videos Shah provides. I'm aghast.

The Good Enough File System, originally developed for 9front, is being ported to OpenBSD. For those who haven't watched my talk, GEFS is a new, crash-safe, snapshotting, copy on write FS that I wrote for 9front, and which I am in the process of moving to OpenBSD. The file system is described in full here. Ori Bernstein One of OpenBSD's shortcomings is its rather archaic filesystem, so any work on something more modern and especially more performant is quite welcome. While any process of replacing FFS is going to be a long one, even having GEFS as an option could be a great addition to OpenBSD.

Apple releases its yearly cluster of operating system updates today, with the two most prominent of course being macOS and iOS/iPadOS. These new versions focus heavily on Apple's AI" stuff, but there are a few actual improvements and changes to the actual operating systems as well. Across both iOS and macOS, users now have a slider to affect how transparent or opaque the Liquid Glass" design is across the operating system. And on the macOS side especially, Apple has made numerous small design tweaks to address user feedback, which has been accumulating since Liquid Glass was introduced. There's nothing radically new in terms of design here, but this is a much-needed polish pass. Across all the releases, but in particular macOS and also iOS, there are a bunch of quality-of-life or performance improvements. For example, macOS now supports HDR for all system UI elements and gets more robust support for a wider range of display modes for external monitors. Samuel Axon at Ars Technica If you're not into AI", there's not a lot of meat on these bones, but at least you can turn the AI" nonsense off through a switch buried deep in the settings applications of Apple's operating systems (which will probably be flicked back on whenever the next update comes).

Want to run something a little more exotic on your server? How about GNU Guix? It has been a month since migrating my home server to GNU Guix. Managing OS state declaratively through Git has eliminated configuration drift, and Guile Scheme provides a cohesive environment that complements Emacs. While adapting to a smaller package ecosystem and managing substitute timing requires occasional adjustments, the stability, reproducibility, and container isolation make it a dependable foundation. Wai Hon I'm definitely noticing an increase in interest in Guix lately.

Late 2000. There is a grey and blue tower PC on my dorm-room desk like nothing anybody who walks into the room has ever seen. The Be logo on the front, a 3.5'' floppy peeking out the bottom of the drive bays, and the vertical grille that hides two columns of green LEDs (blinkenlights) dancing with the CPU load. This was a dual-PowerPC workstation running an operating system you didn't see in the wild. I was studying computer science at the time and this was a fun piece of hardware. J.D. Hodges As a BeOS user in and around 2001 or so, the BeBox was the holy grail of the little community I was a part of. There were some people here and there in online circles who had one, but they were rare even when new, and by 2001, they had become rarer still. This rarity made them mysterious and exciting from almost from the day they were launched, like a small volume halo car few people will ever get to see, let alone experience, first-hand. It's 2026 now, and more and more of the small number of BeBoxen made must be succumbing to degradation and hardware failures. I hope everyone who has one takes good care of them, because these are some of the rarest, most coveted computers of all time. I've still never seen one, and here in Arctic Europe I most likely never will. Still, I remain hopeful. One day.

On the Windows side of the age verification question, Microsoft is obviously following trends among lawmakers the world over. To address this, Windows is introducing a new platform capability: the Windows Age API. This API brings age awareness beyond the operating system by making it available across the entire Windows ecosystem so that apps and services can deliver age-appropriate experiences using the same trusted foundation. By making age awareness available as a platform capability, Windows helps developers build safeguards into experiences from the start rather than placing the burden on children and families to manage protections app by app. Rob Mauceri at the Windows Blogs Meanwhile, on the Linux side of things, there's been some cheering as at least California passed amendments to its age verification law to exempt open source operating systems. These amendments redefine the term operating system provider" to exclude any person or entity that distributes an OS or application under license terms that permit a recipient to copy, redistribute, and modify the software." Any software distributed under the GPL, MIT, BSD, and Apache licenses satisfies that test, which removes the likes of Debian, Fedora, Ubuntu, Arch, and the BSD family from AB 1856's scope. Luke James at Tom's Hardware I think this is not at all the good news that many make it out to be. Exempting Linux, BSD, and other open source operating systems from age verification obligations may seem like a good thing at first glance, but in reality, I think services and applications will simply choose to not work at all on platforms that do not implement age verification. The fear of legal ramifications, especially when it involves children, will be enough for existing and future popular services and applications to exclusively work on platforms that implement age verification - whether those fears are founded or not. In fact, I'm fairly sure a company like Microsoft, which has actually been feeling the squeeze from the Linux side recently - even if it is modestly so - is quite happy to see open source operating systems excluded from these obligations. Google, too, is probably none too unhappy to see any possible open source mobile operating system competitors not implement age verification. The fear of missing out is real, and most people are not as invested in fighting big tech and government surveillance as the average OSNews reader is going to be. If using Linux means not being able to play the latest hit games or use that new successful service, people will choose to stick with Windows or macOS. Let me be very clear that I do not support these age verification laws in any way, shape, or form, and I definitely do not want the open source world to embrace age verification. What I'm worried about is that the open source world will cheer on these exceptions and consider the battle won, when in reality, they feel more like Pyrrhic victories. Age verification laws must be fought and destroyed at ballot boxes the world over, because otherwise I fear they will become just another tool in big tech's toolbox, exemptions or not.

Do tech companies ever stop to think about the misery they unleash on people's lives? The Apple Watch Series 12 uses Audio Intelligence" that, as well as secretly taking notes, also has a Live Rewind feature that can replay the last 15 seconds of recently detected audio and view a text transcript. Matt Growcoot at PetaPixel Another win for us Europeans: this dystopian nightmare will not be available in the EU.

Although Solaris is now mostly defunct, its influence remains substantial; technologies pioneered by Solaris can still be found across a wide range of software A lot of Solaris' inventions have been described and talked about ad nauseam (such as the Slab Allocator), but one I rarely see discussed is its use of turnstiles. Despite being relatively obscure, the idea has quietly spread far beyond Solaris. Variations of it can now be found in major operating systems, web browsers, and language runtimes. In fact, you're probably using several implementations of the same basic concept right now! Loic Gregoire I'm not going to pretend to understand all of this, but I know you people do, and many of you will definitely find this interesting to read. Also note that Gregoire develops their own operating system kernel called zag.

Lotus Notes was the future of communications, a decade before laptops had WiFi. Yet of all things, it wasn't even an email app. It was a notes app, a collaboration tool, an all-things-to-all-people software that let you build apps in the way Access and Airtable later would. That, and the notes could be used for email. Love it or hate it (and there were plenty on both sides of the fence), what you couldn't do was ignore it. This email-and-everything-else platform showed what the future of digital communications would become - and provoked, as email itself was always doomed to provoke, equal measures of awe and exasperation. Matthew Guay I have no experience with Lotus Notes, but I do have some vague memories of the software being used at my parents' employers back in the late '90s. Note that Notes still exists and is in active development as HCL Domino (server) and Notes (the client). If you really want to, you can still run your company of office on Notes. I wonder how many actually still do.

The BSD news will continue until morale improves. I missed this two months ago, but Baptiste Daroussin, creator of pkg and poudriere, is working on a service manager for FreeBSD called rcd. rcd(8) is a service manager daemon called by init(8) (in place of /etc/rc). It reads service definitions from UCL unit files (/etc/rcd.d/*.ucl), builds a dependency DAG, and starts services in parallel. After boot completes, it forks to background and stays running as a supervision daemon (automatically restarting failed services and accepting control commands via a UNIX socket). Baptiste Daroussin It's fully backwards compatible, and works on any existing FreeBSD system without having to make any modifications to rc.d scripts or configuration files. In fact, you can install it on a running system, make zero changes to your files, and reboot to use it, which is quite impressive. The most immediate benefit is, of course, faster boot times, but you'll also get several other benefits already found on similar systems like Solaris' smf. There's a migration path in place, with a hard promise to maintain compatibility with rc.d scripts for as long as needed. This gives maintainers as much time as they need to convert to rcds own unit files.

Yesterday we had the final maintenance release for the NetBSD 9.x series, and today we have FreeBSD 14.5 entering the scene. Since this release is occurring late in a legacy stable branch, there are few new features; rather, the focus is primarily on maintenance. As such, changes since 14.4-RELEASE consist mostly of bug fixes, driver updates, and new versions of externally-maintained software. FreeBSD 14.5 release announcement The adventurous among us are already on the 15.x branch, but those of us running mission-critical systems are most likely still rocking 14.x, and for you, this is a must.

With ever-changing devices, browsers, operating systems, form factors, specifications, personal preferences, tooling, and corporate interests, the web is in a constant state of flux. As a result, so is the HTML we write. For every line of the HTML specification itself that has changed since the language's inception, there are many more bits of HTML that have seen what I'll call environmental' changes. Adaptations to differing browsers, extensions, integrations, and systems which we find HTML existing in. This article doesn't cover once-specced but now obsolete bits of HTML but instead looks at all the snippets that have wormed their way into websites as result of, or in combat against, third-party integrations, browser competition, vendor extensions, and platform-specific hacks. The bits of HTML that were included for reasons, and which have been forgotten for present irrelevance. The snippets that live on only in the markup of sites from bygone eras and in the minds of those who fought during the browser wars. Declan Chidlow I don't do any HTML or website development, and even I clearly recognise quite a few of these. Especially the countless relics of the large technology companies trying to worm their way into the various web standards of decades ago serve as a stark reminder of how many times they tried and failed - which should tell you something about all the times they tried and succeeded.

Speaking of NetBSD, the fifth and final 9x release has been released. It represents a selected subset of fixes deemed important for security or stability reasons since the release of NetBSD 9.4 in April 2024. It is fully compatible with NetBSD 9.0. This also marks the end-of-support for all NetBSD-9.x releases and the netbsd-9 branch. All users still on this branch are urgently asked to update to a more recent release like NetBSD 11.0 (with 11.1 upcoming at the end of this month) or NetBSD 10.2 (to be released in a few days). Martin Husemann at the NetBSD blog The full release notes have more information.

Why use an installer to install an operating system, when you can just do it yourself, step by step? In this post I will cover the installation process of the NetBSD operating system, including disk level encryption. Instead of using the standard installation program (sysinst), I decided to install NetBSD from scratch", as a way to dive into the internals, and learn more about the nuts and bolts of this great operating system. Luis Falcon A fun weekend project for next weekend.

Zenith is a variant of Windows for developer-class devices". Project Zenith comes with a set of pre-installed tools spanning languages and runtimes, source control, and productivity tools. Windows Terminal and Visual Studio Code are pinned to the Taskbar by default, putting your favorite tools within immediate reach. We've also pre-configured Windows Settings for coding across File Explorer, Search, Start, and the Taskbar. File Explorer shows file extensions, hidden files, the full path in the title bar, and the details pane, with long-path support enabled. Recently used files and folders and sync provider tips are turned off for a cleaner workspace. In Search and Start, Command Palette is enabled, while Start menu tips and account notifications are turned off to reduce distractions. Windows Subsystem for Linux (WSL) has become foundational for running Linux workloads on Windows. Last year we open-sourced WSL. Building on that momentum at Build 2026, we integrated WSL more deeply into Windows with WSL containers to provide a built-in way to create, run, and interact with Linux containers directly on Windows. Logan Iyer at the Windows Blogs It's highly unlikely you'll be using this Zenith Windows flavour any time soon, as it requires 64GB of unified RAM with 250 GB/s memory bandwidth. In 2026, that's a serious ask. On top of that, it's not entirely clear to me if Zenith will be available as a separate Windows variant, without having to buy a complete device. Of course, it would be trivial to set all of this up on any fresh Windows installation.

We are pleased to announce the release of ReactOS 0.4.16! After a year and a half of development, we're excited to showcase the improvements we've made between a new graphical installer; a unified bootcd and livecd image; video, audio, networking, and storage stack improvements; a new installation type; and third-party code syncs. The ReactOS Team on the ReactOS website The amount of changes and improvements is quite staggering, honestly. They'll always be chasing a moving target, sure, but if they manage to keep this rate up ReactOS might actually grow into something usable in its own right, full compatibility with Windows or not. Excellent progress.