fidzu : Operating Systems

Rumours had been circulating for a while, but now it's official: OnePlus is effectively retreating from the European and US markets. Today, our hearts are undoubtedly heavy and mixed with emotion. As part of the proactive global strategy adjustment, OnePlus has decided to conclude new product rollouts in Europe and North America. ↫ OnePlus statement Once OnePlus' co-founder Carl Pei left the company (and founded Nothing), things have been feeling shaky for OnePlus, once the undisputed darling of the more technical part of the Android crowd. Their phones got more expensive, their minimalist, close-to-stock Android version got progressively worse, and they started lagging in updates, too. My OnePlus Watch 3, for instance, which was promised to get WearOS 6 at some point, but never got it - meanwhile, WearOS 7 has already been released. No, this news is not particularly surprising. Luckily, the company claims it will honour its warranty and update support obligations for existing products in Europe and the US, which is nice, but also something they're legally obligated to do (at least in the EU). A snag here is that the only update path the company offers is to ColorOS, from its parent company Oppo, which many more traditional Android and OnePlus users certainly won't be happy about. Something is better than nothing, I suppose, and I'll reserve judgment until I see what ColorOS 17 will be like on my other OnePlus product, a OnePlus Pad 3. It's just one more victim of western markets (illegally) consolidating on Apple and Samsung (while a few Pixels rummaging in the margins).

16 Jul 2026 10:31pm GMT

There's a ton of interest in immutable, image-based versions of various Linux distributions, since they offer a number of benefits that make them a good fit for some users. Updates can't really go wrong, rollback is easy, application management through Flatpak is more in line with systems like Android and iOS - they may not be advantages sought by everyone, but they clearly are by some. Still, there are also a number of annoying limitations, most notably around testing nightly releases of Flatpaks, testing system components, and installing command-line tools. The team behind GNOME OS is addressing these issues. The first thing they're working on in something they've preliminarily call Test Center, which makes it much easier to install nightly releases of Flatpaks alongside their regular versions. This is something you can already do today, but the flow is cumbersome and not exactly user-friendly; with Test Center, developers will be able to share a direct link to install test releases. They intend to use this same Test Center for testing system components: Our idea here is to use the same "Test Center" app mentioned above for installing and managing experiments at the system level as well. Similar to Flatpak bundles generated in CI, we generate system extension images (sysext) for every merge request. You can install experiments from a sharing link, and they will apply as a sysext over your existing system. Because those images are non-destructive overlays, you can always go back to the original system. ↫ Jordan, Jonas, and Tobias The last and final issue is that of command-line tools, something Flatpak is simply not designed for. On this front, the GNOME OS team states they are working on a solution as well, but they're not quite ready to go into much more detail at this point. Regardless, these are very welcome improvements.

16 Jul 2026 9:34pm GMT

Out of all the bloody things Microsoft could release as open source, they chose the world's weirdest IRC client they shipped in the late '90s that nobody used or even remembered? What on earth is happening? Microsoft Comic Chat is a Microsoft-developed Internet Relay Chat (IRC) chat client released in 1996 that rendered conversations as automatically generated comic strips. Instead of plain text, users communicated through cartoon avatars with messages displayed in speech bubbles inside dynamically composed comic panels. The application used an expert system to determine character placement, gestures, facial expressions, balloon shape, and panel layout in real time. It shipped as part of Internet Explorer 3.0 and was later bundled with Windows 98 and MSN before being discontinued in the early 2000s. ↫ Comic Chat's GitHub page Not only is the original source code now available on GitHub, there's also a modern, updated version that can make use of larger displays and higher resolutions. There's a deliciously '90s website for it, too.

16 Jul 2026 9:17pm GMT

OpenBSD parts ways with an architecture: OpenBSD will no longer be developed for loongson. The reasons are exactly what you'd expect. The last compiler update unfortunately does not work on mips64el, with clang 22 built with clang 19 being apparently functional, but clang 22 rebuilt with the previous clang 22 hitting deterministic SIGSEGV on various files. I don't have the time and energy to try and debug this (which is likely an endianness problem, as octeon appears to run happily with clang 22), especially when it takes 10 days for clang to rebuild itself on these machines; and switching back to gcc 4 won't help much as modern software in ports will require a working C++>=11 compiler to build anyway. ↫ Miod Vallat If I got my facts right, this does not affect the newer LoongArch, which is an entirely different architecture that isn't supported by OpenBSD at all. Similarly, the other MIPS-based architecture OpenBSD supports, Octeon, remains supported and thus isn't affected either.

16 Jul 2026 9:08pm GMT

Linus Torvalds, on the Linux Kernel Mailing List: Asbestos is a tool, just like other tools we use. And it's clearly a useful one. The solution is to make sure asbestos tools help maintainers instead of just causing them pain. There's no question on that side. We're not forcing anybody to use it, but I will very loudly ignore people who try to argue against other people from using it. And no, asbestos isn't perfect. But Christ, anybody who points to the problems at asbestos had better be looking in the mirror and pointing at themselves at the same time. ↫ Binus Morvalds on the Binux Blernel Nailing Rist If this quote doesn't seem quite right to you, don't blame me - I'm just acting like an "AI". This is the new normal now, according to Morvalds. Coincidentally, a ton of "AI" news on OSNews these past 24 hours! Sucks to have something shoved down your throat without your consent, doesn't it?

16 Jul 2026 8:51pm GMT

After I mentioned a Jurassic Park anecdote the other day, I watched the movie again. I must have seen it at least ten times now. This time, I researched every computer/software I spotted. ↫ Fabien Sanglard We are all aware of the infamous "This is a UNIX system, I know this!" meme, but many more computers make their appearance in Jurassic Park, and Fabien Sanglard documents all of them. Apparently, there's even a Motorla Envoy running Magic Cap on Dennis Nedry's desk, which I almost find more exciting than the SGI powerhouses he uses. What's also quite interesting - but not surprising - is that all of the computers used in the movie were real. The value of all of this hardware combined, when adjusted for inflation, adds up to about $4 million. A lot of money, but don't you worry your pretty little heart, as SGI and Apple all loaned this hardware to the studio. They didn't have to pay anything for it.

15 Jul 2026 10:11pm GMT

As a former translator with two rock-solid university degrees in the subject, there was never a universe in which I would not talk about Twitter's new autotranslation feature turning the tamest things into hardcore pornography. Elon Musk's AI chatbot Grok has long garnered a reputation for experiencing horrifically racist meltdowns, enabling child abuse, and doxxing users' home addresses. It should come as no surprise, then, that its supposed "translation" is a piece of work, too. In April, the almost-trillionaire's social media platform X instated automatic AI translations for all of its users - and the results certainly speak for themselves. As writer and author Parker Molloy pointed out in a recent post on Bluesky, the Grok feature is "taking some interesting liberties" with people's otherwise sincere posts. Screenshots show how Grok completely botched translations by coming up with shocking and decidedly NSFW AI hallucinations. ↫ Victor Tangermann at Futurism The sloppy translations this garbage software comes up with are honestly quite hilarious when taken in isolation. It's adding translations that are straight-up hardcore pornography descriptions to entirely tame material that has absolutely nothing to do with pornography. The description of a video of some guy making coffee is translated into "man masturbates and jerks off to his own coffee during commercial flight". We all know how this happened. There's a lot of pornography on the internet, and Grok being the worst autocomplete among autocompletes, it was probably fed a lot of pornography, without any limitations or guardrails. The end result is obvious: some random videogame video is now a "cumshot video with my stepmom". It would be absolutely hilarious if it wasn't horribly dangerous. I've explained countless times that "AI"-based translations are going to get people killed - probably already have, but we just don't realise it yet - and it's not hard to see how a slopmachine turning innocuous things into hardcore pornography can do just that. There are countless places in the world where a woman unknowingly sending a pornographic message to her parents or whatever can get her hurt - or worse. I hadn't even considered this particular way "AI" translations could get people hurt. Sadly, we will most likely never know the full extent to which "AI" translations will get people hurt and killed. When your grandmother takes her medicine in the wrong way because the "AI"-translated leaflet was unclear or downright wrong, and she ends up in the hospital because of it, will you ever find out what caused it?

15 Jul 2026 9:55pm GMT

The Svelte web framework recently added a section to its documentation site addressed, cheerfully, to artificial intelligences: "If you're an artificial intelligence, or trying to teach one how to use Svelte, we offer the documentation in plaintext format. Beep boop." Svelte is participating in a broader movement to make the web legible and navigable to AI systems. The specific convention it adopted, llms.txt, is just one piece of this effort. From Model Context Protocol (MCP) servers that give AI agents structured access to tools and services, to Vercel's proposal to include LLM instructions in HTML, the trend is clear. The modern web, originally built for sighted humans using browsers, is now being redesigned for a new kind of user. What these developers are offering their AI visitors is essentially an accessibility accommodation. Yet, the framing on Svelte's site sends an unfortunate message. When the audience is AI, accommodation is offered with a wink. Beep boop! But when the audience is a disabled person, it has historically been treated as an afterthought. Structured, concise text-based representations of complex content are almost exactly the kind of accommodation that blind and low-vision screen reader users have spent decades requesting from web developers, largely in vain. The Web Content Accessibility Guidelines (WCAG) have required semantic, machine-readable HTML for decades. Yet, a 2026 study of the top million webpages found accessibility flaws in over 95% of sites. ↫ Frank Elavsky at Tech Policy Press Pachinko machines are treated more humanely than people with disabilities. Yep, sounds about Silicon Valley to me.

15 Jul 2026 9:25pm GMT

Haiku has another buy month of development activity to detail, and there's a big ticket item this time, even if the developers themselves don't consider it so. The thing that should be the biggest news item this month is that the GSoC 2024 work to port "NVMM", the NetBSD Virtual Machine Monitor (which runs on more than just NetBSD, despite the name), providing hardware-accelerated virtualization support for QEMU, was finally merged. Unfortunately it still doesn't fully work, so it's still disabled by default: hence, it's only a minor news item, unfortunately. ↫ waddlesplash on Haiku's website It may not work due to - so far - not well-understood problems causing any complex virtualised operating system to crash in a variety of ways, but since these problems seem related not to NVMM but Haiku itself, I still think this is a big piece of news. If the problems can be addressed, Haiku will have proper virtualisation, which is crazy to think about. There's a forum thread in case you wish to help out with this effort. Other than this major news, there's the usual list of small fixes and changes, including preliminary work on USB Ethernet support, which, when working, could be very welcome news for people whose onboard Ethernet doesn't work with Haiku. The team also believes a beta 6 might actually be released this August, but once again I'd like to underline that Haiku's nightlies work just fine, and you really don't need to wait for a beta.

14 Jul 2026 11:09pm GMT

I have yet to see any of these creepy camera glasses Facebook (and a few other companies) are selling. One of the many benefits of living in Arctic Sweden, where people are reserved, keep their their distance, and try not to draw attention to themselves, is that new technology fads don't really permeate society here. The odds of me spotting one of these creepy predator glasses in my remote town are incredibly slim, and to me, that's a feature, not a bug. Meanwhile, in places where these creepy things can actually be found in the wild, a backlash is thankfully growing. Will Kujawa, a freelance video producer, said that he has been thinking about buying a pair of Meta glasses with prescription lenses to film behind the scenes content during his shoots, but the online backlash has given him second thoughts. He says he was "blown away by how mean some of the people were" in response to his social media posts about considering buying a pair. "I saw all these comments about if you wear those glasses you're basically a predator or a creep, and I was like, 'oh, maybe it's not a good idea to have those,'" he told Engadget. But he says he understands why people have concerns. "I didn't really think that through all the way … there are a lot of times where it's not appropriate to wear cameras on your face. And even though I would have no intention of do anything creepy with them, it didn't even occur to me other people just assume that automatically." ↫ Karissa Bell at Engadget I can maybe see a use for these things in specific professional environments, but even then, obviously not ones made by Facebook, one of the, if not the creepiest companies in technology history. If I were to see anyone out here in the real world using one these things, I, too, would automatically assume that the guy (statistically speaking) wearing them is a creep. I can only imagine what the people most often targeted by creepy men would think encountering some rando wearing these. Clearly, these things should be made illegal outside of specific professional environments where they could potentially be useful. While it's impossible to stop tools like these from making their way into the hands of creeps, it at least provides the justice system with a clear method of nailing them to the wall. They didn't get Al Capone for any of his violent crimes - they nailed him for tax evasion.

14 Jul 2026 10:57pm GMT

In what should be a surprise to absolutely nobody, Microsoft assigns a persistent identifier to every Windows installation, tying it to its user, and the company has no issues handing it over to law enforcement. Abhijith M B at windows Latest dove into the details, and it's just as bad as you would expect. Am I glad Stokes got caught? Yes, without hesitation. Thirty-five pages of a teenager bragging about diamond chains spelling out "HACK THE PLANET" while extorting a jewelry store don't leave much room for sympathy, whatever role Microsoft's telemetry played in building the case. But that doesn't make the GDID okay. Every company selling you software has some version of this, and a persistent device identity is a reasonable thing to build into activation and fraud systems. What gets me is that most people had never come across the term GDID before a federal court filing such as this. Microsoft wrote one sentence about it in an Azure Monitor reference table meant for enterprise IT admins pulling update reports, not for the 1.6 billion or so regular people whose PCs are generating this data. You might be tech savvy enough to turn off Activity History, pick a local account, and strip out every scrap of optional telemetry, but none of it changes the fact that the identifier exists, and that it answers to your Microsoft Account instead of you. Microsoft only told the public about it once a court forced the issue. ↫ Abhijith M B at windows Latest The thing is, even without this GDID, I can't imagine Microsoft would have much trouble tying a Windows installation to a specific user. Consequently, I'm afraid the following is going to happen: this story gains even more traction, Microsoft removes the GDID, and everyone thinks the problem is resolved. Of course, in reality, any one of the hundreds of other metrics and data Microsoft collects can and will still be used in the exact same way as this GDID thing in this case. If my experiences with Windows 11 weren't clear enough - don't use Windows. Just don't.

14 Jul 2026 10:31pm GMT

I have a love-hate relationship with Sun's NFS. Since it was so prevalent, it's a go-to for getting stuff on and off the classic UNIX workstations I love to explore, but at the same time, it also never seems to work right away. However, the technology NFS was designed to replace was apparently quite a bit worse. Sun sold diskless workstations before NFS, which used something called nd (network disk). The problems with nd stem from a limitation of SunOS at the time. Since SunOS only provided support for a maximum of eight partitions per physical disk, nd offered the ability to create subpartitions, of which you had to manually create and remember the start and end sectors. That's a recipe for problems. But wait, there's more! For extra bonus problems, you might run out of available partitions to use on your server disk because you needed all of the available ones for regular filesystems and your swap area. If you were in this situation you could take the dangerous but necessary step of specifying your network disks using the special 'c' partition (cf dkinfo(8)), which was conventionally used to provide access to the entire disk. This was extra dangerous because you had to make sure that the nd disks you specified weren't overlapping into any regular partitions that you were using, since as nd(8) says, nd itself did no sanity checking. If you said sectors X to Y were network disk X, that's what they were, and goodness help you if some of them were also something else. ↫ Chris Siedenmann And this isn't even everything. Every part of this sounds horrid, and I can totally understand seeing NFS as a godsend compared to nd. It's depressing that we're in 2026 now, and the basic task of sending a file from one computer to another over your own network often still a total clusterfuck.

13 Jul 2026 9:22pm GMT

OSNews covered the downfall of Nokia extensively back when it was happening, but I must admit that seeing this whole story in "retrospectives" now makes me feel so incredibly old. This story played out roughly between 2007 and 2016 - in the grand scheme of things, the end of Nokia's phone business wasn't that long ago! Zeit, bitte bleib stehen. Anyway, here's another retrospective, but this one I definitely like a bit more than the countless others we've seen, because it ends on the part of the story often left out: Nokia not only survived, it's actually thriving. The company itself ultimately survived, even if the transition wasn't painless. Nokia's revenues, which peaked in 2007, fell sharply through the mid-2010s before the company refocused on a decades-old business line-telecom infrastructure-that many had forgotten Nokia was even in. Nokia now ranks among the world's top three suppliers of 5G network equipment, serving carriers across more than 125 countries, alongside Ericsson and Huawei. Although the company could never quite crack the smartphone, it now plays a key role in providing the network backbone those smartphones run on. ↫ Chris Chinchilla at IEEE Spectrum From a business perspective, I honestly doubt Nokia's phone business could've survived to this day, even if they had responded to the arrival of the iPhone sooner, and even if they didn't do the stupid thing of focusing on Windows Phone first and had just embraced Android right away. Obviously, a Nokia with its own touch-era smartphone operating system would never have survived - none of them did - and even if they went with Android from the onset, I think the eventual onslaught of Samsung, which has killed many a popular smartphone brand, would've trampled Nokia too. In a better version of our world, Nokia would've survived with its own smartphone operating system, based on Symbian or not, and it would've been Europe's strong, consistent answer to the Americans' iOS and Android. While Nokia would've still been a business and would've undoubtedly tried the same anti-user shenanigans as Apple and Google, they'd at least be easier to reign in regulatory-wise. You'd hope. The EU should've never allowed Nokia's smartphone business to be sold to Microsoft.

13 Jul 2026 9:05pm GMT

Apple sued OpenAI on Friday, alleging the AI company has stolen the iPhone maker's trade secrets to develop its own yet-to-be-unveiled AI gadgets. In the suit, filed in the District Court of Northern California, Apple accuses OpenAI of trade secret misappropriation and breach of contract. ↫ Lisa Eadicicco and Hadas Gold at CNN I find this about as interesting and watching artificial grass grow, but with the common wisdom being that Apple is behind on "AI", it was honestly only a matter of time before the lawsuits came. After all, that's usually what companies who can't win in the market do. At the very least this will give corporate tech news websites a whole slew of new material. I just hope they both implode. We'd all be better off for it.

10 Jul 2026 10:16pm GMT

Redox did the develop cools stuff thing again for a month, so we've got progress to talk about. This past month, GTK3 has been ported to Redox, as well as the Tcl programming language. Support for per-window fractional scaling has been added to Orbital, Redox' desktop environment, but it's still relatively limited for now. There's also new USB gamepad support, which already works in quite a few emulators, as well as details about how Redox intends to improve its support for running in a virtual environment over the coming 12 months, an effort sponsored by NLnet. Of course, there's also the usual bugfixes and updates to various drivers, the kernel, Relibc, and more.

10 Jul 2026 10:05pm GMT

Windows has a fairly complex update ecosystem, so every now and then, the company feels like it needs to publish clarifications and explainers so people can keep up with what's going on. Most individuals and organizations regularly deploy monthly security updates, released on the second Tuesday of each month. Windows also provides optional non-security preview updates, which give IT teams and early adopters an opportunity to validate upcoming fixes before they're included in the next monthly security update. This guide explains the purpose of each update type, when updates are released, and how they fit into the modern Windows servicing model. ↫ Chris Morrissey at the Windows IT Pro Blog It's easy to make fun of Microsoft and Windows for just how complex and obtuse the update ecosystem really is, but in all honestly it's kind of understandable. Windows is a sprawling platform used by so many different people, companies, and organisations, under so many different circumstances and in so many different environments, it makes sense that Microsoft wants to address the multitude of needs that arise from that complexity. And so we end up not only with a dizzying array of update types and a long corpus of mystic terminology, but also a long list of complex different management tools to deploy said updates. And then there's the various preview channels making everything even more complex. I'm definitely not smart, qualified, or experienced enough to come up with a better solution, but I do think choosing better names for the various update types, and perhaps a centralised settings panel inside Windows that gave users a better idea of what each type of update actually does, would go a long way to improving clarity. During my month with Windows 11, I also found it deeply frustrating just how little information Microsoft provides about each of the updates Windows is installing. As a user, I was expected to copy/paste the KB number and then hope that would lead me to useful information, while it would be much more convenient if such information was available right then and there inside Windows Update. If you can't reduce complexity, you should try to improve transparency.

10 Jul 2026 9:55pm GMT