fidzu : Operating Systems

Mount Amiga filesystem images on macOS/Linux using native AmigaOS filesystem handlers via FUSE. amifuse runs actual Amiga filesystem drivers (like PFS3) through m68k CPU emulation, allowing you to read Amiga hard disk images without relying on reverse-engineered implementations. ↫ Amifuse GitHub page Absolutely wild.

22 Dec 2025 2:47pm GMT

Almost two months ago, a tape containing UNIX v4 was found. It was sent off to the Computer History Museum where bitsavers.org would handle the further handling of the tape, and this process has now completed. You can download the contents of the tape from Archive.org - which is sadly down at the moment - while squoze.net has a readme with instructions on how to actually run the copy of UNIX v4 recovered from the tape.

22 Dec 2025 2:21pm GMT

If you've been waiting for the right moment to try FreeBSD on a laptop, take note - 2025 has brought transformative changes. The Foundation's ambitious Laptop Support & Usability Project is systematically addressing the gaps that have held FreeBSD back on modern laptop hardware. The project started in 2024 Q4 and covers areas including Wi-Fi, graphics, audio, installer, and sleep states. 2025 has been its first full year, and with a financial commitment of over $750k to date there has been substantial progress. ↫ Alice Sowerby for the FreeBSD Foundation I think that's an understatement. As part of this effort, FreeBSD introduced support for Wi-Fi 4 and 5 in 2025, with 6 being worked on, and sound support has been greatly improved as well, with new tools and better support for automatic sound redirection for HDA cards. Another major area of improvement is support for various forms of sleep and wake, with modern standby coming in FreeBSD 15.1, and possibly hibernate in 15.2. On top of all this, there's the usual graphics drivers updates, as well as changes to the installer to make it a bit more friendly to desktop use cases. The FreeBSD project is clearly taking desktop and especially laptop seriously lately, and they're putting their money and developers where their mouth is. Add in the fact that FreeBSD already has pretty decent Wayland support, and it the platform will be able to continue to offer the latest KDE releases (and GNOME, if they figure out replacements for its systemd dependencies). With progress like this, we're definitely going to see more and more people making the move to FreeBSD for desktop and laptop use over the coming years.

21 Dec 2025 10:29pm GMT

If Excel rules the world, Word rules the legal profession. Jordan Bryan published a great article explaining why this is the case, and why this is unlikely to change any time soon, no matter how many people from the technology world think they can change this reality. Microsoft Word can never be replaced. OpenAI could build superintelligence surpassing human cognition in every conceivable dimension, rendering all human labor obsolete, and Microsoft Word will survive. Future contracts defining the land rights to distant galaxies will undoubtedly be drafted in Microsoft Word. Microsoft Word is immortal. ↫ Jordan Bryan at The Redline by Version Story Bryan cites two main reasons underpinning Microsoft Word's immortality in the legal profession. First, lawyers need the various formatting options Word provides, and alternatives often suggested by outsiders, like Markdown, don't come close to offering even 5% of the various formatting features lawyers and other writers of legal documents require. By the time you add all those features back to Markdown, you've recreated Word, but infinitely worse and more obtuse. Also, and this is entirely my personal opinion, Markdown sucks. Second, and this one you've surely heard before: Word's .docx format is effectively a network protocol. Everyone in the legal profession uses it, can read it, work with it, mark it up, apply corrections, and so on - from judges to lawyers to clients. If you try to work with, say, Google Docs, instead, you create a ton of friction in every interaction you have with other people in the legal profession. I vividly remember this from my 15 years as a translator - every single document you ever worked with was a Microsoft Office document. Sure, the translation agency standing between the end client and the translator might have abstracted the document into a computer-aided translation tool like Trados, but you're still working with .docx, and the translated document sent to the client is still .docx, and needs to look identical to the source, just in a different language. In the technology world, there's a lot of people who come barging into some other profession or field, claiming to know everything, and suggest to "just do x", without any deference to how said profession or field actually operates. "Just use Markdown and git" even if the people involved have no clue what a markup language even is let alone what git is; "just use LibreOffice" even if the people involved will skewer you for altering the formatting of a document even ever so slightly; we all know examples of this. An industry tends to work a certain way not because they're stupid or haven't seen the light - it tends to work that way because there's a thousand little reasons you're not aware of that make that way the best way.

18 Dec 2025 11:28pm GMT

In 1979, VisiCalc was released for the Apple II, and to this day, many consider it the very first spreadsheet program. Considering just how important spreadsheets have become since then - Excel rules the world - the first spreadsheet program is definitely an interesting topic to dive into. It turns out that while VisiCalc was the first spreadsheet program for home computers, it's not actually the first spreadsheet program, period. That honour goes to LANPAR, created ten years before VisiCalc. Ten years before VisiCalc, two engineers at Bell Canada came up with a pretty neat idea. At the time, organizational budgets were created using a program that ran on a mainframe system. If a manager wanted to make a change to the budget model, that might take programmers months to create an updated version. Rene Pardo and Remy Landau discussed the problem and asked "what if the managers could make their own budget forms as they would normally write them?" And with that, a new idea was created: the spreadsheet program. The new spreadsheet was called LANPAR, for "LANguage for Programming Arrays at Random" (but really it was a mash-up of their last names: LANdau and PARdo). ↫ Jim Hall at Technically We Write While there wasn't a graphical user interface on the screen with a grid and icons and everything else we associate with a spreadsheet today, it was still very much a spreadsheet. Individual cells were delinianated with semicolons, you could write down formulas to manipulate these cells, and the program could do forward referencing. The idea was to make it so easy to use, managers at Dell Canada could make budgeting changes overnight, instead of having programmers take weeks or months to do so. I'm not particularly well-versed in Excel and spreadsheets in general, but I can definitely imagine advanced users no longer really seeing the grids and numbers as individual entities, instead visualising everything much more closely to what LANPAR did. Like Neo when he finally peers through the Matrix.

18 Dec 2025 10:01pm GMT

Jamie Zawinski, one of the founders of Netscape and later Mozilla, has dug up the original versions of the iconic Mozilla dinosaur logos, and posted them online in all their glory. While he strongly believes Mozilla owned these logos outright, and that they were released as open source in 1998 or 1999, he can't technically prove that. It has come to my attention that the artwork for the original mozilla.org "dinosaur" logo is not widely available online. So, here it is. As I explained in some detail in my 2016 article "They Live and the secret history of the Mozilla logo", I commissioned this artwork from Shepard Fairey to use as the branding of the newly-founded mozilla.org and our open source release of the Netscape source code, which eventually became Firefox. This happened in March 1998. ↫ Jamie Zawinski The original Mozilla dinosaur logos are works of pure art. They sure don't make logos like this anymore.

18 Dec 2025 9:37pm GMT

Mark Weiser has written a really interesting article about just how desirable new computing environments, like VR, "AI" agents, and so on, really are. On the topic of "AI" agents, he writes: Take intelligent agents. The idea, as near as I can tell, is that the ideal computer should be like a human being, only more obedient. Anything so insidiously appealing should immediately give pause. Why should a computer be anything like a human being? Are airplanes like birds, typewriters like pens, alphabets like mouths, cars like horses? Are human interactions so free of trouble, misunderstandings, and ambiguity that they represent a desirable computer interface goal? Further, it takes a lot of time and attention to build and maintain a smoothly running team of people, even a pair of people. A computer that I must talk to, give commands to, or have a relationship with (much less be intimate with), is a computer that is too much the center of attention. ↫ Mark Weiser That's one hell of a laser-focused takedown of "AI" tools in modern computing. When it comes to voice input, he argues that it's too intrusive, too attention-grabbing, and a good tool is supposed to be the exact opposite of that. Voice input, especially when there's other people around, puts the interface at the center of everyone's attention, and that's not what you should want. With regards to virtual reality, he notes that it replaces your entire perception with nothing but interface, all around you, making it as much the center of attention as it could be. What's most fascinating about this article and its focus on "AI" agents, virtual reality, and more, is that it was published in January 1994. All the same questions, worries, and problems in computing we deal with today, were just as much topics of debate over thirty years ago. It's remarkable how you could copy and paste many of the paragraphs written by Weiser in 1994 into the modern day, and they'd be just applicable now as they were then. I bet many of you had no idea the quoted paragraph was over thirty years old. Mark Weiser was a visionary computer scientist, and had a long career at Xerox PARC, eventually landing him the role of Chief Technology Officer at PARC in 1996. He coined the term "ubiquitous computing" in 1988, the idea that computers are everywhere, in the form of wearables, handhelds, and larger displays - very prescient for 1988. He argued that computers should be unobtrusive, get out of your way, help you get things done that aren't managing and shepherding the computer itself, and most of all, that computers should make users feel calm. Sadly, he passed away in 1999, at the age of 46, clearly way too early for someone with such astonishing forward-looking insight into computing. Looking at what computers have become today, and what kinds of interfaces the major technology companies are trying to shove down our throats, we clearly strayed far from Weiser's vision. Modern computers and interfaces are the exact opposite of unobtrusive and calming, and often hinder the things you're trying to get done more than they should. I wonder what Weiser would think about computing in 2025.

17 Dec 2025 9:36pm GMT

In recent years, things have not been going well for Mozilla. Firefox's market share is a rounding error, and financially, the company is effectively entirely dependent on free money from Google for making it the default search engine in Firefox. Mozilla's tried to stem the bleeding with deeply unpopular efforts like focusing on online advertising and cramming more and more "AI" into Firefox, but so far, nothing has worked, and more and more of the remaining small group of Firefox users are moving to modded versions of Firefox without the "AI" nonsense and other anti-features. The task of turning the tide is now up to Mozilla's new CEO, Anthony Enzor-DeMeo, who took up the role starting today. In his first message to the public in his new role as CEO of Mozilla, he lays out his vision for the future of the company. What are his plans for Mozilla's most important product, the Firefox web browser? Firefox will grow from a browser into a broader ecosystem of trusted software. Firefox will remain our anchor. It will evolve into a modern AI browser and support a portfolio of new and trusted software additions. ↫ Anthony Enzor-DeMeo So far, the "AI" additions to Firefox have not exactly been met with thunderous applause - to put it mildly - and I don't see how increasing these efforts is going to magically turn that sentiment around. I'd hazard a guess that Firefox users, in particular, are probably quite averse to "AI" and what it stands for, further strengthening the feeling that the people leading Mozilla seem a little bit out of touch with their own users. Add to this the obvious fact that "AI" is a bubble waiting to pop, and I'm left wondering how investing in "AI" now is going to do anything but make Mozilla waste even more money. I don't want Firefox to fail, as it is currently the only browser that isn't Chrome, Chrome in a trench coat, or Safari, but it seems Mozilla is trying to do everything to chase away what few users Firefox had left. In the short term, we can at least use modified versions of Firefox that have the "AI" nonsense and other anti-features removed, but for the long term, we're going to need something else if Mozilla keeps going down the same path it's been going in recent years. The only viable long-term alternative is Servo, but that's still a long way off from being a usable day-to-day browser. The browser landscape ain't looking so hot, and this new Mozilla CEO is not making me feel any better.

16 Dec 2025 11:15pm GMT

Back in 2017 I wrote about a technique for creating closures in C using JIT-compiled wrapper. It's neat, though rarely necessary in real programs, so I don't think about it often. I applied it to qsort, which sadly accepts no context pointer. More practical would be working around insufficient custom allocator interfaces, to create allocation functions at run-time bound to a particular allocation region. I've learned a lot since I last wrote about this subject, and a recent article had me thinking about it again, and how I could do better than before. In this article I will enhance Win32 window procedure callbacks with a fifth argument, allowing us to more directly pass extra context. I'm using w64devkit on x64, but the everything here should work out-of-the-box with any x64 toolchain that speaks GNU assembly. ↫ Chris Wellons Sometimes, people get upset when I mention something is out of my wheelhouse, so just for those people, here's an article well outside of my wheelhouse. I choose honesty over faking confidence.

16 Dec 2025 3:27pm GMT

Any computing device will inevitably get a custom operating system - whether based on an existing operating system or something entirely custom - and of course, Kobo e-readers are no exception. QuillOS is an Alpine Linux-based distribution specifically developed for the unique challenges of e-readers, and comes with a custom Qt-based user interface, support for a whole slew of e-book formats, NetSurf as a web browser, encrypted storage, a VNC viewer, and a ton more. Basic hardware capabilities like Wi-Fi and power management are also supported, and it has online update support, too. The current release is already two years old, sadly, so I'm not sure how active the project is at this point. I wanted to highlight it here since something like this is a great way to liberate your Kobo device if, for some reason, Kobo ever started making their devices worse through updates, or the company shutters its services. You know, something that seems rather relevant today. Sadly, my own Kobo does not seem to be supported.

16 Dec 2025 3:21pm GMT

There's a new Haiku monthly activity report, and this one's a true doozy. Let's start with the biggest news. The most notable development in November was the introduction of a port of the Go programming language, version 1.18. This is still a few years old (from 2022; the current is Go 1.25), but it's far newer than the previous Go port to Haiku (1.4 from 2014); and unlike the previous port which was never in the package repositories, this one is now already available there (for x86_64 at least) and can be installed via pkgman. ↫ Haiku activity report As the project notes, they're still a few versions behind, but at least it's a lot more modern of an implementation than they had before. Now that it's in the repositories for Haiku, it might also attract more people to work on the port, potentially bringing even newer versions to the BeOS-inspired operating system. Welcome as it may be, this new Go port isn't the only big ticket item this month. Haiku can now gracefully recover from an app_server crash, something it used to be able to do a long time ago, but which was broken for a long time. The app_server is Haiku's display server and window manager, so the ability to restart it at runtime after a crash, and have it reconnect with still-running applications, is incredibly welcome. As far as I can tell, all modern operating systems can do this by now, so it's great to have this functionality restored in Haiku. Of course, aside from these two big improvements, there's the usual load of fixes and changes in applications, drivers, and other components of the operating system.

12 Dec 2025 11:51pm GMT

Alpine Linux maintainer Ariadne Conill has published a very interesting blog post about the shortcomings of both sudo and doas, and offers a potential different way of achieving the same goals as those tools. Systems built around identity-based access control tend to rely on ambient authority: policy is centralized and errors in the policy configuration or bugs in the policy engine can allow attackers to make full use of that ambient authority. In the case of a SUID binary like doas or sudo, that means an attacker can obtain root access in the event of a bug or misconfiguration. What if there was a better way? Instead of thinking about privilege escalation as becoming root for a moment, what if it meant being handed a narrowly scoped capability, one with just enough authority to perform a specific action and nothing more? Enter the object-capability model. ↫ Ariadne Conill To bring this approach to life, they created a tool called capsudo. Instead of temporarily changing your identity, capsudo can grant far more fine-grained capabilities that match the exact task you're trying to accomplish. As an example, Conill details mounting and unmounting - with capsudo, you can not only grant the ability for a user to mount and unmount whatever device, but also allow the user to only mount or unmount just one specific device. Another example given is how capsudo can be used to give a service account user to only those resources the account needs to perform its tasks. Of course, Conill explains all of this way better than I ever could, with actual example commands and more details. Conill happens to be the same person who created Wayback, illustrating that they have a tendency to look at problems in a unique and interesting way. I'm not smart enough to determine if this approach makes sense compared to sudo or doas, but the way it's described it does feel like a superior, more secure solution.

12 Dec 2025 11:35pm GMT

Unix has been enormously successful over the past 55 years. It started out as a small experiment to develop a time-sharing system (i.e., a multi-user operating system) at AT&T Bell Labs. The goal was to take a few core principles to their logical conclusion. The OS bundled many small tools that were easy to combine, as it was illustrated by a famous exchange between Donald Knuth and Douglas McIlroy in 1986. Today, Unix lives on mostly as a spiritual predecessor to Linux, Net/Free/OpenBSD, macOS, and arguably, ChromeOS and Android. Usenet tells us about the height of its early popularity. ↫ Gábor Nyéki There are so many amazing stories in this article, I honestly have no idea what to highlight. So first and foremost, I want you to read the whole thing yourself, as everyone's bound to have their own personal favourite section that resonates the most. My personal favourite story from the article - which is just an aside, to illustrate that even the asides are great - is that when Australia joined Usenet in 1983, new posts to Usenet were delivered to the country by airmail. On magnetic tape. Once per week. The overarching theme here is that the early days of UNIX, as documented on Usenet, were a fascinating wild west of implementations, hacks, and personalities, which, yes, clashed with each other, but also spread untold amounts of information, knowledge, and experience to every corner of the world. I hope Nyéki will write more of these articles.

12 Dec 2025 10:27pm GMT

System76, creator of Pop!_OS and prominent Linux OEM, has just announced the release of Pop!_OS 24.04 LTS - normally not something I particularly care about, but in this case, it comes with the first stable release of COSMIC Desktop. COSMIC is a brand new desktop environment by System76, written in Rust, and after quite some time in development, it's now out in the wild as a stable release. Today is special not only in that it's the culmination of over three years of work, but even more so in that System76 has built a complete desktop environment for the open source community. We're proud of this contribution to the open source ecosystem. COSMIC is built on the ethos that the best open source projects enable people to not only use them, but to build with them. COSMIC is modular and composable. It's the flagship experience for Pop!_OS in its own way, and can be adapted by anyone that wants to build their own unique user experience for Linux. ↫ Carl Richell You don't need to run Pop!_OS to try out COSMIC, as it's already available on a variety of other distributions (although it may take a bit for this stable version to land in the respective repositories).

11 Dec 2025 8:33pm GMT

I'm sure most of us here are aware of the bright red-and-yellow colour scheme called "Hot Dog Stand", included in Windows 3.1. While it's not the only truly garish colour scheme included in Windows 3.1, its name probably did a lot to make it stand out from the others. There's been a ton of speculation about the origins of the colour scheme, and why it was included in Windows 3.1, but it seems nobody ever bothered to look for someone who actually worked on the Windows 3.1 user interface - until now. PC Gamer's Wes Fenlon contacted Virginia Howlett, Microsoft's first user interface designer who joined the company in 1985, and asked her about the infamous colour scheme. It turns out that the origin story for the infamous colour scheme is rather mundane. In Howlett's own words: I do remember some discussion about whether we should include it, and some snarky laughter. But it was not intended as a joke. It was not inspired by any hot dog stands, and it was not included as an example of a bad interface-although it was one. It was just a garish choice, in case somebody out there liked ugly bright red and yellow. ↫ Virginia Howlett, quoted by Wes Fenlon in PC Gamer Howlett then lists a few other included colour schemes that were just as garish, or even more so, as examples to underline her point. Personally, I'm a huge proponent of allowing users to make their interfaces as ugly and garish as they want, as the only arbiter on what's on your screen is you, and nobody else. Hot Dog Stand and similar garish themes need to make a comeback, because there's bound to be some people out there whose vibes align with it.

11 Dec 2025 8:17pm GMT

IBM owns Red Hat which in turn runs Fedora, the popular desktop Linux distribution. Sadly, shit rolls downhill, so we're starting to see some worrying signs that Fedora is going to be used a means to push "AI". Case in point, this article in the Fedora Magazine: Generative AI systems are changing the way people interact with computers. MCP (model context protocol) is a way that enables generate AI systems to run commands and use tools to enable live, conversational interaction with systems. Using the new linux-mcp-server, let's walk through how you can talk with your Fedora system for understanding your system and getting help troubleshooting it! ↫ Máirín Duffy and Brian Smith at Fedora Magazine This "linux-mcp-server" tool is developed by IBM's Red Hat, and of course, IBM has a vested interest in further increasing the size of the "AI" bubble. As such, it makes sense from their perspective to start pushing "AI" services and tools all the way down to the Fedora community, ending up with articles like this one. What's sad is that even in this article, which surely uses the best possible examples, it's hard to see how any of it could possibly be any faster than doing the example tasks without the "help" of an "AI". In the first example, the "AI" is supposed to figure out why the computer is having Wi-Fi connection issues, and while it does figure that out, the solutions it presents are really dumb and utterly wrong. Most notably, even though this is an article about running these tools on a Fedora system, written for Fedora Magazine, the "AI" stubbornly insists on using apt for every solution, which is a basic, stupid mistake that doesn't exactly instill confidence in any of its other findings being accurate. The second example involves asking the "AI" to explain how much disk space the system is using, and why. The "prompt" (the human-created "question" the "AI" is supposed to "answer") is bonkers long - it's a 117 words long monstrosity, formatted into several individual questions - and the output is so verbose and it takes such a scattershot approach that following-up on everything is going to take a huge amount of time. Within that same time frame, it would've been not only much faster, but also much more user-friendly to just open Filelight (installed by default as part of KDE), which creates a nice diagram which instantly shows you what is taking up space, and why. The third example is about creating an update readiness report for upgrading from Fedora 42 to Fedora 43, and its "prompt" is even longer at 190 words, and writing that up with all those individual questions must've taken more time than to just… Do a simple dry-run of a dnf system upgrade which gets you like 90% of the way there. Here, too, the "AI" blurts out so much information, much of which entirely useless, that going through it all takes more time than just manually checking up on a dnf dry run and peaking at your disk space usage. All this effort to set all of this up, and so much effort to carefully craft complex "prompts", only to end up with clearly wrong information, and way too much superfluous information that just ends up distracting you from the task you set out to accmplish. Is this really the kind of future of computing we're supposed to be rooting for? Is this the kind of stuff Fedora's new "AI" policy is supposed to enable? If so, I'm afraid the disconnect between Fedora's leadership and whatever its users actually use Fedora for is far, far wider than I imagined.

11 Dec 2025 7:51pm GMT