16 Nov 2026

feedSlashdot

Microsoft Blames Monster Email Outage On Software Defect Introduced In July Fix

Microsoft says last week's massive Microsoft 365 outage was caused by a software defect introduced in a July update that remained dormant until a Teams failover and a simultaneous 14% reduction in gateway capacity triggered a cascading failure. More than 80% of the affected gateway servers became unresponsive at the outage's worst point, and because the months-old change could not simply be rolled back, engineers spent roughly 15 hours developing and deploying a patch that restored the previous code path. The Register reports: According to a preliminary post incident report published by Microsoft on November 15, the defect was introduced in July 2026. The update looked fine at the time, Microsoft says, having passed load testing and been deployed without any impact. However, the testing wasn't good enough. Microsoft's report states: "Our load testing tended to focus on weaker hardware with fewer cores." The defect caused "lock contention inside an internal Windows process which caused the machine's resources (CPU & memory) to be exhausted." "The contention issue is worsened on machines with more cores and newer hardware." The fix containing the defect was prepared specifically for Microsoft 365 network gateway servers. Then two things happened at once. Teams failed over to the "primary" gateway that supports Exchange Online, creating a surge in load that was not, in itself, particularly unusual. At the same time, almost 14 percent of server capacity for the networking gateway was out of service, which wasn't a problem by itself either: it was on its way to being restored and, according to Microsoft, "the service had sufficient capacity headroom." Together, they pushed the gateway into the defect and chaos ensued. It was a classic cascading failure scenario. When a server loses connectivity, traffic gets routed to the next healthy endpoint. Which encountered the same problem. So traffic was rerouted again and... you can see where this was going. Within two hours, the defect was encountered across Microsoft's fleet. "At its lowest," the report states, "more than 80 percent of servers were unresponsive." So, what to do? Bringing servers back to service didn't help -- they were immediately overwhelmed and fell over again. "Our normally automated recovery processes were not designed to restore service from this broad unresponsive state." A straightforward rollback was also not possible because the defect was months old. Instead, engineers developed patch for the patch or, in Microsoft's words, "an update that returned the code path to the previously known good state in Windows." The patch was applied to groups of servers and service was gradually restored.

Read more of this story at Slashdot.

16 Nov 2026 4:30pm GMT

AI-Assisted Coders Run Windows on iPhone Duo, Build a Floppy Disk-Based AI Chatbot for MS-DOS

The blog XDA Developers reports that a Claude enthusiast used the AI assistant to make a language model that runs off a floppy disk. "And you can stick it on a DOS computer to boot." The language models "runs at a respectable speed, given that it's running off a CPU that was designed decades before LLMs were even a thing." Over on the ClaudeAI subreddit, user wollymonjak showed off this really impressive feat... [I]t's not going to be a particularly powerful AI; in fact, wollymonjak notes that if you ask something too complex or too long, it starts spitting out nonsense. But who cares about that when you're using a language model on DOS? The same blog also notes that "the iPhone Duo hasn't been out for too long, and someone has already gotten Windows 11 on it." As spotted by TechSpot, this cool feat was performed by Ammaar Reshi over on X. Their project is called WindowsiOS, and its goal is to get Windows 11 running on an iPhone Duo without jailbreaking. Usually, when we cover a project coded up by AI, Claude is the one that called the shots; this time, Reshi opted to use Gemini 4 Carbon, Google's flagship model.

Read more of this story at Slashdot.

16 Nov 2026 12:34pm GMT

Purism Announces 'Librem 5 v2' Linux Phone with RISC-V SoC

From the Linux-news blog OMG Ubuntu: Purism is crowdfunding a new version of its Librem 5 Linux smartphone, this one powered by RISC-V rather than Arm. Librem 5 v2 will use an octa-core SpacemiT K1 RISC-V SoC, replacing the quad-core Arm64 NXP CPU. This processor shift will provide better performance and longer battery life than the original Librem 5 and not run as hot in use. Memory is bumped to 8 GB RAM, up from 3 GB, and storage leaps to 128 GB from 32 GB. Librem 5 v2 will run PureOS, Purism's Debian-based operating system using Phosh as its UI. SD card read speeds are faster, which is handy since the device can boot a second OS from a memory card. On-board hardware encoding means the Librem 5 will be able to take 13 megapixel photos and shoot high-definition video for the first time.... "RISC-V is the future, and Librem 5 v2 is the perfect product to bring it to a mainstream audience", Jonathon Hall, CTO at Purism, says of the launch. "Freeing us from the control of Big Tech starts with the foundation, and RISC-V's foundation frees us from the oligarchy. The Librem 5 v2 puts you in control of your data, combining that with the ease of use we expect in the modern era". Its specifications include a 5.7-inch 720 x 1440 display, hardware kill switches, and a removable 4500mAh battery, writes Slashdot reader BrianFagioli: The asking price is $1,599, with production delivery targeted for roughly May 2028.. Purism acknowledges remaining work on graphics, peripheral drivers, ARM64 app emulation, and power management. NERDS.xyz argues that the concept is appealing, but the price and wait are difficult to justify for an everyday phone. Android already uses the Linux kernel, so the appeal here is an alternative built around PureOS and the broader desktop Linux ecosystem. Is this a reasonable cost to help fund that alternative, or too much money for hardware and software that buyers cannot yet evaluate as a finished product? Purism says they've already received 53 of their goal of 2,500 orders (2%) with 91 days still remaining. (The campaign runs through February 15 of 2027)

Read more of this story at Slashdot.

16 Nov 2026 8:34am GMT

feedPlanet Arch Linux

Mutex poisoning is not for everyone

After some recent discussion on the topic of mutex poisoning and notably a blog post that I thought was interesting, thoughtful, exhaustive, yet completely disagreed with, I wanted to comment on the debate myself. To me, poisoning-by-default is one of biggest mistakes that were made in the language, next to some others that are a story for a different time.

16 Nov 2026 12:00am GMT

15 Nov 2026

feedOSnews

KDE will now load XWayland on demand

When running KDE, the X11 compatibility layer for Wayland, XWayland, always runs, even if there isn't anything on the system still requiring the legacy X server to work. In the next step towards a Wayland-only world, the KDE people have reached a major milestone: XWayland now only runs when actually needed. This week a significant technical milestone was achieved: the XWayland compatibility layer is now loaded only when needed. Previously it had always been running even when no apps were using it, and fixing this required porting various system services away from legacy X11 code paths. This work was done by Vlad Zahorodnii, David Edmundson, and David Redondo, and will ship in Plasma 6.9. ↫ Nate Graham This frees up some system resources, which is always a welcome improvement. I do wonder how this might impact the load times of legacy X applications, but I have a feeling it's close to immeasurable.

15 Nov 2026 11:41pm GMT

Redox gets Go, GIMP, and more

I love and admire the Redox project, but their insistence on fudging the publication dates of their monthly progress reports really bothers me, for some reason. No, I'm not 16 days late - the report covering October was published only yesterday evening, and not on 31 October as the website claims. None of this matters to anyone but weird people such as myself, but I still want to get it off my chest. Don't bother any Redox people about this. Anyway, the big news for the month of October is the port of the official Go programming language compiler, allowing for cross-compilation and self-hosted compilation using relibc. Another major port also made its way to Redox in October: GIMP now runs on Redox, using the Orbital backend of the GTK port. The work to make Redox compatible with Cloud Hypervisor is also complete, with more information in its own dedicated article. Video playback in WebKitGTK3 has been fixed as well, and even YouTube works now which is quite neat. There's a ton more in this report, like an updated Servo port, NUMA support has been tested on real hardware for the first time and seems to work, work on rootless package installation has begun, and much more.

15 Nov 2026 11:31pm GMT

Disk encryption on NetBSD: achieving secrecy

NetBSD developer Nia Alarie has written a guide on how to set up a NetBSD system with disk encryption that's quite useful for those of us who deeply care about such a level of security. On top of that, the guide is also interesting if you just want to learn a bit more about how NetBSD works. The guide is written for sparc64, but should work on more mainstream architectures just as well. A guide written by a NetBSD developer is obviously going to employ some exotic or weird hardware. As is tradition.

15 Nov 2026 11:21pm GMT

08 Oct 2026

feedPlanet Arch Linux

Writing parsers is hard

This is a story of how we got from something like this: Failed to deserialize BUILDINFO file: Parser failed with the following error: unknown ^ invalid makepkg build environment option expected `buildflags`, `ccache`, `check`, `color`, `distcc`, `sign`, `makeflags` To this: When the ALPM project started, the goal was fairly simple: Better tooling to interact with the low-level plumbing of Arch Linux Package Management (ALPM). This meant binaries to read/write individual file types, better error messages, extensive specifications and of course exports to common dataformats like JSON. The thing is, although some of us already had experience with low-level dataframe parsing, …

08 Oct 2026 12:00am GMT

09 Aug 2026

feedPlanet Arch Linux

On scripts and hooks

Over the last few weeks, we have been doing research on the integration of our official distribution packages when installed on a target system. In this context we have been looking at the current uses of alpm-install-scriptlet(5) files and alpm-hooks(5) in around 120 package source repositories (alpm-source-repo(7)) to better understand the underlying functionality and use-cases these two integrations offer and target. In this article we are going to look at how these two systems work, how Arch Linux is currently using them and attempt to provide suggestions for when to use which. Learning about alpm-hooks(5) and alpm-install-scriptlet(5) files …

09 Aug 2026 12:00am GMT