fidzu : Operating Systems

The KDE team released KDE Plasma 6.7 today, and with it comes a long list of improvements, new features, bug fixes, new old themes, and so much more. A new feature that is sure to please those among us who use virtual desktops: you can now have different virtual desktop setups per display. It's been a long-requested feature, so it's great to see it makes its way to the KDE users. I despise virtual desktops, but I'm happy to see something that I assumed was already part of KDE to finally actually become available. Another major feature in KDE Plasma 6.7 is something we've already talked about: the return of the classic Oxygen and Air themes from the KDE 4.x days. These themes have seen extensive work over the past year or so to make them usable on the latest KDE release, which includes tons of bug fixes, visual nips and tucks, and countless additions to the collection of assets required to make a modern KDE theme look complete. This includes a ton of new icons in the old styles, light and dark modes, accent colour support, and much more. There's still work left here, including adding support for QtQuick/Kirigami applications - which brings us to the next major new addition to KDE 6.7 This is also something we've already talked about: Union. I won't repeat what I already explained last time Union came up, but suffice it to say that Union effectively unifies the various different ways KDE applications are themed, allowing theme designers to use relatively standard CSS to create themes that cover every aspect of the KDE user experience. Before Union, theme designers had to create individual, unique themes for a variety of parts of KDE - the Plasma desktop, QtWidgets using QStyle, QtQuick/Kirigami - which was a ton of work, and in the case of QtQuick/Kirigami, wasn't really possible at all. As such, without Union, KDE's theming is essentially broken, and Union fixes that. For now, Union is not enabled by default, and must be installed and enabled separately for testing. Of course, there's a ton of other smaller new features, changes, and bug fixes as well. KDE Plasma 6.7 will find its way to your distribution soon enough.

16 Jun 2026 8:20pm GMT

A week or so ago, Apple announced a bunch of features for the App Store on iOS, including personalised recommendations based on your activity and usage of iOS. It turns out this includes a keylogger (taplogger?) in the App Store, which records every single tap you make, every single letter you enter, and a lot of other information. All of this information is unencrypted and sent to Apple. Now Apple is putting the extensive identifiable analytics they collect in the App Store in action. They record every tap and there's no way to turn it off. They can even calculate your typing speed. ↫ Michael Tsai, quoting Mysk The provided screenshots of the data collected are terrifying, especially because the data is unencrypted, sent to Apple, and fully tied to your user account. Apple clearly wants a slice of that big, juicy advertising pie, and they, too, are discovering that the easiest and best way to serve targeted ads is to collect as much data as they can about you. Of course, this is something the entire internet (but not OSNews!) and several megacorporations are built on by now, but Apple has been incredibly sanctimonious about how it supposedly actually cares about user privacy, making this keylogger yet another case of Apple's hypocrisy on full display. Of course, if you care about privacy, you're entirely free to download your iOS applications from somewhere other than the App Store and install them yours… Oh, wait.

16 Jun 2026 6:41pm GMT

Another story from the good old days from Raymond Chen. During an exchange of war stories, a colleague of mine told one from back in the days when Windows included a processor emulator for x86-32 on systems that natively ran some other processor. (This has happened many times. And no, I don't know which processor this particular story applied to.) ↫ Raymond Chen at The Old New Thing So the core of the story comes down to this: All in all, it took this program 256 kilobytes of code to initialize 64 kilobytes of data. ↫ Raymond Chen at The Old New Thing The people working on Windows were so offended by this, they added code to the processor emulator just to fix this program.

16 Jun 2026 1:53pm GMT

Speaking of FreeBSD, the project released version 15.1 of their operating system today. As it's a point release, it's not full of massive changes, but it still brings the LinuxKPI-based wireless drivers up to Linux 7.0, support for the C23 version of the C has progressed considerably, Unicode has bene updated to version 17.0.0 and CLDR 48, and more.

16 Jun 2026 1:43pm GMT

Expect to see more and more articles like this one, as more and more people discover that FreeBSD's desktop/laptop support keeps improving rapidly. FreeBSD 15 really feels like a breakthrough release. It's always been my favorite operating system for servers, but with the arrival of pkgbase, massive improvements to the LinuxKPI drivers, and the launch of the Laptop Support and Usability Project, it's become my primary desktop, too. ↫ Cullum Smith Since Smith tried FreeBSD 14.0, there's now KDE Plasma 6.x, you can leave legacy X11 behind and use Wayland on FreeBSD now, and support for Intel Wi-Fi chips has greatly expanded. Apparently, battery life has improved as well, which is one of the hardest problems to solve for an operating system, especially with the wide variety of hardware combinations in the x86 world. The rest of Smith's article is a guide to setting up FreeBSD 15 with KDE and Wayland. It's quite detailed with a ton of low-level tuning and fiddling, accompanied by clear and concise explanation of what the changes do, which I really like. Definitely a bookmark for anyone who wants to try out FreeBSD with KDE.

16 Jun 2026 1:24pm GMT

It's been a while since we've had a new operating system project written in Rust, so let's look at Zinnia. The kernel is written in (almost) 100% Rust and attempts to avoid unsafe code where possible. It implements a big range of POSIX APIs in system calls, but also exposes common extensions found in Linux and BSDs, like epoll and timerfd. This allows it to run a somewhat modern desktop using Wayland and X11 sessions. Most drivers are implemented as modules. These are Rust ELF dylibs which get loaded and linked during boot from an initrd, similar to Linux systems. Zinnia can boot from any UEFI based system thanks to the Limine bootloader. ↫ Zinnia OS website At least Weston and Xfce can run on Zinnia, even on real hardware, which is quite an achievement. The project was started in 2024 as a learning endeavour, but quickly grew out of control, as these projects are wont to do. The code's open source.

15 Jun 2026 7:28pm GMT

We're a little deep into June already, but it's only now that Haiku published its monthly progress report for May. There's a bunch of fixes for drag-and-drop behaviour in Tracker, AVX512 support can now be enabled thanks to changes to the kernel's FPU handling, some low-level changes were made for the Rust and Zig compilers, and further improvements were made to the boot process on the Raspberry Pi 5 (although a lot more work is needed on that front). There's still no sixth beta since a few more blockers remain, but don't let that stop you from installing Haiku - it's stable enough as it is, sixth beta or no.

15 Jun 2026 7:21pm GMT

Tribblix, the Illumos distribution focused on giving you a classic UNIX-style experience, has been updated with the release of Milestone 40. This version has some major component updates. Perl in now 5.42 instead of 5.34, and the default Python is now 3.13. The GCC suite is now version 14.2.0, go is version 1.26, Xfce has been updated to version 4.18, node is v22, with v24 added and v20 removed. ↫ Tribblix M40 release notes There's a more detailed changelog, as well as the downloads page to get started. If you're already running Tribblix, you can update in-place, of course.

15 Jun 2026 7:10pm GMT

An infuriating story about something most of us don't really stop to think about: e-books and the rendering engines companies and software use to display them. It's the year 2026. Thanks to the horrendous RMSDK which Kobo decided to use as their backbone for all book rendering (probably for DRM reasons), a single line of perfectly valid CSS turns a perfectly valid EPUB file into a "corrupted file" on Kobo and just drops the whole book. No clear error message, no fallback. Just a massive fail. ↫ André Klein The level of obnoxiousness goes even deeper: Kobo devices ship with a better, actually maintained renderer for e-books as well, but in order to have a book use it, the book file in question needs to have a specific file extension. Remember that e-book files are just packaged websites; there's no reason to do any of this nonsense with two rendering engines, one of which is shit and frozen in time. I have never had to do anything related to creating an e-book - I just put books on my own Kobo and read them - and even I am getting annoyed just reading this.

15 Jun 2026 2:01pm GMT

How far can you get, application development-wise, by using only the original APIs from Windows 1.0, and only whatever came included by default with Windows 1.0? I finally decided to write an application for the very first version of Windows and see how different the modern WinAPI really is from its earliest versions. Windows 1.0 came out back in the mid-1980s - the era of 16-bit processors, MS-DOS, and cooperative multitasking. At first glance, you might think it has almost nothing in common with modern Windows, but when you look specifically at the application API, that's where things get interesting. I wanted to see how far it would be possible to go using only the capabilities of the first version of Windows. I didn't want to just make a minimal example with a window and a menu, but a small, complete application with graphics, keyboard input, timers, and constant redrawing. For this experiment, I chose Xonix - a simple yet surprisingly addictive game. ↫ Stanislav Safronov It turns out that surprisingly, despite the 40 years and massive changes since Windows 1.0, there's still a lot that feels recognisable. It's also remarkable that the code Safronov ended up with ran on every version of Windows from 1.0 to 10, but sine it's a 16 bit application it no longer works on Windows 11. It also had a hiccup on Windows 95, but he suspects that's an issue in the 16 bit subsystem in Windows 95, and not in his code. The code's available on GitHub.

15 Jun 2026 1:00pm GMT

In 1994 I got my first computer: an Intel i486 DX2-66 with 4 MB RAM and a 512MB harddisk. The software was IBMs OS/2 and Microsofts Windows 3.11. In the next four years I was upgrading this machine every few months with more RAM (up to 16MB), a CD-ROM-drive and a soundblaster card. So I learned upgrading this machine, installing new software and finally learned how to program new software using BASIC. But I never got in touch with the boot-process or the details of MS-DOS. In 2026, 32 years later, I learned from some screenshots of the DDX3216, that Behringer used a real 386 processor within this machine. Immediately, some of my neurons fired in my head and I pondered if I could boot software and even a full operating system on this device. My goal was to learn how an x86-system is booting, how DOS takes over and what is necessary to get into the shell. ↫ Christian Nöding So this introduction is a bit cryptic if you're not aware of what a DDX3216 is - I sure had no idea. The Behringer DDX3216 is a digital mixing console for use in music studios, and I think it's about 25 years old or so. Apparently it's built around a 386, and as Nöding details in this article, that means it can be made to run DOS. It also happens to have a small black and white LCD, so there's a place to route output to, as well. Furthermore, once you open it up, you'll find things like a BIOS chip, PCMCIA slot, a floppy controller, serial/parallel port controller, and more. Sure sounds like a PC to me. After talking to companies and individuals who might have a BIOS compatible with the AMD 386 SoC used in the device bore no fruit, Nöding decided to develop his own BIOS, which involves getting all the devices, interfaces, and even the display to work properly as well. The next step was getting DOS to work, and after MS-DOS 6.22 refused to work, FreeDOS did the trick and booted just fine. There's still a ton more possible things that can be done here, but this is already quite amazing.

14 Jun 2026 9:36pm GMT

TrueType is a widely used vector font standard for rendering text in web pages, PDFs, operating systems, and applications. Familiar fonts like Helvetica, Garamond, and Monaco are all built on TrueType outlines. The format specifies a hinting interpreter intended to help outlines rasterize faithfully on low-resolution displays. Modern high-resolution displays enable beautiful typography from outlines alone, but TrueType fonts that need hinting to render legibly remain in use and we continue to support them. Font parsers process data from untrusted sources, making the TrueType hinting interpreter a security-critical attack surface. To make the format more resilient on Apple platforms, we rewrote its hinting interpreter from C to memory-safe Swift for the Fall 2025 releases. In addition to memory safety, we also improved performance: on average, our Swift interpreter runs 13% faster than the C interpreter it replaced. ↫ Scott Perry This article provides a deep dive into how, exactly they did that.

14 Jun 2026 11:34am GMT

If you want to try out a modern Amiga operating system, your choices are severely constrained. Both MorphOS and AmigaOS 4 need PowerPC hardware, and at the moment, there's little to no modern hardware available for purchase to run these operating systems on. The only AmigaOS 4 hardware you can buy is either incredibly outdated, incredibly expensive, or both, and while MorphOS does run on readily available Apple PowerPC machines, those, too, are getting quite long in the tooth and performance simply isn't keeping up. Until the Mirari becomes available - with the project steadily progressing, I have high hopes - the reality for people wanting to try out AmigaOS or MorphOS is going to be expensive, at best. Or is it? QEMU exists, and QEMU can emulate various PowerPC systems just fine. Shouldn't it be possible to run these two unique operating systems in a virtual environment on your modern PC, thereby making it trivial for those of us interested in the world of Amiga to dip our toes into the water without having to spend inordinate sums for outdated hardware? It turns out that yes, this is entirely possible, and as I highlighted almost a year ago, George Sokianos has made this process effectively foolproof by developing a custom GUI frontend for QEMU specifically designed to make it incredibly easy to set up and run AmigaOS 4 and MorphOS in QEMU virtual machines. We're almost a year since that first version, and in that time, Sokianos has updated the tool, called Kyvos, to version 2. It costs a mere €9, and works on Linux (x86 and ARM), Windows (x86 and ARM) and macOS (x86 and ARM). You also get an incredibly detailed manual with step-by-step instructions for every supported operating system and specific emulated machine, which includes instructions for the convoluted AmigaOS 4 installation process, as well as a bunch of other information and helpful tips. In addition, the manual includes links to where you can buy AmigaOS 4 - be sure to use these specific links to buy AmigaOS 4, because Sokianos gets a commission for sales through these links. AmigaOS 4 costs like €30, so it's not a big investment. MorphOS can be downloaded for free, but after 30 minutes of use, the operating system will slow down and cripple itself, unless you pay for and register your copy for €79. I own a copy for my 17″ PowerBook G4 1.25Ghz, but I think copies are tied to hardware, so I haven't tried registering it with my key yet. The MorphOS registration tool does not accept virtual machines, so you can't use it to buy a copy for a virtual machine. Kyvos' graphical user interface mimics the UI of other virtual machine software like VirtualBox, and it will check to make sure you have all the correct dependencies and requirements installed. The guided setup processes for MorphOS and AmigaOS 4 virtual machines will tell you exactly which operating system ISOs and files you need and makes sure you have them, before setting up the QEMU virtual machines with the optimal settings. Once created, start the virtual machine, and they'll boot from the installation media. Follow the included manual as you install the operating systems, including some post-install help, and you'll end up with fully working, network-capable virtual machines running MorphOS and AmigaOS 4. Both installation and setup procedures worked without any issues on my machine, and within like half an our I had to two fully working copies of MorphOS and AmigaOS 4 running on my Linux desktop gaming PC (I exempted myself from the Windows 11 incentive for this one, since my Linux gaming PC is by far the most powerful computer I own). Networking and sound works - AmigaOS 4 requires some post-install steps for those, listed in the Kyvos manual - and I could browse the web right away with the included web browsers. The online update tool for AmigaOS 4 also works perfectly, allowing me to upgrade to the latest version of the operating system and various included components. I'm anything but a MorphOS or AmigaOS 4 expert, so I can't confidently say much about performance compared to best real compatible hardware out there, but at least for MorphOS I can say it runs considerably faster in this virtual machine than it does on my old 17″ PowerBook G4 1.25Ghz. I feel like AmigaOS 4 runs a bit smoother than MorphOS does, as with the latter I experienced the occasional hiccup and stutter which were absent on AmigaOS 4. Still, both are entirely usable and a pleasure to use. With how limited the hardware selection for these two operating systems is, using QEMU through Kyvos is by far the easiest and most straightforward way to dip your toes into the waters of the modern Amiga operating systems. For a total of around €40, you'll be running AmigaOS 4 in a very capable and straightforward way, and if and when MorphOS allows registration for virtual machines (they really should), an additional €79 will give you a fully working installation of that unique operating system, too. Kyvos is a complete no-brainer for anyone reading OSNews.

12 Jun 2026 2:26pm GMT

Video game consoles have a long history with web browsers. From the advent of the World Wide Web, consoles have been trying to get online. Browsers on video game consoles were initially very much an attempt to provide a cheap gateway to the web for a casual audience lacking technical expertise, though as time progressed they've become a greater and more integrated part of systems. This article takes a look at browsers on video game consoles in detail, though only covers official web browsers. Many consoles have browsers installable via custom firmware and homebrew, but they're beyond the scope of this post, as are non-web systems such as Satellaview and online services that didn't provide a browser, such as XBAND, Sega Meganet, and Sega Channel. ↫ Declan Chidlow The article starts off with the Philips CD-I, which has always been a fascinating product for technology fans in The Netherlands because that's where Philips is from. Memory that far back is untrustworthy, but I can definitely remember being inundated with commercials, advertising, magazine articles, and newspaper reports about the CD-I, all throughout its rather troubled life. Yet, I don't remember anything about it being capable of browsing a rudimentary web. Of course, we're talking 1995 here, a time when I didn't even have internet at home yet, although I did use the web at a friend's place at that time. We didn't get internet at home until I think 1997 or 1998, followed by the move to broadband cable internet just a year later, since our small rural town happened to be one of the first places to get broadband. Good times. Did anyone ever actually use browsers on consoles, though? I mean, using them always felt incredibly clunky, and by the time they were capable enough to really do anything we all had laptops and later smartphones anyway. I certainly don't remember anyone using them for anything but a gimmick, but perhaps my sample size was far too small and not diverse enough.

11 Jun 2026 5:38pm GMT

With the announcement of an upcoming new macOS release also come the usual changes in which Macs will still be supported. MacOS 27 Golden Gate is an important release in this regard, as it will be the first release of Apple's desktop operating system that will be entirely ARM-only, dropping support for all Intel Macs. It's important to note that Apple will provide three more years of security updates for the final Intel release of macOS, so Intel users won't be dropped like a brick immediately. Still, the Intel Mac Pro was still being sold all the way up until mid-2023, and I'd be royally pissed off if my expensive 2023 Intel Mac went out of support a mere six years after purchase. They weren't cheap machines, and while you can argue everybody knew the writing was on the wall for the Intel Mac Pro in 2023, it still feels way too short of a supported lifespan for such an expensive, high-end piece of equipment. It didn't sell many units, I'm sure, but still. In addition, MacOS 27 will be the last release to include the Rosetta 2 translation layer that allows Intel binaries to run on ARM macOS. I have no idea how many important applications are still Intel-only, but I have a feeling that number is going to be relatively small, and will become even smaller as the first macOS release without Rosetta 2 support nears release. On top op of that, I'm sure enterprising users will find a way to transplant Rosetta 2 onto unsupported macOS releases, and if all else fails, there's always virtual machines.

11 Jun 2026 2:13pm GMT

Apple recently announced its next crack at integrating "AI" into its operating systems, this time opting to simply whitelabel Google's Gemini "AI" tools instead of developing its own LLM technology. Called "Siri AI", Apple also stated it's not coming to the EU, and the company stated that's because the EU's basic consumer protection legislation would give other "AI" tools "unprecedented access" to user data on users' devices. The company made a big stink about this in the press. As anyone with basic pattern recognition skills already knew, this was a blatant, baldfaced lie. What really happened is that Apple asked the EU for an 18-month long exemption from the EU's consumer protection and privacy legislation during which it would not have to comply with any legal privacy and interoperability requirements - just so it could roll out Siri "AI" before anyone else could offer a competing product for Apple users. Obviously, the EU wasn't going to grant such an exemption. "The decision not to roll out Siri AI in the EU is Apple's and Apple's only," spokesperson Thomas Regnier told reporters in Brussels, saying there was nothing in the Digital Markets Act to stop the company from introducing new products in the EU. "Apple was simply unable to develop interoperability solutions that meet essential EU ​privacy and security standards," Regnier said. "Instead ​of trying to find ⁠a suitable compliance solution, Apple simply made a request to the European Commission to be exempted from their interoperability obligations under the DMA - and this for at least 18 months. ​That's not an option," Regnier said. ↫ Inti Landauro and Foo Yun Chee at Reuters So what's really going on here is that Apple wants to offer a set of whitelabeled Google Gemini tools on iOS and macOS in the EU, but because Apple is classified as a gatekeeper, it is legally obligated to offer interoperability options for competing "AI" tools. These options in turn need to adhere to the EU's strict privacy regulations, so that competing "AI" tools can offer the same level of privacy that Apple's own whitelabeled Google Gemini tools claim to offer. Apple didn't want to offer these privacy-respecting interoperability options as required by law, so instead of following the law in the countries it wants to operate in, Apple asked to be placed above the law for at least 18 months, basically giving Siri "AI" a massive head-start over possible competitors so that it could entrench itself in the userbase. The EU saw right through Apple's nonsense, and now called them out on their bullshit. Perhaps Apple has gotten so used to openly bribing Trump that they forgot other parts of the world don't work that way. Whenever Apple and its PR attack dogs say anything about the EU, you can be assured they are lying. They have proven time and time again to basically never speak a single word of truth when it comes to its dealings in the EU. It's almost pathological at this point, and what makes it doubly interesting is that Apple will not launch Siri "AI" in China either, for the very same regulatory reasons - yet all China got was a single footnote in a press release. I wonder why.

10 Jun 2026 11:12pm GMT