fidzu : Operating Systems

A great and concise history of the run-up to MS-DOS 2.0. Yet, there was a nagging feeling that a single-tasking CP/M clone was inadequate for the new generation of personal computers. Digital Research released multi-user, multitasking MP/M-86 in September 1981 and announced the single‑user multitasking Concurrent CP/M in early 1982. In response, Microsoft came up with a plan for tiered approach to its operating systems: single-user/single-tasking MS-DOS at the bottom; multi-user/multitasking XENIX at the top; and in the middle, something called XEDOS: a single-user version of XENIX. This "pyramid of upward-compatible operating systems" was announced in a Byte Magazine editorial in January 1982. ↫ Nemanja Trifunovic I've always found this tiered approach fascinating, and the world surely would've looked quite different had Microsoft been able to make it work. I doubt Windows NT would ever have existed, and most of the world would probably be running a XENIX-based Windows today (all else being equal, which is of course unlikely and silly). Regardless, MS-DOS 2.0 contained a few UNIX-like utilities to deal with its brand new support for directory trees and other new features, and even had a /dev directory.

18 Aug 2026 9:59am GMT

If you thought pervert glasses weren't bad enough, Apple is taking it up a notch by adding cameras to its AirPods. Apple is working on camera-equipped AirPods that appear to be nearly ready to launch, based on a video MacRumors found in the macOS Tahoe 26.7 release candidate. In a short demo, a man holds a book up so the camera in the AirPods can see the title. "With Visual Intelligence, your world becomes savable. See something you like? Just ask me to save it for later," says the voiceover text. ↫ Juli Clover at MacRumors AirPods are tiny. I've seen people use them at the gym. I've seen them on playgrounds. I've seen them around swimming pools. People use them at the beach. They're used at schools. In locker rooms. Tiny cameras in tiny AirPods that can photograph anything in front of the user are a pervert's wet dream. Abusers are going to love this. Why wear bulky glasses anyone can see and try to demand you take off, when you can wear tiny AirPods that have already been fully normalised in society? Was there not a single woman or parent on the team that made this? All over the United States, people are destroying Flock surveillance cameras. More and more communities are rising up and demanding these things removed from their streets and neighbourhoods. The awareness of just how pervasive mass government surveillance has become is growing, and Silicon Valley's complicity is not exactly a secret. And in this climate of rapidly growing concern and anger, Apple is going to add tiny cameras to its tiny AirPods. Was there not a single person of colour or protester on the team that made this? How detached from reality do you have to be to greenlight something like this? Does anyone - regardless of skin colour, gender, or political leaning - want even more cameras around them?

18 Aug 2026 9:41am GMT

I was around when Quake was launched, but I was entirely unaware of this story. By June 1996, after three years of hard work, id Software had completed their next title, Quake. As for their previous title, they were going to release both a shareware version and a full version of their game. Since it used a mere 22 MiB of storage, people at id Software had the idea of leveraging the remaining capacity of a CD-ROM. Why not include encrypted versions of the full id catalogue of games? Not only this would cut out the middlemen, it would give instant access to gamers with a simple phone call and a credit card. The concept was implemented. The CD was announced on July 3, 1996 and released on August 30th. The hacker group GNOMON released Quakecrk.zip only 39 days later. The archive contained QCRACK.EXE, a tool allowing to decrypt every single game on the CD-ROM. ↫ Fabien Sanglard The system id employed turned out to be incredibly primitive and simple, and hackers found out quite easily that the system required no secret sauce from id at all - the code you'd get over the phone contained no secret, and all the validation program on the disk did was check to ensure the code received over the phone matched the code generated by the disk. No wonder it took them only 39 days to crack this.

18 Aug 2026 9:24am GMT

Earlier this year, Natalie Vock made a splash with a set of patches to the Linux kernel that greatly increased performance on AMD GPUs with lower amounts of VRAM. With that work now accepted by upstream, Vock decided to turn their attention to another interesting problem: what if you run out of VRAM, and how can we improve performance when we do? Regardless, what I hope this blogpost can demonstrate is that even if you end up with some memory evicted to system RAM, the slowdown can be manageable. There's measures that drivers (particularly, the kernel driver) can take to make overcommit work as fast as possible, and even applications can do their part in coordinating with the driver stack to mitigate the effects of their memory being evicted. With everything in place, VRAM overcommit isn't really as big of a deal as one may think it is at first sight. ↫ Natalie Vock The work Vock has done has already been in SteamOS for a while, and they're currently in the process of upstreaming it to the vanilla kernel as well. Since this is a complex set of patches and changes, this may take a while, and as such, they've prepared custom kernel and Mesa branches for adventurous users. Do note that these branches won't be maintained much, and are entirely experimental, not as well-tested as the SteamOS kernel, and probably won't yield the same performance improvements. Still, this is the kind of work that has a material impact for users. Not everyone has a 16GB monster GPU, especially not today with supply chains ravaged and ruined by slopmakers, so it's great to see the Linux world working to improve performance for everyone, not just the wealthy few.

18 Aug 2026 9:13am GMT

The Touch Bar arrived in 2016 seemingly already pre-doomed, on a generation of machines that had a "we've run out of ideas" smell all around them. The arrow keys were reshaped, the keyboard got a slimming down, and even the beloved MagSafe wasn't, in fact, safe. All of these changes would prove unpopular and get reverted in time, and the axe would eventually come for the Touch Bar, too. With an enormous benefit of hindsight, a decade after its arrival, and on the (rumored) eve of fully multitouch MacBooks, I wanted to look critically at the Touch Bar in more detail. I put a spicy title above this post, and while I'm not sure I can answer it in the affirmative, I feel I got surprisingly close to that. ↫ Marcin Wichary I have never spent this much reading about and pondering a technology seemingly nobody liked and that I never really used. I still think there's merit to the idea of screen on a keyboard, but only if the screens are integrated into the individual keys (as some products have tried over the years). Of course, this would also be astronomically expensive, delicate, and virtually impossible to repair, so I'm not sure something like that can be reasonably made at an affordable price.

18 Aug 2026 8:48am GMT

Version 7.2 of the Linux kernel has been released. Significant features in this release include common attributes support in the bpf()vsystem call, cache-aware load balancing for the CPU scheduler, large-folio support in the Btrfs filesystem, further swap subsystem improvements, improvements to the Landlock security module, support for block devices with inline encryption hardware via the dm-inlinecrypt device-mapper target, and much more. ↫ corbet at LWN.net If you run Linux, you'll get it sooner or later.

17 Aug 2026 1:11pm GMT

We talked about the latest release of Delphi a few days ago, and that brought me to Hans Otten's website. This site is about my experience with the Wirth school of languages, based on the ideas and implementations of Prof Niklaus Wirth, Kenneth Bowles, Per Brinch Hansen, colleagues, and their students. And my experience with the various variants, from the P2 and P4 compilers originating in Zürich ETH, via UCSD Pascal P-System to the Borland compilers and Modula and Oberon systems. All applicable to small computers and device control. On this website you will find information on Pascal for small machines, like Wirth compilers, the UCSD Pascal system, many scanned books and other files on UCSD Pascal, Pascal on MSX and CP/M, Delphi programming on PC, Freepascal and Lazarus on Windows and Raspberry Pi, Oberon systems. Many sources of early Pascal compilers! And last but not least my Pascal-M system! ↫ Hans Otten If you're into Pascal and its related languages and technologies, this is a treasure trove of information.

17 Aug 2026 1:05pm GMT

One of the most surprising aspects of the Nix language is that it is lazy, especially if you have never used a lazy language before. This laziness is what makes much of Nixpkgs possible, and its complexity. I decided to take that idea and make the attribute path a sequence of button presses in Super Mario Bros. 3. Each node in the tree is a frame of the game, and each child is a button press that produces a new frame. Game states are recursive by nature. ↫ Farid Zakaria This has zero practical applications, and yet, it's absolutely genius. I love this.

17 Aug 2026 12:52pm GMT

Today, you can get low-quality knockoffs of just about any popular smartphone on sites like AliExpress or Temu, whether they be iPhones, Galaxy phones, or whatever else. They have terrible build quality, bottom-of-the-barrel components and specifications, and all run outdated versions of Android - badly. At the same time, various consumer electronics brands, once popular in a bygone era, sell the rights to their brand name to unknown companies, who then put these brands on generic hardware to give their products a sheen of legitimacy. That's why today, you can still buy Nokia smartphones, Polaroid cameras, and low-effort Hi-Fi equipment from various once-respected brands. None of this is new, however. In the late '90s and early 2000s, companies were already doing the same thing. In fact, there's one device from this era which combines both business practices - it's both a cheap knockoff of a wildly successful device, and it carries a once-revered brand name. Also, just to add some juice, this story involves stolen source code. Let's take a look at the worst PDA of all time, the Olivetti daVinci. In 1997, Palm launched the Palm Pilot, and it and its successors proved to be a massive hit. Where countless before it had failed, Palm found the magic formula to make pocket computing work. I wrote an in-depth article about Palm over 13 years ago which goes into much (much) more detail, but the reason the Palm Pilot succeeded where things like the Newton, PenPoint OS, and Windows for Pen Computing failed, is that Palm's founder, Jeff Hawkins, realised that they were competing with paper, not with desktop computers. Instead of trying to shove the capabilities of a full personal computer into a (barely) pockatable device, a pocket computer had to be as fast and convenient as paper, and therefore extremely strict about which features to add, and which to omit. To this day, the entirety of smartphone computing stands on the shoulders of Palm. Palm's ideas, implementations, approaches, paradigms, and even people were absorbed by Apple and Google, where they shaped both iOS and Android. The phone you're looking at right now has a ton of Palm DNA in it, still. After all, you're still using the homescreen-with-apps paradigm Palm already perfected in the late '90s and early 2000s. The success of the Palm Pilot and its successors did not go unnoticed. Microsoft, most prominently, felt incredibly threatened by Palm's success: The success of Palm's products got the attention of Microsoft, and the company pretty much announced it was going to crush Palm. According to Hawkins, Microsoft had a sales conference, where, at some point, a big target appeared on the projector screen, with the Palm logo dead in the centre of it: "we are going to crush and kill these guys", was the central message. Hawkins recalls that he got condolence letters after that, stating things like "Sorry Jeff. Too bad." ↫ Thom Holwerda While Microsoft proved to be unable to "kill and crush" Palm, it did manage to build a relatively successful business selling PDAs running various incarnations of Windows CE. Together, Palm and Microsoft dominated the PDA market pretty much throughout its entire existence, and while the market was a mere fraction of the smartphone market of today, other companies still wanted a piece of this pie too. One of these companies was Olivetti, a storied Italian company with a long history making typewriters, computers, and other electronics. I'm not going into detail about Olivetti's history, but the company was renowned for its attention to design, creating iconic products like the Lexikon 80, Lettera 22, Elea 9003, Programma 101, and so, so many more. Olivetti also entered the personal computer market, first with a variety of custom machines featuring Z80 and later Motorola 68000 processors running a variety of custom operating systems developed by Olivetti (including its own UNIX variant, X/OS). After a few machines using MIPS and Alpha processors in the early '90s, the company would eventually focus entirely on Intel-based PCs (including this amazing failure) running Windows. Like so many other computer makers from that era, Olivetti eventually left the PC business by selling it off in 1997. To this day, Olivetti PCs tend to cost more on the used market than those from other brands, despite no technical merits dictating so. At around this time, our current story begins. Seeing the success of the Palm Pilot and the emergence of copycat devices running Microsoft's Windows CE, Olivetti wanted in on the action. And so, in the late '90s, the company introduced the Olivetti daVinci, a line of PDAs whose software looked suspiciously like Palm OS. There's not a ton of information out there about the development history, but it seems that while Olivetti designed the hardware, it contracted the development of the operating system out to a company from Hong Kong, Echolink Design. And this is where things went horribly wrong for Olivetti. The software Echolink Design developed for the daVinci didn't just look like Palm OS, it was Palm OS - at least, according to Palm. After being on the market for about a year, the Palm Pilot maker, then a subsidiary of 3Com, filed for an injunction, alleging that the daVinci operating system designed by Echolink Design contained actual Palm OS source code. In addition, Palm also filed suit against CompanionLink Software, the company that developed the Outlook synchronisation software for the daVinci. Palm won handily, and within a day of the filing, temporary restraining orders were put in place on both Olivetti and CompanionLink, stopping sales of the daVinci and its software dead in its tracks. It seemed to have been a pretty clear-cut case. From The Wall Street Journal at the time: U.S. District Judge James Ware ruled Olivetti's Royal daVinci organizer contains software that appears to have been copied from the operating system for 3Com's Palm organizers. Judge Ware said a review by a software expert found the daVinci software contains private Palm code and even grammatical

14 Aug 2026 7:18pm GMT

In the last few days, I built a shoot 'em up game by embedding a tiny custom bytecode VM and rendering the graphics using a fullscreen pixel shader. The result is a 3kB Windows executable. This was done for Langjam Gamejam, a 7-day challenge where you create a programming language and then use it to build a game. The project combines several interests of mine: language tooling, game development, procedural graphics, and demoscene-style size constraints. The game jam format forced me to keep the scope small and explore new ideas. Also, it was fun! ↫ Laurent Le Brun In seven days, Le Brun created a brand new programming language, compiler, bytecode interpreter, a game written in the new language, and rendered it, ending up with a 3kB self-contained executable. It's amazing what humans can do.

14 Aug 2026 6:57pm GMT

A while back, when chatting with a colleague over their computer, I noticed that a logo did not look exactly the same as it did on mine. It looked thinner on theirs and more faithful to the original image. It was rendered at 15px; here is an upscaled version. If you squint, or take a step back, the one from Chrome looks thicker. A bit weird, but swapping the image for an SVG fixed it. Still, I was curious: why was it rendering like this in the first place? I did some digging and found a nifty optimization that Chrome uses when rendering JPEGs at small scales. ↫ Guillaume Técher I love it when people detail their discoveries like this.

14 Aug 2026 6:50pm GMT

Another month started almost two weeks ago, so we've got a new monthly report from Redox, the general purpose operating system written in Rust. The month of July - it seems the report was published with a bit of a delay, regardless of what the date on their site says - brought improvements to the installer, with new options commonly found in most installers, such as a choice of installation method, network-based installation, and more. The Google Summer of Code work on the new CPU scheduler has also been merged, including a number of related performance enhancements. There's improvements to the ARM port, Amlogic Meson UART ARM64 support, and uutils grep and sed have been successfully built on Redox, replacing their their GNU counterparts in the os-test test suite. In addition, a whole slew of demos were ported as well, from Ratatui demos to various Iced demos covering things like reading QR codes and processing Markdown. Of course, this is all topped off with the usual long list of lower-level, smaller changes and improvements to the kernel, drivers, Relibc, and more.

12 Aug 2026 11:15pm GMT

The OSNews Fundraiser, to celebrate the fact I posted 20000 stories in 21 years, is still underway. The first major incentive was reached, and I, a long-time Linux user, published my experiences using Windows 11 for a month. It wasn't a success. Keep donating if you want to find out what a Linux user thinks of the current state of macOS! Why support OSNews? I want to make sure I can run OSNews for another two decades and another 20000 posts, and I need your help to do so. Since my wife, who has a tough, underpaid job in elderly care, is largely unable to work due to health reasons caused by that very same job, my income has become a lot more crucial for our kids, my wife, and myself. With OSNews readers being more skeptical of subscription-like things like our Patreon than most people, it's exactly these one-time donations that make up the bulk of your support. Thank you.

12 Aug 2026 6:40pm GMT

Raymond Chen explains what, exactly, the file winstart.bat in Windows 95 is used for. In Windows 95, you could create a winstart.bat file in your Windows directory. During startup, the virtual machine manager initializes and creates the so-called "System virtual machine" (the "System VM"), which is the virtual machine that all Windows programs run in. But before running the user-mode kernel in that virtual machine, the virtual machine manager runs the winstart.bat batch file if it exists. ↫ Raymond Chen Chen needs to use several diagrams to really explain what the batch file is used for, but as a very crude summary, it allows you to load TSRs that only apply to Windows programs, while not affecting any additional DOS command prompts you may load later after Windows is already running. While many think it's a Windows 95 feature, it was already present in Windows 3.x. A unique feature that I doubt many people made active use of.

12 Aug 2026 6:24pm GMT

Delphi is still very much a thing, and still very much in active development. The current stewards of Delphi, Embarcadero, released the Delphi 13 Community Edition today. Delphi Community Edition is a full-featured, free edition of Delphi for building native applications with the Delphi language. It includes a professional IDE, visual designers, integrated compilers and debuggers, the VCL framework for Windows development, and the FireMonkey framework for creating native applications from a shared codebase across Windows, macOS, iOS, and Android. It is designed for students, hobbyists, freelancers, and small teams that meet the Community Edition license requirements. ↫ Marco Cantu at the Embarcadero blog Delphi has been around since 1995, first released for Windows 3.1. It's both a programming language, a variant of Object Pascal, and the accompanying IDE and related tooling and frameworks, originally developed by legendary company Borland. This latest version of course adds a number of new features to the programming language, and further improves the IDE as well, this time with a brand new 64bit version. The two frameworks for visual application development, VCL and FireMonkey, have also been updated and improved. Sadly, it's not open source, and the Community Edition is intended for mostly non-commercial, hobbyist use. If you want to actually earn any money using Delphi, you're going to have to step up to Delphi 13 Florence, which isn't free.

12 Aug 2026 6:14pm GMT

The slow but steady march to the grave for the Android Open Source Project continues. Every few months Google hammers another big nail in the coffin of Android as an open source effort, and I've documented them all here on OSNews (nail, nail, nail, nail, nail), coming to the conclusion long ago that for all intents and purposes, Android is no longer an open source operating system. The latest move, however, is just petty. According to GrapheneOS on , Google has apparently replaced public, instant code downloads for Pixel phone drivers with a manual request form. Instead of publishing code directly to open developer platforms where anyone can grab it, Google now requires developers to fill out a Google Form and wait for someone to send them a Google Drive link. What used to take a couple of hours is now taking weeks. ↫ Hillary Keverenge at Android Authority I'm perhaps misremembering, but I vaguely recall discussions decades ago about what, exactly, it meant to "make source code available", as open source licenses state in a variety of words. Would mailing a paper print-out by classic post satisfy such requirements? Could you write the source code on a brick and throw it through the user's window? Could you hire a church choir to sing it? These are all silly examples, but before everyone had internet access, this was a relevant question. The widespread availability of the internet and software like git solved these issues, which makes it all the more petty that Google now requires an actual application process, waiting times, and Google Drive dumps just to get access to the source code for Pixel drivers. Google is clearly trying to kill whatever's left of the Android Open Source Project's rotting corpse, only barely technically complying with any license requirements only because they're obligated to. The Android team at Google must be a hoot at parties.

11 Aug 2026 10:45pm GMT