OSnews

With the original release of Windows 8, Microsoft also enforced Secure Boot. It's been 15 years since that release, and that means the original 2011 Secure Boot certificates are about to expire. If these certificates are not replaced with new ones, Secure Boot will cease to function - your machine will still boot and operate, but the benefits of Secure Boot are mostly gone, and as newer vulnerabilities are discovered, systems without updated Secure Boot certificates will be increasingly exposed. Microsoft has already been rolling out new certificates through Windows updates, but only for users of supported versions of Windows, which means Windows 11. If you're using Windows 10, without the Extended Security Updates, you won't be getting the new certificates through Windows Update. Even if you use Windows 11, you may need a UEFI update from your laptop or motherboard OEM, assuming they still support your device. For Linux users using Secure Boot, you're probably covered by fwupd, which will update the certificates as part of your system's update program, like KDE's Discover. Of course, you can also use fwupd manually in the terminal, if you'd like. For everyone else not using Secure Boot, none of this will matter and you're going to be just fine. I honestly doubt there will be much fallout from this updating process, but there's always bound to be a few people who fall between the cracks. All we can do is hope whomever is responsible for Secure Boot at Microsoft hasn't started slopcoding yet.

What happens when you slopcode a bunch of bloat to your basic text editor? Well, you add a remote code execution vulnerability to notepad.exe. Improper neutralization of special elements used in a command (command injection') in Windows Notepad App allows an unauthorized attacker to execute code over a network. An attacker could trick a user into clicking a malicious link inside a Markdown file opened in Notepad, causing the application to launch unverified protocols that load and execute remote files. CVE-2026-20841 I don't know how many more obvious examples one needs to understand that Microsoft simply does not care, in any way, shape, or form, about Windows. A lot of people seem very hesitant to accept that with even LinkedIn generating more revenue for Microsoft than Windows, the writing is on the wall. Anyway, the fix has been released through the Microsoft Store.

If you're a developer and use KDE, you're going to be interested in a new feature KDE is working on for KDE Linux. In my last post, I laid out the vision for Kapsule-a container-based extensibility layer for KDE Linux built on top of Incus. The pitch was simple: give users real, persistent development environments without compromising the immutable base system. At the time, it was a functional proof of concept living in my personal namespace. Well, things have moved fast. Herp De Derp Not only is Kapsule now available in KDE Linux, it's also properly integrated with Konsole now. This means you can launch Kapsule containers right from the new tab menu in Konsole for even easier access. They're also working on allowing users to easily launch graphical applications from the containers and have them appear in the host desktop environment, and they intend to make the level of integration with the host more configurable so developers can better tailor their containers to their needs.

Another month, another Redox progress report. January turned out to be a big month for the Rust-based general purpose operating system, as they've cargo and rustc working on Redox. Cargo and rustc are now working on Redox! Thanks to Anhad Singh and his southern-hemisphere Redox Summer of Code project, we are now able to compile your favorite Rust CLI and TUI programs on Redox. Compilers are often one of the most challenging things for a new operating system to support, because of the intensive and somewhat scattershot use of resources. Ribbon and Ron Williams That's not all for January, though. An initial capability-based security infrastructure has been implemented for granular permissions, SSH support has been improved and now works properly for remoting into Redox sessions, and USB input latency has been massively reduced. You can now also add, remove, and change boot parameters in a new text editing environment in the bootloader, and the login manager now has power and keyboard layout menus. January also saw the first commit made entirely from within Redox, which is pretty neat. Of course, there's much more, as well as the usual slew of kernel, relibc, and application bugfixes and small changes.

I'm currently building an 80386-compatible core in SystemVerilog, driven by the original Intel microcode extracted from real 386 silicon. Real mode is now operational in simulation, with more than 10,000 single-instruction test cases passing successfully, and work on protected-mode features is in progress. In the course of this work, corners of the 386 microcode and silicon have been examined in detail; this series documents the resulting findings. In the previous post, we looked at multiplication and division - iterative algorithms that process one bit per cycle. Shifts and rotates are a different story: the 386 has a dedicated barrel shifter that completes an arbitrary multi-bit shift in a single cycle. What's interesting is how the microcode makes one piece of hardware serve all shift and rotate variants - and how the complex rotate-through-carry instructions are handled. nand2mario I understood some of this.

For me, vim is a combination of genuine improvements in vi's core editing behavior (cf), frustrating (to me) bits of trying too hard to be smart (which I mostly disable when I run across them), and an extension mechanism I ignore but people use to make vim into a superintelligent editor with things like LSP integrations. Some of the improvements and additions to vi's core editing may be things that Bill Joy either didn't think of or didn't think were important enough. However, I feel strongly that some or even many of omitted features and differences are a product of the limited environments vi had to operate in. The poster child for this is vi's support of only a single level of undo, which drastically constrains the potential memory requirements (and implementation complexity) of undo, especially since a single editing operation in vi can make sweeping changes across a large file (consider a whole-file :...s/../../' substitution, for example). Chris Siebenmann I have only very limited needs when it comes to command-line text editors, and as such, I absolutely swear by the simplicity of nano. In other words, I'm probably not the right person to dive into the editor debate that's been raging for decades, but reading Siebenmann's points I can't help but agree. In this day and age, defaulting an editor that has only one level of undo is insanity, and I can't imagine doing the kind of complex work people who use command-line editors do while being limited to just one window. As for the debate about operating systems that symlink the vi command to vim or a similar improved variant of vi, I feel like that's the wrong thing to do. Much like how I absolutely despise how macOS hides its UNIX-y file system structure from the GUI, leading to bizarre ls results in the terminal, I don't think you should be tricking users. If a user enters vi, it should launch vi, and not something that kind of looks like vi but isn't. Computers shouldn't be lying to users. If they don't want their users to be using vi, they shouldn't be installing vi in the first place.

Update: we've already hit the 5000 goal, in a little over 24 hours. Considering I thought this would take weeks - assuming we'd hit the goal at all - I'm a bit overwhelmed with all the love and support. Thank you so, so much. Since people are still donating, I upped the goal to 7500 to give people something to donate to. You people are wild. Amazing. It's time for an OSNews fundrasier! This time, it's unplanned due to a financial emergency after our car unexpectedly had to be scrapped (you can find more details below). If you want to support one of the few independent technology news websites left, this is your chance. OSNews is entirely supported by you, our readers, so go to our Ko-Fi and donate to our emergency fundraiser today! Why support OSNews? In short, we are truly independent. After turning off our ads, our Patreons and donors are our sole source of income, and since I know many of you prefer the occasional individual donation over recurring Patreon ones, I run a fundraiser a few times a year to rally the troops, so to speak. This particular fundraiser wasn't planned, however, given the circumstances described below, several readers have urged me to run a fundraiser now. We're incredibly grateful for even having the opportunity to do something like this, and as always, I'd like to stress that OSNews will never be paywalled, and that access to our website will never be predicated on your financial support. You can ignore all of this and continue on reading the site as usual. What's going on? Sadly, and unexpectedly, we've had to scrap our car. Our 2007 Hyundai Santa Fe did not survive this Arctic Winter, as the two decades in the biting cold has taken a toll on a long list of components and parts - it would no longer start. After consulting an expert, we determined that repairs would've been too expensive to make financial sense for such an old vehicle. Sometimes, you have to take the loss lest you throw money down a pit. An unreliable car in an Arctic climate is a really bad idea, since getting stranded on a back road somewhere when it's -30C (or colder) with two toddlers is not going to be a fun time. On top of that, my wife uses our car to commute to work, and while using the bus is going to be fine for a little while, her job in home care for the very elderly and recovering alcoholics is incredibly stressful and intensive. Dealing with bus schedules and wait times at such low temperatures is not exactly compatible with her job. Since she's just recovering from a doctor-mandated rest period - very common in her line of work - her income has taken a hit. Taking professional care of people with severe dementia or other old-age related conditions is a thankless and underpaid job, and it's no surprise those working in this profession often require mandated rest (and thus a temporary pay cut). And so, urged on by readers on Mastodon, I'm doing an OSNews fundraiser to help us pay for the new" car. Of course, we're looking for a used car, not a new one, and based on our needs we've set a budget of around 10,000. This should allow us to buy something like a used Mazda 6 or Volvo V60 from around 2014-2015, or something similar in size and age, with a reasonable petrol engine (an EV is well out of our price range). We consider this the sweet spot for safety features, size, age, longevity, and reliability. We've got some savings, but most of the purchase price will have to come in the form of a car loan. We've already made some changes to our monthly expenses to cover for part of the monthly repayments, including a lucky break where our daycare expenses will be going down considerably next month. Based on this, I've set the fundraising goal at 5000. If we manage to hit that - and the last few times we hit our goals quite fast - it won't cover the entire purchase price, but it will cut down on the amount we need to loan considerably. I'm feeling a little apprehensive about all of this, since this isn't really an OSNews-related expense I can easily get some content out of. However, I'm entirely open to suggestions about how I could get some OSNews content out of this - perhaps buying and installing one of those Android headunits with a large display? They make them tailored for almost every vehicle at low prices on AliExpress, and the installation process and user experience might be something interesting to write about, as it's potentially a great way to add some modern features to an older car. Feel free to make any suggestions. I'm also open to other crazy ideas. If you happen to work at an automaker, and need some testing done in an Arctic environment - including ice roads - I'm open to ideas. A few random notes Since about half of our audience hails from the United States, I figured I'd make a few notes about car pricing in Europe, and in Arctic Sweden in particular. Cars are definitely more expensive here in Europe, doubly so in the sparsely populated area where we live (low supply leads to higher prices). Buying a brand new car is entirely out of the question due to pricing, and leasing is also far too expensive (well over 500/month for even a basic, small car). Used electric cars are still well out of our budget as well, and since we don't have our own driveway, we wouldn't be able to charge at home anyway. Opting to forego a car entirely is sadly not an option either. With two small children, the Arctic climate, the remoteness, my wife's stressful job and commute, and long distances to basic amenities, we can't go Dutch" and live

About a year ago I mentioned that I had rediscovered the Dillo Web Browser. Unlike some of my other hobbies, endeavours, and interests, my appreciation for Dillo has not wavered. I only have a moment to gush today, so I'll cut right to it. Dillo has been plugging along nicely (see the Git forge.) and adding little features. Features that even I, a guy with a blog, can put to use. Here are a few of my favourites. Bobby Hiltz If you're looking for a more minimalist, less distracting browser experience that gives you a ton of interesting UNIXy control, you should really consider giving Dillo a try.

KDE's Nate Graham has published a status update about KDE Linux, the KDE project's new immutable Linux distribution, intended to be the KDE OS" showcasing the best of the KDE community. While the project is approaching the beta stage, it's currently still in alpha, but from what I gather from friends who are using it, the alpha label might actually be like how Haiku is supposedly still alpha: intended more to scare people away for now than ana ctual descriptor of the state of the software. Recently, KDE Linux enabled delta updates, possibly dramatically reducing the size of updates. Before delta updates were enabled, a system update would come in at 7GB, while with delta updates enabled, it's gone down to 1-2GB. In addition, plasma-setup and plasma-login-manager have been added to KDE Linux, which are, respectively, a first-run setup assistant and KDE's new login manager. This new login manager was forked from SDDM, and specifically targets Wayland, and comes with much deeper Plasma integration than SDDM. Note that SDDM will remain available for platforms that don't use Wayland. KDE Linux has also massively improved its hardware support, and the list is long; from scanners to fancy multi-button mice, from Android devices to professional audio devices, and much more. Performance has been improved as well, the boot manager menu will no longer be shown at every boot but only when needed, the wireless regulatory domain is now properly set and managed, and much, much more. I'm keeping an eye on KDE Linux as a possible replacement for my Fedora KDE installations if Fedora ever loses the plot, even if it's an immutable distribution relying on Flatpak. I'm a KDE user, and I want the latest and greatest the KDE community has to offer without going through an distributor.

Cameron Kaiser comes in with another amazing article, this time diving into a unique video titler from Canada, released in 1985. The Super Micro Script was one of several such machines this company made over its lifetime, a stylish self-contained box capable of emitting a 32*16 small or 10*4 large character layer with 64*32 block graphics in eight colours. It could even directly overlay its output over a composite video signal using a built-in genlock, one of the earliest such consumer units to do so. Crack this unit open, however, and you'll find the show controlled by an off-the-shelf Motorola 6800-family microcontroller and a Motorola 6847 VDG video chip, making it a relative of contemporary 1980s home computers that sometimes used nearly exactly the same architecture. More important than that, though, it has socketed EPROMs we can theoretically pull and substitute with our own - though we'll have to figure out why the ROMs look like nonsense, and there's also the small matter of this unit failing to generate a picture. Nevertheless, when we're done, another homegrown Canadian computer will rise and shine. We'll even add a bitbanged serial port and write a MAME emulation driver for it so we can develop software quickly ... after we fix it first. Cameron Kaiser I know I keep repeating myself, but Kaiser's work on so many of these rare and unique systems is not only worthwhile and amazing to read, they're also incredibly valuable from a historical and preservation perspective. This article in hand, anyone who stumbles upon one of these machines can get the most out of it, possibly fix one, and use it for fun projects. I'm incredibly grateful for this sort of work. Video titles are such an interesting relic of the past. These days, adding titles to a video is child's play, but back when computing power came at a massive premium and digital video was but a distant dream, using analog video to overlay text onto was the best way to go about it. Video titler makers did try to move the technology from professional settings to home settings, but from what I can gather, this move never really paid off. Still, I'd love to buy one of these at some point and mess around with it. There's some real cool retro effects you can create with these.

If you use an Apple silicon Mac I'm sure you have been impressed by its performance. Whether you're working with images, audio, video or building software, we've enjoyed a new turn of speed since the M1 on day 1. While most attribute this to their Performance cores, as it goes with the name, much is in truth the result of the unsung Efficiency cores, and how they keep background tasks where they should be. Howard Oakley While both Intel and AMD are making gains on Apple, there's simply no denying the reality that Apple's M series of chips are leading the pack in mobile computing (the picture is different in desktops). There are probably hundreds of reasons why Apple has had this lead for so many years now, but the way macOS distributes background and foreground tasks across the two types of cores in M series chips is an important one. Still, I wonder how the various other processors that use power and efficiency cores fare in this regard. You'd think they would provide a similar level of benefit, but I wouldn't be surprised if the way Windows or Linux handles such cores and the distribution of tasks is simply not as optimised or strict as it is in macOS. Apple often vastly overstates the benefits of its vertical integration", but I think the tight coupling between macOS and Apple's own processors is definitely a case where they're being entirely truthful.

We talked about Nemin's first impressions of the Guix System as someone coming from a Nix environment, but today they've got a follow-up article diving into the experience of creating new packages for Guix. I spent about a week packaging WezTerm and learning the ropes of being a Guix contributor along the way. During the packaging process I stumble many times, only to stand back up and figure out a solution. I also explain some of my complaints about the peculiarities of the process, but also provide plenty of praise about of how much the system tries to enable you to do your job. Finally, I also touch on how positive the experience of the code review was. Nemin's blog These are the kinds of content a rather niche system like Guix needs. Guix isn't exactly one of the popular picks out there, so having level-headed, honest, but well-written introductions to its core concepts and user experience, written by a third party is going to do wonders for people interested in trying it out.

It was only a matter of time before the illegal, erratic, inhumane, and cruel behaviours and policies of the second Trump regime were going to affect the open source world in a possibly very visible way. Christian Hergert, longtime GNOME and Linux contributor, employed by Red Hat, wanted to leave the US with his family and move to Europe, but requests to remain employed by Red Hat were denied. As such, he decided to end his employment at Red Hat and push on with the move. However, without employment, his work on open source software is going to suffer. While at their in-person visa appointment in Seattle, US border patrol goons shot two people in their hometown of Portland, underlining the urgency with which people might want to consider getting out of the US, even if it means losing employment. Regardless, the end result is that quite a bit of user-facing software that millions of people use every day is going to be affected. This move also means a professional shift. For many years, I've dedicated a substantial portion of my time to maintaining and developing key components across the GNOME platform and its surrounding ecosystem. These projects are widely used, including in major Linux distributions and enterprise environments, and they depend on steady, ongoing care. For many years, I've been putting in more than forty hours each week maintaining and advancing this stack. That level of unpaid or ad-hoc effort isn't something I can sustain, and my direct involvement going forward will be very limited. Given how widely this software is used in commercial and enterprise environments, long-term stewardship really needs to be backed by funded, dedicated work rather than spare-time contributions. Christian Hergert The list of projects for which Hergert is effectively the sole maintainer is long, and if you're a Linux user, odds are you're using at least some of them: GNOME's text editor, GNOME's terminal, GNOME's flagship IDE Builder, and tons of lower-level widely-used frameworks and libraries like GtkSourceView, libspelling, libpeas, and countless others. While new maintainers will definitely be found for at least some of these, the disruption will be real and will be felt beyond these projects alone. There's also the possibility that Hergert won't be the only prolific open source contributor seeking to leave the US and thus reducing their contributions, especially if a company like Red Hat makes it a policy not to help its employees trying to flee whatever mess the US is in. Stories like these illustrate so well why the no politics!" crowd is so utterly misguided. Politics governs every aspect of our lives, especially so if you're part of a minority group currently being targeted by the largest and most powerful state apparatus in the world, and pretending to be all three wise monkeys at once is not going to make any of that go away. Even if you're not directly targeted because you're not transgender, you're not brown, you're not an immigrant, or not whatever else they fancy targeting today, the growing tendrils of even an incompetent totalitarian regime will eventually find you and harm you. More so than any other type of software, open source software is made by real humans, and as these totalitarian tendrils keep growing, more and more of these real humans will be affected, no matter how incompetent these tendrils might be. You can't run away and hide from that reality, even if it makes you uncomfortable.

As part of our efforts to use more sovereign digital solutions, the European Commission is preparing an internal communication solution based on the Matrix protocol," the spokesperson told Euractiv. Matrix is an open source, community-developed messaging protocol shepherded by a non-profit that's headquartered in London. It's already widely used for public messengers across Europe, with the French government, German healthcare providers and European armed forces all using tools built on the protocol. Maximilian Henning at Euractiv Right now, most government agencies and institutions in Europe are effectively entirely reliant on Microsoft for their digital infrastructure, and that's not a tenable situation going forward with the Americans being openly hostile towards Europe, up to and including threatening to invade European countries. Europe needs its own digital infrastructure, and opting to build those around open source tools is the obvious way to go. Of course, this isn't an easy process, but two platitudes apply here: Rome wasn't built in a day, and every journey begins with a first step. By opting to use existing open source tools, though, these efforts will have a massive head start, and will hopefully lead to a flurry of increased activity for the open source projects in question. In this particular case it's Matrix, which can surely need some additional work and eyeballs, if my use of the protocol is any indication.

What does it look like when a hardware and software company descends into an obsession with recurring services revenue to please its shareholders? Look no further than Apple, who has turned its Apple News service into a vehicle for scam ads. These fake going out of business ads" have been around for a few years, and even the US Better Business Bureau warns about them, as they take peoples' money then shut down. Does Apple care? Does Taboola care? Does Apple care that Taboola serves ads like this? My guess: no, no, and no. Kirk McElhearn While serving obvious scams to users is already bad enough, the real kicker is that even if you are a paying user of Apple News, you still get served ads, including the scams. Of course, massive corporations like Apple are free too just scam you, since they're effectively immune from any legal consequences, so it's unlikely the scamming will stop as long as it makes line go up. On an entirely unrelated note, OSNews is entirely free of ads, so there's no scams here. OSNews is fully funded by our readers through single donations on Ko-Fi or by becoming a Patreon.

I nominate this for the Most Expected News Of The Decade" award. Today, The Tech Oversight Project published a new report spotlighting newly unsealed documents in the 2026 social media addiction trials. The documents provide smoking-gun evidence that Meta, Google, Snap, and TikTok all purposefully designed their social media products to addict children and teens with no regard for known harms to their wellbeing, and how that mass youth addiction was core to the companies' business models. The documents contain internal discussions among company employees, presentations from internal meetings, expert testimony, and evidence of Big Tech coordination with tech-funded groups, including the National Parent Teachers Association (PTA) and Family Online Safety Institute (FOSI), in attempts to control the narrative in response to concerned parents. The Tech Oversight Project Modern social media companies are not entirely different from tobacco companies. They and everyone else know full well just how dangerous social media is, and how being addicted to it has disastrous consequences for the people involved. Tobacco companies, too, knew how dangerous smoking was decades before the general population was aware, and yet they kept pushing cigarettes, even to kids, deaths be damned. In fact, they're still doing the same thing today with vapes", and we're kind of letting it happen all over again. Social media is directly responsible for genocides, extreme polarisation, the spread of endless amounts of lies causing parents to harm their children, mass generation of child pornography, and much, much more. All of this is not a coincidence, mere side-effects, unintended consequences - social media are designed and optimised specifically to achieve these goals, like cigarettes and now vapes" are designed specifically to be as addictive as possible. The people responsible - social media companies, their executives, their employees - need to face justice, answer for what they've done, and face the legal consequences. Of course, that's not going to happen. Billionaires and their megacorporations are untouchable, too big to fail, too closely tied to especially the current regime in the US. I don't think social media bans for people under 16 are the answer, since they tend to come with onerous and invasive online identity checks and because they cut vulnerable people off from their support networks, but it's clear we need to do something.

Gadgets, desk accessories, widgets - whatever you they were called, they were a must-have feature for various operating systems for a while. Windows in particular has tried making them happen six times, and every time, they failed to really catch on and ended up being killed, only for the company to try again a few years later. Microsoft has been trying to solve the same UX problem since 1997: how to surface live information without making you launch an app. They've shipped six different implementations across nearly 30 years. Each one died from a different fundamental flaw - performance, security, screen space, privacy, engagement. And each death triggered the same reflex: containment. Pavel Osadchuk There's quite a few memories in this article. I never actually used Active Desktop back when it came out, because I seem to remember the channels feature was either not available in The Netherlands or the available channels were American stuff we didn't care about. The sidebar in Vista had a lot of potential, and I did like the feature, but there weren't a lot of great widgets and we hadn't entered the era of omnipresent notifications begging for out attention just yet, so use cases remained elusive. Now Metro, that's where things came together, at least for me. I was en enthusiastic Windows Phone user - I imported two Windows Phone devices from the US to be an early adopter - and I still consider its live tiles with notifications and other useful information to be the most pleasant user interface for a mobile device, bar none. It may have taken Microsoft six tries, but they nailed it with that one, and I'm still sad the Windows Phone user interface lost out to whatever iOS and Android offered. On desktops and laptops, though, it's a different story, and I don't think the Metro tiles concept ever made any sense there. Widgets as they exist in Windows now mostly seem like an annoying distraction, and I've never seen anyone actually use them. Does anyone even keep them enabled at all?

Microsoft Research, in collaboration with various others, has just released LiteBox, a library operating system. LiteBox is a sandboxing library OS that drastically cuts down the interface to the host, thereby reducing attack surface. It focuses on easy interop of various North" shims and South" platforms. LiteBox is designed for usage in both kernel and non-kernel scenarios. LiteBox exposes a Rust-y nix/rustix-inspired North" interface when it is provided a Platform interface at its South". These interfaces allow for a wide variety of use-cases, easily allowing for connection between any of the North-South pairs. LiteBox GitHub Page Suggested use-cases are running unmodified Linux applications on Windows, sandboxing Linux applications on Linux, running OP-TEE applications on Linux, and more. It's written in Rust, and the code is available on GitHub under an MIT license.

Over the past month or so, several enterprising contributors have taken an interest in the zig libc subproject. The idea here is to incrementally delete redundant code, by providing libc functions as Zig standard library wrappers rather than as vendored C source files. In many cases, these functions are one-to-one mappings, such as memcpy or atan2, or trivially wrap a generic function, like strnlen. So far, roughly 250 C source files have been deleted from the Zig repository, with 2032 remaining. With each function that makes the transition, Zig gains independence from third party projects and from the C programming language, compilation speed improves, Zig's installation size is simplified and reduced, and user applications which statically link libc enjoy reduced binary size. Andrew Kelley on the Zig Devlog The goal is to replace all of the musl, wasi-libc, and MinGW-w64 C code bundled in Zig with new Zig code.

Rust is everywhere, and it's no surprise it's also made its way into the lowest levels of certain operating systems and kernels, so it shouldn't be surprising that various operating system developers have to field questions and inquiries about Rust. NetBSD developer Benny Siegert wrote a blog post about this very subject, and in it, details why it's unlikely Rust will find its way into the NetBSD base system and/or the kernel First, NetBSD is famed for its wide architecture and platform support, and Rust would make that a lot more troublesome due to Rust simply not being available on many platforms NetBSD supports. Rust release cycles also aren't compatible with NetBSD, it would draw a lot of dependency code into the base system, and keeping Rust and its compiler toolchain working is a lot of work that falls on the shoulders of a relatively small group of NetBSD developers. Note that while NetBSD does tend to take a more cautious approach to these matters than, say, Linux or FreeBSD, the operating system isn't averse to change on principle. For instance, not only is Lua part of the base system, it's even used in the NetBSD kernel due to its ability to rapidly develop and prototype kernel drivers. In short, while it doesn't seem likely Rust will make it into the NetBSD base system, it's not an impossibility either.

We recently talked about Apple's pre-Mac OS X dabblings in UNIX, but Apple wasn't the only computer and operating system company exploring UNIX alternatives. Microsoft had the rather successful Xenix, Atari had ASV, Sony had NEWS, to name just a very small few. The Amiga, too, wanted in on the UNIX action, and as such, released Amiga UNIX, based on AT&T System V Release 4. The Amiga UNIX website is dedicated to everything you would ever want to know about this operating system. This site is dedicated on preserving Amix's history and sharing information and instructions on what Amix is, how to install it (either on real hardware or in emulation) and what can you do with it. Mainly, it tries to cater to people who wish to run AMIX for whatever reason on their hardware. By documenting experiences with it, it is hoped that subsequent SVR4 junkies will find the way more smooth than it might have been without any guidance at all. For even a relatively experienced modern Unix or GNU/Linux administrator, System V UNIX is sufficiently different to present difficulty in installation and administration. Not so much in moving around between directories, and using common utilities that persist to this day - although many of those are hoary and somewhat forgetful in their retirement - but of doing more in depth tasks and understanding the differences. The Amiga Unix Wiki If you wish to run Amiga UNIX yourself, you'll either have to have one of the original two models sold with it - the 2500UX and 3000UX - or one of the Amigas that meets the minimum requirements. Another option is, of course, emulation, and WinUAE has support for running Amiga UNIX.

After a seemingly endless stream of tone deaf news from Mozilla, we've finally got some good news for Firefox users. As the company's been hinting at for a while on social media now, they've added an AI" kill switch to the latest Firefox nightly release, as well as a set of toggles to disable specific AI" features. You can choose to use some of these and not others. If you don't want to use AI features from Firefox at all, you can turn on the Block AI enhancements toggle. When it's toggled on, you won't see pop-ups or reminders to use existing or upcoming AI features. Once you set your AI preferences in Firefox, they stay in place across updates. You can also change them whenever you want. Ajit Varma at the Mozilla blog I'm particularly enamoured with the specific mention that the setting will remain unaffected by updates. It's incredibly sad that Mozilla even has to mention this, but they have nobody to blame but themselves for that one. None of this is enough to draw me away from Librewolf and back to Firefox, but at least it gives those of us who prefer to keep using Firefox the option to disable all of this AI" nonsense. Also, there's no Librewolf for POWER9, so I have to use Firefox somewhere. It's unlikely Chrome or Safari will get such clear AI" kill switches, so it might become a reason for some to switch to Firefox from Chrome or Safari.

In the late 1980s, with the expansion of the Internet (even though it was not open to commercial activities yet) and the slowly increasing capabilities of workstations, some people started to imagine the unthinkable: that, some day, you may use your computer to record voice messages, send them over the Internet, and the recipient could listen to these messages on his own computer. That was definitely science fiction... until workstation manufacturers started to add audio capabilities to their hardware. Miod Vallat A great story detailing how the audio hardware in the HP 9000/425e was made to work on OpenBSD and NetBSD.

I previously covered x64 OpenVMS release on VMware. This was insanely cool achievement for the operating system. While it had no practical ramification there was one small annoyance. The OS console was on a serial port. In VMware it meant another VM connected via named pipe. Now OpenVMS x64 supports (limited?) local console on OPA0. Virtually Fun I think this has been available for a while now - since 2024 - but we hadn't covered it yet. That same 2024 post also indicates CDE and DECWindows work now, a side effect of a C/C++ compiler bugfix. Sadly, VSI has made it clear that desktop support is not at all on their list of things to spend time on, so don't expect graphics support to improve meaningfully other than by accident like in this case.

But NixOS isn't the only declarative distro out there. In fact GNU forked Nix fairly early and made their own spin called Guix, whose big innovation is that, instead of using the unwieldy Nix-language, it uses Scheme. Specifically Guile Scheme, GNU's sanctioned configuration language. I've been following Guix for a bit, but it never felt quite ready to me with stuff like KDE being only barely supported and a lot of hardware not working out of the box. However, now that (after three years) Guix announced its 1.5.0 release with a lot of stuff stabilized and KDE finally a first-party citizen, I figured now is the best time to give it a fresh shot. This post captures my experiences from installation to the first 3-4 days. Nemin's blog If you're interested in Guix, but aren't quite sure if you want to take the plunge, this article does a great job of showing you the ropes, listing what issues you might run into, some pitfalls to avoid, and so on.

It's no secret that Windows 11 isn't exactly well-liked by even most of its users, and I'm fairly sure that perception has permeated into the general public as well. It seems Microsoft is finally getting the message, and they're clearly spooked: the company has told The Verge that they have heard the complaints, and intend to start fixing many of the issues people are having. The feedback we're receiving from our community of passionate customers and Windows Insiders has been clear. We need to improve Windows in ways that are meaningful for people. This year, you will see us focus on addressing pain points we hear consistently from customers: improving system performance, reliability, and the overall experience of Windows. Pavan Davuluri, head of Windows, to The Verge This entire statement is utterly meaningless. I have zero faith in words; only actions will do. Microsoft has made many promises over the years, and they have a history of simply not following through on them. Up until this year is over and there have been material improvements in Windows 11 that we can measure, see, and point to, nothing has changed between the day before the statement and the day after. Anyone taking this at face value and reporting it as such is an idiot. This means that at the end of this year, Windows 11 should be faster, more stable, experience far fewer breaking updates, have fewer - nay - zero ads, a far more consistent user interface, proper local account support, and more. If these things haven't become reality once the countdown runs out and on 31 December, Microsoft lied to our faces once more. Until then, don't use Windows.

Operating systems written in Rust - especially for embedded use - are quite common these days, and today's example fits right into that trend. Ariel OS is an operating system for secure, memory-safe, low-power Internet of Things (IoT). It is based on Rust from the ground up and supports hardware based on 32-bit microcontroller architectures (Cortex-M, RISC-V, and Xtensa). For a quick overview of our motivations and what we plan next, check our roadmap. Ariel OS builds on top of existing projects from the Embedded Rust ecosystem, including Embassy, esp-hal, defmt, probe-rs, sequential-storage, and embedded-test. While those provide high-quality building blocks for a wide range of embedded applications, such projects do not provide the high level of integration that developers know from contemporary C-based operating systems for microcontrollers, such as RIOT or Zephyr for instance. Ariel OS GitHub page There's bound to be a microcontroller you can get your hands on that Ariel OS supports, and since it's licensed under either a MIT or Apache 2.0 license, you can get going right away.

As most of you will know, Mac OS X (or Rhapsody if you count the developer releases) wasn't Apple's first foray into the world of UNIX. The company sold its own UNIX variant, A/UX, from 1988 to 1995, which combined a System V-based UNIX with a System 7.0.1 desktop environment and application compatibility, before it acquired NeXT and started working on Rhapsody/Mac OS X. As a sidenote, I don't know if the application compatibility layer was related to the Macintosh Application Environment for UNIX, which I have running on my HP-UX machines. That's not the only time Apple dabbled with UNIX, though - Apple's unique Apple Network Server product from 1996 also came with UNIX, but time it wasn't one from Apple itself, but rather from its enemy-turned-friend IBM: AIX. The Network Server shipped with a slightly customised version of IBM's AIX operating system; regular AIX straight from IBM wouldn't work. The more things change, the more they stay the same I guess. Since the Apple Network Server was built around a modified Power Macintosh 9500 - there's much more to the hardware, but that's the short of it - so you would expect the Network Server to also be able to run regular Mac OS for PowerPC, right? Apple even sold server products running plain Mac OS at the time, so it'd make sense, but nothing about Apple in the '90s made any sense whatsoever, so no, use of plain Mac OS was locked out through the ROM. And let's not even get started about other PowerPC operating systems of the time, like, of all things, Windows NT - something Apple supposedly demonstrated at some point. But was that always the case? Well, we've got new ROMs straight from a former Apple employee, and after flashing them to a supported ROM chip, the Apple Network Sever can now run classic Mac OS. On top of that, and even more miraculous, the Windows NT-capable ROMs have also been discovered. I'll give you a spoiler now: it turns out the NT ROM isn't enough to install Windows NT by itself, even though it has some interesting attributes. Sadly this was not unexpected. But the pre-production ROM does work to boot Mac OS, albeit with apparent bugs and an injection of extra hardware. Let's get the 700 running again (call it a Refurb Weekend) and show the process. Cameron Kaiser While it's great news to see that Mac OS can now be run on the Network Server, I'm personally much more interested in the story behind the Windows NT ROMs. The idea that Apple would sell a computer running Windows NT out of the box is wild to think about now, but considering the desperate state the company was in at the time, all options must've been on the table. Sadly, as Kaiser discovered, the Windows NT ROMs in and of themselves are not enough to run Windows NT. However, they appear to be much farther along in the development process than even the Mac OS-capable ROMs, which is fascinating. When Jobs talked Gil Amelio into canning the ANS as well, the ROM initiative naturally went out the window with it. However, while the existing 2.0 Mac OS ROMs are only known on an unmarked development flash stick similar to mine, these final 2.26NT ROMs appear almost production-ready with fully printed labels, suggesting they had reached a very late stage of development. Cameron Kaiser Despite not being able to boot Windows NT for PowerPC as-is, most likely because there's no compatible ARC or HAL, Kaiser did discover a ton of interesting details, like how this ROM configures the Network Server to run in little endian mode, which is all Windows NT for PowerPC ever supported, making this the very first time a PowerPC machine did so. I'm hoping Kaiser manages to track down the necessary components to make Windows NT bootable on the ANS, as one of the most unique curiosities in Apple history. There's a ton more details in the article, as per usual Kaiser standards, and it's an absolute joy to read.

While the two major open source desktop environments get most of the airtime - and for good reason, since they're both exceptionally good - there's a long tail of other desktop environments out there catering to all kinds of special workflows and weird niches. I think we can all agree that Xfce leads this long tail of more niche desktop environments, without really being niche itself. Xfce may not be as popular as KDE or GNOME, but it's an amazing full-featured desktop environment that offers a slightly more traditional, less fast-paced desktop for those that desire so. Xfce, too, is moving to Wayland, which can mean significant efforts in certain places, not the least of which is the window manager. Xfce originally planned to adapt its venerable xfwm4 to support both X11 and Wayland at the same time, but this turned out to be too complex for a variety of reasons, all more or less caused by differences between X11 and Wayland. On top of that, this approach would risk introducing new bugs to the X11 side of things, and the Xfce project does not want to subject its X11 users to that. As such, they've decided to develop a Wayland compositor from scratch: xfwl4. The goal is, that xfwl4 will offer the same functionality and behavior as xfwm4 does, or as much as possible considering the differences between X11 and Wayland. Using xfwl4 should feel just like using xfwm4 on X11. We even plan to reuse the existing xfwm4 configuration dialogs and xfconf settings to ensure a seamless transition. Xfwl4 will not be based on the existing xfwm4 code. Instead, it will be written from scratch in rust, using smithay building blocks. The Xfce development team This project also includes related tasks like rearchitecting session-startup to support Wayland, implementing support for the xdg-session-management protocol, and adding support for XWayland. This is obviously anything but a small effort, but it seems like a practical solution. Xfce users generally seem to choose Xfce exactly because it's a stable environment that does not move fast(er) and break (some) things. As such, keeping the X11 window manager separate and stable, without Wayland work possibly breaking it, seems like the kind of thing the average Xfce user can get behind. Personally, I can't wait for Xfce to become a full Wayland desktop, as dealing with X11's nonsense feels decidedly retro to me now, and I don't see Xfce as a retro environment at all. It's going to take some time, of course, but thanks to countless generous donations to Xfce, longtime Xfce core developer Brian Tarricone will be paid to work on this project. Excellent news for everyone involved.

Since I have no qualms about kicking a proprietary software product while it's down, let's now switch to NTDEVs thoughts on the state of Windows 11. Unfortunately, the issue that plagued Windows since the dawn of time has only aggravated recently. Windows 11 is a mixture of old and new technologies that are glued together, with decades of legacy code that simply refuses to die (because if it did a lot of corporate costumers would complain, and whether we like it or not they are paying big cash for support to Microsoft). Also, it tries to have a modern" UI that unfortunately not only is inconsistent, but also it's too heavy for its own good, being just a lipstick on a bloated old pig. Last, but certainly not least, it is full of AI features that most people didn't ask for, some are even actively feared (see Recall) and are also quite lacking in polish and usefulness. Until Microsoft stops treating Windows as an AI innovation platform" of sorts and starts treating it as the stable, reliable tool it was always meant to be, the user experience will continue to feel like a battle between the person sitting at the desk and the company that built the desk. NETDEV When even some of the most knowledgeable and respected Windows/Windows NT developers and experts are this down on the current state of Windows, you know things are way worse than we even know from just following the news and our own experiences. Back in 2024, I stated that I firmly believe we will see Windows - or at least, huge, crucial chunks of it - shift to an open source development model, as it's the only way for Windows to move forward without crumbling into itself. It would also be a massive cost-cutting and personnel-culling step for Microsoft, something that seems to become ever more relevant now that the company bet massively on AI", without any of it paying off. They're going to need to do some serious cost-cutting once the AI" bubble bursts, and Windows will definitely be the first on the chopping block. As a side note, the step to release Windows as open source won't be nearly as difficult or problematic as people think. In fact, Microsoft has provided access to the source code behind Windows and various other products for decades, and countless governments and organisations have access to said source code. On top of that, the source code to Windows XP and Server 2003 is out there, hosted on GitHub, and various other leaks have occurred as well over the years. While I'm sure a large clean-up effort would still be required, and while it surely will be a big engineering effort, if there were any truly shocking things in the code Microsoft wouldn't want the world to see we'd already know by now. I'm getting the strong feeling Microsoft is trying to squeeze every last drop of revenue out of Windows before it ends up on the chopping block. Windows will definitely not be axed, but cost-cutting is inevitable.

I've been terribly sick for a few days so we've got some catching up to. Let's first take a look at how Windows is doing. People often say Linux is too much work." And I agree. They're completely justified to complain. There's the documentation page diving, the forums, the reddit threads. And, most importantly, you have to basically rewire your brain and stop expecting it to behave like Windows used to. But I looked at the list above and realized: Windows is now also too much work. And the difference with Windows is that you're going to do all that work while actively fighting your computer only for it to be undone when the next surprise update comes and ruins everything. You might be thinking just disable updates, man" or just install LTSC", or just run some random debloat script off of GitHub". Why? Why would I jump through all these hoops? I'd rather put in the effort for an OS that knows what consent is and respects me as a user. Bogdan-Mihai Mosteanu You know how in most theme parks they have various different rides for all kinds of people? There's the wild and crazy over-the-top deathcoasters for the ultimate thrill seekers, the more gentle wooden coasters for those who like a thrill, but not over-the-top. There's the swinging ship-type things for thrill-seeking accountants who seek their thrills predictably. There's a game of Russian roulette played in the backlot. For the kids, there's the classic spinning tea cups. And then there's the public transport service dressed up as an old-timey steam train that just brings you to your destination without any issue, silently doing its thing, the unsung backbone of park logistics. Commercial operating systems like Windows and macOS are the games of Russian roulette, predictably unexpectedly shooting you in the face every sixth time you pull the trigger. That's not my vibe. I want my operating system to be that steam train, and desktop Linux is the only thing that fits that bill - and it's very clear more and more people are discovering that too.

9front, by far the best operating system in the whole world, pushed out a new release, titled GEFS SERVICE PACK 1. Even with only a few changes, this is still, as always, a more monumental, important, and groundbreaking release than any other operating system release in history. Everything changes, today, because exec() now supports shell-scripts as interpreter in #!, improved sam scrolling, TLS by default in ircrc, and more. You're already running 9front, of course, but if you're one of the few holdouts still using something else, download GEFS SERVICE PACK 1 and install it.

Your mission, should you choose to accept it, is to sneak into the earliest parts of the boot process, swap the startup config without breaking anything, and leave without a trace. Are you ready? Let's begin. Jynn Nelson Genius.

Encrypting the data stored locally on your hard drives is generally a good idea, specifically if you have use a laptop and take it with you a lot and thieves might get a hold of it. This issue becomes even more pressing if you carry sensitive data as a dissident or whistleblower and have to deal with law enforcement. Or, you know, if you're an American citizen fascist paramilitary groups like ICE doesn't like because your skin colour is too brown or whatever. Windows offers local disk encryption too, in the form of its BitLocker feature, and Microsoft suggests users store their encryption keys on Microsoft's servers. However, when you do so, these keys will be stored unencrypted, and it turns out Microsoft will happily hand them over to law enforcement. This is private data on a private computer and they made the architectural choice to hold access to that data. They absolutely should be treating it like something that belongs to the user," said Matt Green, cryptography expert and associate professor at the Johns Hopkins University Information Security Institute. If Apple can do it, if Google can do it, then Microsoft can do it. Microsoft is the only company that's not doing this," he added. It's a little weird... The lesson here is that if you have access to keys, eventually law enforcement is going to come." Thomas Brewster Microsoft is choosing to store these keys in unencrypted fashion, and that of course means law enforcement is going to come knocking. With everything that's happening in the United States at the moment, the platitude of I have nothing to hide" has lost even more of its meaning, as people - even toddlers - are being snatched from the streets and out of their homes on a daily basis by fascist paramilitaries. Even if times were better, though, Microsoft should still refrain from storing these keys unencrypted. It is entirely possible, nay, trivial to address this shortcoming, but the odds of the company fixing this while trying to suck up to the current US regime seem small. Everybody, but especially those living under totalitarian(-esque) regimes, should be taking extra care to make sure their data isn't just encrypted, but that the keys are safe as well.

Last year brought a wealth of new features and fixes to Firefox on Linux. Besides numerous improvements and bug fixes, I want to highlight some major achievements: HDR video playback support, reworked rendering for fractionally scaled displays, and asynchronous rendering implementation. All this progress was enabled by advances in the Wayland compositor ecosystem, with new features implemented by Mutter and KWin. Martin Stransky It's amazing how the adoption of Wayland is making it so much easier for application developers to support modern features like these. Instead of having to settle for whatever roadblocks and limitations thrown up by legacy X11 cruft, the Linux desktop can now enjoy modern features like HDR, and much more easily support features like fractional scaling. The move to Wayland, as long as it may have taken, has catapulted the Linux desktop from its '90s roots right into the modern era. It's great to see Firefox implementing improvements like these for Linux users, but of course, they come with Mozilla's push to make Firefox an AI" browser, something few Firefox users seem to want. Luckily, the various Firefox variants like Librewolf and Waterfox will get these same features while removing all the AI" bloat, so as long as Mozilla remains committed to Firefox for Linux - or Firefox in general - Linux users can rest safe. Sadly, I'm afraid Mozilla's massive pivot to AI" isn't going to work out, so I have no idea how long Mozilla will be able to afford Firefox on Linux development specifically, and Firefox development generally.

Developing for Windows seems to be a bit of a nightmare, at least according to Microsoft, so they're trying to make the lives of developers easier with a new tool called winapp. The winapp CLI is specifically tailored for cross-platform frameworks and developers working outside of Visual Studio or MSBuild. Whether you are a web developer building with Electron, a C++ veteran using CMake, or a .NET, Rust or Dart developer building apps for Windows, the CLI can streamline the complexities of Windows development - from setting up your environment to packaging for distribution. This makes it significantly easier to access modern APIs - including Windows AI APIs, security features and shell integrations - directly from any toolchain. Windows development often involves managing multiple SDKs, creating and editing multiple manifests, generating certificates and navigating intricate packaging requirements. The goal of this project is to unify these tasks into a single CLI, letting you focus on building great apps rather than fighting with configuration. While the CLI is still in its early days, and there are many Windows development scenarios still in the works, we're sharing this public preview now to learn from real usage, gather feedback and feature requests, and focus our investments on the areas that matter most to developers. Nikola Metulev at the Windows Blogs For instance, run the command winapp init at the root of your project, and winapp will download the proper SDKs, create manifest files, etc., all automatically. You can also generate the correct certificates, easily create MSIX packages, and more. The tool is available through winget and npm (for Electron projects), but is still in preview, with the code available on GitHub.

So Markdown is this Lightweight Markup Language. Everyone (relative; among programmers, writers, and other power-users") uses it. LLMs use it. So it's destined to eat the world. But it doesn't mean Markdown is good. Artyom Bologov We have these crazy fast and complex computers, but I'm still supposed to style text with obscure, arbitrary symbols, like an animal? We invented WYSIWYG decades ago, and our computers should be able to figure out how to properly share styled/unstyled text without us users having to learn markup languages using arcane symbols that require weird claw grips to type. The widespread use of Markdown is not indicative of its merits; it merely underlines the utter failure of the computing industry to fix basic problems.

ReactOS is celebrating its 30th birthday. Happy Birthday ReactOS! Today marks 30 years since the first commit to the ReactOS source tree. It's been such a long journey that many of our contributors today, including myself, were not alive during this event. Yet our mission to deliver your favorite Windows apps and drivers in an open-source environment you can trust" continues to bring people together. Let's take a brief look at some of the high and low points throughout our history. Carl Bialorucki at the ReactOS website OSNews has been following ReactOS since about 2002 or so (the oldest reference I could find, but note that our 1997-2001 content isn't available online, so we may have mentioned it earlier), so you can definitely say we all grew up alongside ReactOS' growth and development. All of the events the team mentions in their retrospective on 30 years of ReactOS were covered here on OSNews as well, which is wild to think about. Personally, I don't really know how to feel about the project. On the one hand, I absolutely adore that dedicated, skilled, and talented individuals dedicate their precious free time to something as ambitious as creating a Windows NT-compatible operating system, and there's no denying they've achieved incredible feats of engineering few people in the world are capable of. ReactOS is a hobby operating system that survived the test of time where few others have - AtheOS, Syllable, SkyOS , and so many others mentioned in that oldest reference I linked to are long dead and gone - and that alone makes it a massively successful project. On the other hand, its sheer ambition is also what holds the project down. If you say you're going to offer a Windows NT-compatible operating system, you set expectations so insanely high you'll never even come close to meeting them. Every time I've seen someone try ReactOS, either in writing or on YouTube, they always seem to come away disappointed - not because ReactOS isn't impressive, but because it's inevitably so far removed from its ambitious goals. And that's a real shame. If you take away that ambitious goal of being Windows NT-compatible, and just focus on what they've already achieved as it stands now, there's a really impressive and fun alternative operating system here. I really hope the next 30 years will be kind to ReactOS.

If you have any interest in SGI's IRIX or used IRIX back when it was still current, you're undoubtedly aware of Nekoware, a collection of freeware for IRIX, maintained and kept up-to-date as much as possible. After stagnating in 2015 and a few failed restarts and some infighting (apparently), the project finally relaunched somewhere last year, and a new quarterly release was pushed out. Nekoware 2025Q4 is a clean break from previous releases, and requires that users fully remove any traces of previous installations. It contains the kinds of packages these freeware/open source collections for classic UNIX tended to contain: tons of common open source libraries, command-line tools, and more, including a few emulators. You'll need IRIX 6.5.21 or newer, running on at least a MIPS R5000 processor-equipped SGI machine. Planning for and work on the next release is already underway, and a brand new Nekoware SDK has been released as well, which provides bootstrap functionality and addresses the problem of having to build Nekoware on unstable IRIX environments. Seeing Nekoware resurrected is great news for the surprisingly active IRIX community. As a HP-UX user, I feel some envy.

In January 1976, MOS Technologies presented a demonstration computer for their recently developed 6502 processor. MOS, which was acquired by Commodore later that year, needed to show the public what their low-cost processor was able to. The KIM-1 single board computer came fully assembled with an input keypad, a six-digit LED display, and complete documentation. It was intended for developers, but it turned out that at a price of only $249 the computer was the ideal playground for hobbyists, who could now afford a complete computer. The unforgettable Jim Butterfield described it like this back in 1999: But suddenly there was the KIM-1. It was fully assembled (although you had to add a power supply). Everybody's KIM-1 was essentially the same (although the CPU added an extra instruction during the KIM-1's production life). And this created something that was never before part of the home computer phenomenon: users could quite happily exchange programs with each other; magazines could publish such programs; and people could talk about a known system. We knew the 6502 chip was great, but it took quite a while to convince the majority of computer hobbyists. MOS Technology offered this CPU at a price that was a fraction of what the other available chips cost. We faced the attitude that it must be no good because it's too cheap," even though the 6502, with its pipelined architecture, outperformed the 8080 and the 6800." Jim Butterfield Even though there would soon be better equipped and faster home computers (mostly based on the 6502) and the KIM-1 vanished from the collective minds, the home computer revolution started 50 years ago in Jan 1976. Hans Otten keeps the memory alive on his homepage, where you can find a full collection of information about single-board computers and especially the KIM-1.

Howard Oakley answers a very interesting question - is it possible to slim macOS down by turning off unneeded services and similar tricks? The answer is obviously no, you cannot. Classic Mac OS was more modular, with optional installs that the user could pick and choose, as shown above in Mac OS 9.1. These days with the SSV, choice is more limited from the start, with the only real options being whether to install the cryptexes used in AI, and the x86 code translator Rosetta 2. The latter is transient, though, and likely to go away next year. Like it or not, modern macOS isn't designed or implemented to give the user much choice in which processes it runs, and architectural features including the SSV and DAS-CTS prevent you from paring its processes down to any significant degree. Howard Oakley That's because macOS is not about creating the best experience for the user, but about creating the most value for shareholders. Giving users choice, allowing them to modify their operating system to suit their needs, removing unneeded components or replacing them with competing alternatives just isn't in the interest of shareholders, and thus, it's not allowed by Apple. That's exactly why they're fighting the EU's very basic and simple consumer protection legislation tooth and nail with lies and propaganda, while giving Trump millions of dollars and silly plaques in bribes. You're as much a user of macOS as a passenger on a ferry is its captain. If you just want to get from Harwich to Hoek van Holland, that's a fine arrangement, but if you want to explore beyond the bounds of the path laid out by those more wealthy than you, you're going to have to leave macOS behind and find a different ship.

The 9020 is a fascinating system, exemplary of so many of the challenges and excitement of the birth of the modern computer. On the one hand, a 9020 is a sophisticated, fault-tolerant, high-performance computer system with impressive diagnostic capabilities and remarkably dynamic resource allocation. On the other hand, a 9020 is just six to seven S/360 computers married to each other with a vibe that is more duct tape and bailing wire than aerospace aluminum and titanium. J. B. Crawford I was hooked from beginning to end. An absolutely exceptional article.

I totally forgot you could do this, but back in the Windows 9x days, you could hold down shift while clicking restart, and it would perform a sort-of soft" restart without going through a complete reboot cycle. What's going on here? The behavior you're seeing is the result of passing the EW_RESTARTWINDOWS flag to the old 16-bit ExitWindows function. What happens is that the 16-bit Windows kernel shuts down, and then the 32-bit virtual memory manager shuts down, and the CPU is put back into real mode, and control returns to win.com with a special signal that means Can you start protected mode Windows again for me?" The code in win.com prints the Please wait while Windows restarts..." message, and then tries to get the system back into the same state that it was in back when win.com had been freshly-launched. Raymond Chen There's a whole lot more involved behind the curtains, of course, and if conditions aren't right, the system will still perform a full reboot cycle. Chen further notes that because WIN.COM was written in assembly, getting back to that freshly-launched" state wasn't always easy to achieve. I only vaguely remember you could hold down shift and get a faster reboot", but I don't remember ever really using it. I've been digging around in my memories since I saw this story yesterday, and I just can't think of a scenario where I would've realised in time that I could do this.

Xous is a microkernel operating system designed for medium embedded systems with clear separation of processes. Nearly everything is implemented in userspace, where message passing forms the basic communications primitive. Xous website It's written in Rust, and it's been around for a while - so much so it's sponsored by NLnet and the EU. The Xous Book provides a ton more details and information, with a strong focus on the kernel. You can run Xous in hosted mode on Linux, Windows, or macOS, inside the Renode emulator, or on the one supported hardware device, the Precursor. Obviously, the code's open and on GitHub (which they should really be moving to a European solution now that the Americans are threatening the EU with war over Greenland).

Have you noticed how it seems like how the light mode" of your graphical user interface of choice is getting lighter over time? It turns out you're not crazy, and at least for macOS, light mode has indeed been getting lighter. You can clearly see that the brightness of the UI has been steadily increasing for the last 16 years. The upper line is the default mode/light mode, the lower line is dark mode. When I started using MacOS in 2012, I was running Snow Leopard, the windows had an average brightness of 71%. Since then they've steadily increased so that in MacOS Tahoe, they're at a full 100%. Will Richardson While this particular post only covers macOS, I wouldn't be surprised to discover similar findings in Windows, GNOME, and KDE. The benefit of using KDE is that it's at least relatively easy to switch colour schemes or themes, but changing colours in Windows is becoming a hidden feature, and GNOME doesn't support it out of the box at all, and let's not even get started about macOS. I think light mode" should be grey mode", and definitely lament the lack of supported, maintained grey modes" in both KDE and GNOME. There's a reason that graphical user interfaces in the era of extensive science-based human-computer interaction research opted for soft, gentle greys (ooh, aah, mmm), and I'm convinced we need to bring it back. The glaring whites we use today are cold and clinical, and feel unpleasant to the point where I turn down the brightness of my monitor in a way that makes other colours feel too muted. Or perhaps I'm out of touch.

If only it was that simple - cue the rollercoaster ride. What an absolutely garish state of affairs lies behind this simple radio button on a website. I'm also well aware OSNews has a certain amount of complexity it might not need, and while I can't fix that, I am at least working on a potential solution.

I'm not particularly interested in photo editing or management, professional or not, but one thing I do know is that many people who are miss one application in particular: Aperture. Discontinued over a decade ago, people still lament its loss, and Daniel Kennett explains to us layman why that's the case. Aperture's technical brilliance is remarkable in how quiet it is. There's no BEHOLD RAINBOW SPARKLE ANIMATIONS WHILE THE AI MAKES AUNT JANICE LOOK LIKE AN ANTHROPOMORPHISED CARROT, just an understated dedication to making the tool you're using work for you in exactly the way you want to work. It's the kind of monumental engineering effort that the user is unlikely to ever notice, simply because of how obvious it is to use - if I want to zoom in to this photo, I point at it with the zoom thing. Duh. Sure, it's a tiny thumbnail inside a small thumbnail of a page in a book... but how else would it work? And that is why Aperture was so special. It was powered by some of the most impressive technology around at the time, but you'd never even know it because you were too busy getting shit done. Daniel Kennett I half-expected to get some wishy-washy vibes-based article about some professional photo management tool, but instead, I came away easily and clearly understanding what made Aperture such a great tool. Beng able to access any set of tools wherever you are, without having to take a photo to a certain specific place in the user interface makes perfect sense to me, and the given counterexample from the modern Photos application instantly feels cumbersome and grating. At this point it's clear Aperture's never coming back, but I'm rather surprised nobody seems to have taken the effort to clone it. It seems there's a market out there for something like this, but from what I gather Lightroom isn't what Aperture fans are looking for, and any other alternatives are simply too limited or unpolished. There's a market here, for sure. What other alternatives to Aperture exist today?

There's cursed computing, and then there's cursed computing. It turns out that you can render GNOME's windows with the compositor from Windows 7, dwm.exe. Yes. tl;dr of how this clusterfuck works: this is effectively just x11 forwarding an x server from windows to linux. the fun part is a) making gnome run with an already existing window manager (namely dwm.exe lol), b) making gnome run over x11 forwarding (it is Not a fan, last time it tried running gnome on windows this is what broke it and made it quit trying), and c) actually ripping out parts of the gnome compositor again to make dwm instead of gnome render window decorations to achieve aero gnome -49016 at Mastodon This is already one of the most cursed things I've ever seen, but then things got so much worse. How about Windows 7's dwm.exe, but composited by GNOME? I need an adult.

Virtualisation is a lot older than you might think, with (one of?) the first implementation(s) being IBM's VM/CMS, the line of operating systems that would grow to include things like System/370, System/390, all the way up until IBM/Z, which is still being developed and sold today; only recently IBM released the IBM z17 and z/OS 3.2, after all. The VM series of operating systems is designed exclusively for mainframes, and works by giving every user their own dedicated virtual machine running on top of the Control Program, the hypervisor. Inside this virtual machine the user can run a wide variety of operating systems, from the simple, single-user classics like IBM's Conversational Monitor System, to more complex systems like Linux or AIX. Early versions of VM were released as open source and are now in the public domain, and enthusiasts have continued to build upon it and expand it, with the latest incarnations being the VM/370 Community Edition releases. They contain the Control Program and Conversational Monitor System, augmented by various fixes, improvements, and other additions. You can run VM in an emulator like Hercules, and continue on from there - but what, exactly, can you do with it? That's where Fun things to do with your VM/370 machine comes in. This article will give you an introduction to the system, and a number of first and later steps you can take while exploring this probably alien environment. If you've always dreamt of using an early IBM mainframe, this is probably the easiest way to do so, because buying one is a really, really bad idea.

ChaosBSD is a fork of FreeBSD. It exists because upstream cannot, and should not, accept broken drivers, half-working hardware, vendor trash, or speculative hacks. We can. ChaosBSD GitHub page This is an excellent approach to testing drivers that simply aren't even remotely ready to be included in FreeBSD-proper. It should be obvious that this is not, in any way, meant to be used as a production operating system, as it will contain things that are broken and incomplete on purpose. The name's also pretty great.