fidzu : Operating Systems

There are many problems in this world - some big, some small, some so minute nobody ought to put them to paper at all. The problem I'm going to highlight here is even smaller than that. This literally - the actual literally - does not matter and absolutely nobody should care about it, let alone put any work into changing it or addressing it some other way. I want to talk about the iconography GNOME's Disks utility uses to symbolise "mount" and "unmount". No, I'm not descending into madness. GNOME's Disks utility uses the "play" symbol on the mount button, and the "stop" symbol on the unmount button. Inexplicably, considering the state of the world in general and the rapidly deteriorating quality of software specifically, this bothers me. Out in the real world, built on decades of consistent use, these symbols have gained clearly defined meanings, and mounting and unmounting disks definitely isn't one of them. In fact, the meaning of these symbols isn't mere convention; they're defined in a variety of international standards for symbols for use in software and on equipment, such as ISO/IEC 18035 (which you need to buy to read; my copy fell of a truck): ISO/IEC 18035:2002 defines a consistent set of icons and related functions that are represented by multimedia applications on a computer screen and that users interact with to control such applications. It describes controls applying to such functions as: Play, Pause, Stop, Rewind, Scan forward, Scan backward, Replay backward, Loop, Go to beginning, Go to previous, Go to next, Go to end, Set volume and Mute. ↫ ISO/IEC 18035:2003 They're also part of ISO 7000/IEC 60417, a much larger, more encompassing standard that also contains things like the various symbols used on laundry machines, tumble dryers, in cars, and so on. The symbols themselves are much older than the standards, of course, with many of them dating back to the 1960s and possibly even 1950s. The point remains, though: the play and stop symbols have clearly defined meanings, and I don't think they are at all a good fit for mount and unmount. The function of the "play" symbol according to ISO/IEC 18035: To enable the user to start the presentation of dynamic media, except where the task requires automatic playing of that media. ↫ ISO/IEC 18035:2003 And of the "stop" symbol: To enable the user to stop the presentation of dynamic media. ↫ ISO/IEC 18035:2003 Neither of these descriptions match what mounting and unmounting mean or do. Mounting a drive or partition doesn't present any media at all; it merely makes the drive or partition in question accessible. Unmounting also doesn't eject anything; it merely makes the drive or partition inaccessible. I would argue that play and pause act upon contents of a drive or volume, and not upon the drive or volume itself. As it stands right now, you "play" a drive" to "play" a video stored on said drive. Madness. I already know what you're thinking, and yes, I agree that the Disks utility is a tool aimed at more advanced use cases and users, and most normal, average users will never even know it exists, let alone open it at all. Very few people get to see these symbols, and those that do already know full well what mounting and unmounting mean, reducing the importance of said symbols considerably. But now it's time for the big surprise, the twist in the story that turns this entire thing on its head. Files, GNOME's file manager, uses an entirely different symbol for unmounting! Instead of the "stop" symbol, Files uses the "eject" symbol. You may think this is a more accurate visual representation of what unmounting means, but I strongly disagree. Let's turn to ISO/IEC 18035:2003 once again: To enable the user to eject the current physical media from the appropriate drive. ↫ ISO/IEC 18035:2003 Unmounting doesn't eject anything! If you unmount a USB stick, the stick doesn't get fired out of the USB port. If you unmount a volume, it doesn't get removed from the SSD. Hell, if you unmount a CD-ROM, it doesn't even eject it! Ejecting a CD-ROM - opening the drive's tray or spitting the CD-ROM out of a slot-loader - is an entirely different act! Are we really "ejecting" a CD-ROM twice? Are we "mounting" a CD-ROM when we merely close the tray? No! Madness! The real underlying problem here is, of course, that mounting and unmounting are deeply weird and confusing concepts, bordering on the esoteric, that simply do not have physical equivalents to fall back on. Using symbols and iconography designed in the 1960s explicitly for playing music or stopping a video or ejecting a cassette tape are not a good fit for something as difficult to explain to most people as mounting and unmounting. It's like putting an eject symbol on a car's door handle or a play symbol on a soap dispenser. Should GNOME developers waste any time or resources to address this? No, of course not, that would be stupid. Nobody should care about this but me. I should suffer in silence, every time I need to mount or unmount something, forced to look for an eject or stop symbol in whatever user interface I happen to be using. Every time, I should die a little inside. Please, don't be like me and waste precious resources thinking about this. I'm not descending into madness. I just want mount and unmount symbols that make sense. I'm not descending into madness.

12 Nov 2026 10:13am GMT

We're almost halfway through November, but we hadn't seen Haiku's monthly activity report for October yet. It's here now, and there's quite a few good things in here, like support for two and three-finger tap gestures on touchpads for right and middle-click, a new driver that adds Universal Flash Storage support, and even some build fixes for Haiku's SPARC port as well as some fixes on the RISC-V side. Of course, that's just a selection, as there's the usual long list of smaller changes, bugfixes, and improvements as well.

11 Nov 2026 3:22pm GMT

Today, we're excited to announce the release of .NET 11! This year's release makes building modern applications faster, more productive, and has improvements across C# 15, ASP.NET Core, .NET MAUI, and Windows development. With hundreds of runtime optimizations, more responsive SDK tooling, and less overhead in everyday commands, you can spend less time waiting and more time creating. Build richer web and cross-platform applications, take advantage of new C# language features, and explore AI-powered development with improved tools and agentic capabilities. ↫ .NET Team I'm not going to pretend to care about .NET, but I know many of you have to care on a professional level, because .NET is remarkably popular in places where the spotlights don't often shine.

11 Nov 2026 3:13pm GMT

An interesting question, and a detailed technical rundown of how to make this happen, which involved building a custom Linux kernel, of course. I really, really enjoy the conclusion. And you know? It turned out fine. Nothing exploded on my system. As I could predict, because this was otherwise impossible, nobody did it. The signal system was setup in such a way that you would most likely realize something you were doing was wrong, and not try it. To pull back further, it is interesting to notice how the rules we all take for granted are just set somewhere in code. They were written by someone, at some point. If there is code restricting you from doing something, someone wrote it. Either they did not think anyone would want to do that thing, or they specifically prevented you from doing it. Those rules are written somewhere, and you can take it in your paws to go sniff around the code, pull out the relevant parts, and hack around the things that bother you. For fun, learning, or convenience. Snoop around. Sniff code. Put your paws in it. Hack shit. ↫ lux at VulpineCitrus Even if there's no real reason to do, even if it's just to satiate an odd and possibly slightly morbid sense of curiosity, fuck with code.

11 Nov 2026 3:10pm GMT

OpenIndiana is a rolling-release illumos distribution, but they do release snapshots twice a year to serve as a base for installations, which they call Hipster. The project's just released OpenIndiana Hipster 2026.10, and it brings a number of welcome changes. First, there's UEFI framebuffer support on the live image, which is automatically configured when loading up the image. Second, Firefox and Thunderbird versions have been bumped to 159.0, and a whole slew of development tools have been updated to newer versions as well. This snapshot also brings QEMU 11.1.2 and VirtualBox 7.2.22, and a number of new applications have been added as well. In addition, SPARC build support has been improved to enable new and updated packages for Sun's dead ISA as well. You can download a fresh image, or update an existing installation through IPS.

09 Nov 2026 2:23pm GMT

Creator and lead developer of Chimera Linux, Nina "q66", write about their efforts to get NVIDIA drivers to work properly on musl-based distributions. As you may be aware, one of the limitations of musl-based distributions is that they will not function to their proper extent when used in computers with various NVIDIA graphics cards. This is due to the proprietary nature of the driver, being built for glibc. I have been experimenting with trying to make this work, and this post is the summary of that effort. ↫ Nina "q66" on the Chimera blog What follows is a deeply technical exploration of the problem, and the steps Nina q66 and the Chimera team are taking to try and fix it. With how popular and widespread NVIDIA hardware still is, this is a hugely important issue to try and address, and I'm grateful they're trying to address it.

09 Nov 2026 2:17pm GMT

About five months after the previous release, the MorphOS team has released MorphOS 3.21. It brings the usual list of big fixes and smaller improvements, but there's a few big ticket items in here as well. MorphOS 3.21 introduces BasicWorks, an office suite made up of CellBasics and PageBasics. It offers document and spreadsheet authoring and loads and saves Microsoft Office and OpenOffice documents. Also new are NVMEMount, an auto-mounter for booting from and mounting NVMe partitions, and the Marbles and Cyber 3D blankers. Graphics performance has been improved, with a faster Radeon driver on cards with little video memory thanks to GART backed bitmap transfers, quicker TinyGL texture copies, hardware accelerated antialiased text in TTEngine and much faster color SVG glyph rendering in Cairo. The Bcm43xx wireless driver has been substantially reworked, with automatic transmit rate selection, updated firmware and numerous connection fixes. PowerBook and iMac hotkeys are now fully configurable. ↫ MorphOS 3.21 release announcement The BasicWorks office suite has been in the works for a while now, and more information on it can be found in a thread on the MorphZone forums and on the website for the spreadsheet component of the suite, CellBasics. The formula loaders and xlsx loaders are ports of open source projects, but the rest of the application is new code based on ObjectiveC++ and Cairo/Harfbuzz. It uses its own file format, but can import csv and xslsx files, so I'm assuming the same more or else applies to the word processor (but with docx, of course). Alongside MorphOS 3.21 also comes a new release for Wayfarer, the web browser the Amiga-inspired operating system uses. Wayfarer 12.0 moves to WebKitGTK 2.52.5 (which was released in July of 2026, so it's quite up to date), and now uses the Skia graphics library. R300-R500 Radeons will render websites with Skia-GL for some massive performance improvements, helped further along by a slew of additional performance optimisations. Adblocking has been improved as well, YouTube should work a lot better now, and much more. The full release notes for MorphOS 3.21 give you all the details.

07 Nov 2026 7:46pm GMT

Ask any program to listen on port 0 and it will hand you a socket on port 47193…or 58037…or whatever the kernel felt like that day. Port 0 is not a port you can have. It is the number you pass when you want the operating system to pick one for you. But a TCP header is just bytes. The destination port field is 16 bits wide, and 0x0000 fits in 16 bits as well as anything else does. Nothing on the wire stops a packet from being addressed to port 0. Your tools will refuse it, your browser will block it, and your scanner's default port list skips it, because everyone agrees it isn't a real port. Which makes it a pretty good place to hide things, whether anyone meant to or not. So we did some TCP cowboy shit & port scanned the entire fucking internet for open ports on port 0, which uncovered some interesting unexpected findings. ↫ acidvegas An awesome and entertaining read. Don't skip this one.

07 Nov 2026 7:33pm GMT

A little tidbit of news regarding the nest major update to Windows, known as Windows 11 27H2. Apparently, it's going to come with some more serious changes to the codebase, therefore necessitating a full operating system swap instead of a mere enablement package, much like Windows 11 24H2 was. For those who need a refresher, Microsoft has long been rumored to be running on a three-year release cadence and for a while, it was even thought that the company would launch Windows 12 in 2H 2024. That evidently didn't happen, as instead we got Windows 11 24H2, but it was a major upgrade, a full OS swap compared to Windows 11 23H2 and 22H2. Essentially, it looks like every three releases, Microsoft is performing a full swap with major changes in the underlying codebase, and it seems to line up with Windows 11 27H2 as well. At the moment it's not known if system requirements will change or not. ↫ Sayan Sen at Neowin.net Microsoft is currently testing adding support for Intel's Advanced Performance Extensions, which should yield improved 64bit performance and reduced power consumption. It makes sense to assume this support will be coming with Windows 11 27H2, which should hopefully lead to tangible performance improvements across the board. Also, there's going to be a new default wallpaper. Be still my beating heart.

07 Nov 2026 7:27pm GMT

Ubuntu has been at the forefront of replacing the traditional versions of basic tools like sudo with replacements written in Rust, but aside from worries about replacing battle-tested code with brand new, relatively untested code, there's new things to worry about it. As it turns out, sudo-rs, the Rust replacement for sudo, is intentionally incompatible with the classic version in dangerous ways, as Chris Siebenmann discovered to his dismay. Basically, the classic sudo supports the use of wildcards defined using square brackets, so that if you allow a user to run, say, /usr/sbin/exim -bp, without a password, they can run exim -bpa, exim -bpc, exim -bpr, or exim -bpu without having to supply a password. This allows for very specific, fine-grained access control, which is quite a nice capability to have if you're managing many systems and users. Sadly, sudo-rs intentionally does not support this, opting to only allow you to use the generic * wildcard. Worse yet, it doesn't really make this clear, either. ↫ Chris Siebenmann I do not really have words for this. The Rust sudo has apparently opted to keep the single most dangerous wildcard while disallowing all of the wildcards that allow one to be narrow and specific about what you're allowing, and it buries this at the end of a section that devotes a bunch of words to describing functionality it doesn't have and doesn't support, with absolutely nothing else in that section to say this (either up front or in the descriptions of how all the wildcards would work if sudo-rs supported them, which it doesn't). If you're going to replace such vital, core tools like sudo that god knows how many people rely on every single day, you better be damn sure you're feature-complete and can act as a drop-in replacement. If someone switches from sudo to doas, nobody expects the experience to be identical. However, if you're consistently being told that sudo-rs is a drop-in replacement and you shouldn't expect any disruptions, you better be able to make true on that promise. Ubuntu isn't some also-ran small hobby distribution, and its developers should act like it. What a clown show.

05 Nov 2026 4:24pm GMT

The second desktop environment release I've got for you today is LXQt 2.5.0. This new version excises its last LXDE dependency, and QTerminal and QTermWidget received considerable improvements, like new background image modes, a visual bell, support for OSC-8 hyperlinks, and more. There's a ton of smaller changes and improvements as well, but do note that due to a bug, 2.5.0 broke LXQt's Monitor Settings on X11. The project intends to fix this as quickly as possible and push a point release to address this issue.

05 Nov 2026 4:03pm GMT

It's desktop environment Thursday, as I've got two new releases for you today. First, Cinnamon, the desktop environment primarily associated with Linux Mint, has hit version 6.8. This version will officially ship with Linux Mint 27, scheduled for around Christmas of this year. Highlights of Cinnamon 6.8 include hibernation support via a Suspend action in the main menu, modern one-to-one trackpad gestures for both Wayland and Xorg sessions, support for the oo7 Secret Service provider, support for multiple instances in the Sound applet, and a more unified Network applet that merges the WireGuard and VPN sections. ↫ Marcus Nestor at 9To5Linux While Cinnamon is first and foremost a Linux Mint project, it's available on countless other distributions as well, including dedicated variants for popular distributions like Fedora and Ubuntu. Its Wayland support is finally materialising too, which is long overdue.

05 Nov 2026 3:57pm GMT

The first point release for NetBSD 11 has been released. As the version number suggests, there's no major changes here. This release includes security updates for mozilla-rootcerts, brotli, xorg-server, hdaudio(4), compat_linux(8), unbound(8), and ipfilter. Among the non-security related changes are improved USB device stability on Raspberry Pi, fixed hot-plugging bugs in various USB Wi-Fi drivers, support for battery monitoring on the Microsoft Surface Go 3, fixed thread-local storage on ARMv5, fixes for running the MIPS Malta and PA-RISC ports under QEMU, support for the Zhaoxin KX-7000 CPU, and support for sensors, i2c, real-time clocks, and fan control on Sun Ultra 25/45 and Sun Fire V215/V245 machines. ↫ Nia Alarie on the NetBSD blog The full release notes provide more details.

04 Nov 2026 10:52pm GMT

Another interesting post from Raymond Chen, this time about the difficulty of dealing with a system that's become CPU-starved. The question is simple: why not just run Task Manager and important parts of the UI like the taskbar at a higher priority? The catch with running anything at high priority is that unless you have been very careful to avoid it, you will eventually run into a shared resource that you will have to wait for, and you are now stuck. Your priority checkout pass gets you to the front of the line, but if the person at the register has a large shopping cart full of groceries, you just have to wait until they are done before you get your chance. Even if the code that protects the shared resource is careful to avoid priority inversion by transferring the priority of the waiter to the thread that owns the resource, you are still stuck waiting, and that owning thread might be doing something that takes a long time, like, say, accessing a file over the network. ↫ Raymond Chen If a system has reached a state where even accessing or using something like a task manager becomes a problem, I personally just bonk my computer over the head with a forced shutdown using the power button. Honestly though, I can't remember the last time I've had to do this, as my Linux machines all seem to handle problematic applications just fine. That being said, I'm sure people managing tons of servers and/or workstations and developers debugging their own running code run into catastrophic problems like this far more often, making forced shutdowns not as practical. Have a terminal window open with top and easy access to the kill command, or make sure you can just ssh into it remotely if the UI has gone completely nuts.

04 Nov 2026 10:44pm GMT

What if you want to change the time in your car's infotainment system, but it's so locked down that you can't even open the time settings menu without a very specific, DRM'd SD card? Well, you try to jailbreak it, of course, but the amount of effort required can kind of spiral out of control. And then, all the way at the end, it's just an offset. The first thing I did was use this to create a full backup of the internal eMMC using dd. With a more complete dump of the system, I pretty quickly figured out that the date & time settings that I'm interested in are in /mnt/flash/settings.dat, which is a custom binary format. After some more reverse engineering, it turned out the unit doesn't really have a concept of timezones at all. It gets the time from GPS and stores the local offset as a number of minutes. Mine was set to 180. I changed it to 120. That is how I was finally able to fix my car's timezone. ↫ Rasmus Moorats This harrowing story involved an older car - a 2014 Renault Latitude - but with the number of screens and the amount of user-facing software only increasing every year, requiring jailbreaks to get your car to do what you want it to do are only going to become more common. I wouldn't be surprised if whole generations of cars are going to become much harder to sell in the near future, cratering the used market, because people are not willing to put up with software problems nobody wants to or can fix. He just wanted to change the goddamn time.

04 Nov 2026 10:33pm GMT

Enlightenment, the long-running desktop environment and associated libraries and frameworks, just released version 0.28.0. It brings initial support for NetBSD, support for Network Manager and a whole slew of related changes and fixes to make that possible, as well as native PipeWire support. There's also a brand new clipboard manager, which brings with it modernisations and bug fixes for related UI elements. This release also reworks a ton code related to battery management, AC polling, and more, adding features like setting battery thresholds, ACPI power profile support, and so on. Of course, there's also the long list of smaller fixes and changes. You can download the release and build it yourself, or wait for your distribution of BSD variant to package it.

02 Nov 2026 8:31pm GMT