fidzu : Operating Systems

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

You all donated en masse to have me use Windows 11 for a month, and so I did. What was it like for a long-time Linux user to go back and experience Windows as it exists now? Is it really as bad as we've collectively made it out to be? Did my month with Windows 11 consist of nothing but pain and misery, or are there good things to say, too? Or, was it an unexpected pleasant surprise? And ultimately, did I stay with Windows 11, or move back to the Linux world? ➡️ Donate through Ko-Fi ➡️ Donate through SEPA transfer* ➡️ Buy merch from our store ➡️ Why a fundraiser? *Name: Thom Holwerda - IBAN: SE08 8000 0820 1684 4657 8414 - BIC: SWEDSESS This year, I'm celebrating the milestone of having posted 20000 stories on OSNews during my 21 years as managing editor of OSNews. This is my full-time job, and since nobody is going to give me any bonuses, stock options, or golden pens, we're running a big fundraiser to keep OSNews going. To add some spice to the whole thing, I added some incentives, with the first being using Windows 11 for a month. We're slowly but steadily approaching the next incentive, too, which is a proper video tour of my office, (unique) computers, and massive devices collection. There's a similar incentive to this Windows 11 one, but for macOS. Yikes. The rules for the Windows 11 incentive are simple: use stock Windows 11 for a month for my computing tasks (with the exception of gaming - converting my Linux gaming PC to Windows just to play the same games seemed silly). I wasn't allowed to use any debloating tools, but as an EU citizen, I do have the ability to remove a ton of Windows stuff thanks to the success of the Digital Markets Act. I also tried to stick to Microsoft's own applications as much as possible, for that true "ecosystem experience", and wasn't allowed to hack my way into a normal local user account. I was all-in. So what was it like? Setting it all up The installation process posed a number of challenges and issues. First and foremost, the Windows 11 installation process is incredibly barebones, and basically assumes no other operating system exists in the world. It has no clue anything other than Windows' filesystems exist, making it dangerously easy to accidentally damage or outright delete any other operating systems you might have installed. My laptop happens to have two M.2 SSDs in, so I could safely dedicate one of them to Windows 11 without interfering with the other SSD with Fedora installed on it, but if you're experimenting with Windows 11 on your Linux machine with just one drive, you might want to reconsider. I also had to perform the first portion of the installation process - the WinPE section - with just my keyboard, since apparently, my trackpad was not supported and did not work at all. Once the system went through its first of what would be many reboots to come and loaded into the phase of the installation where you're actually already running Windows 11, my trackpad came to life, but without any gestures support - so no scrolling. Not a gamebreaker or anything, but definitely annoying. A bigger issue was that the Wi-Fi 7 Intel BE200 chip in my laptop was not supported out of the box by Windows 11. This meant that I had to install these drivers during the installation process, which involves going to the Intel website and finding the correct drivers to use. To make this process more obtuse and less intuitive, you can't use the normal driver installer; you have to specifically opt for the "Intel® PROSet/Wireless Software and Wi-Fi Drivers for IT Administrators", download the ZIP, unpack it on a different computer, put the unpacked drivers on a USB stick, and point the Windows 11 installer to this USB stick. Mind you, the BE200 chip was launched almost three years ago, and there's no excuse for Windows 11 not supporting this chip out of the box - like Linux does. The remainder of the installation process involved dodging a lot of tracking and telemetry prompts, reboots, a lot of waiting, setting up the dreaded online account, waiting some more, and then finally ending up at the desktop. I then set out to enjoy my EU privileges by removing whatever applications I didn't need and turning off features I didn't want, as well as making sure all the drivers were up to date. This mostly involved installing the Intel Driver & Support Assistant and the Intel graphics drivers. Curiously, this is where I hit a returning issue: after installing the Intel GPU drivers for the first time, as well as after every subsequent update, the screen would go black and stay that way, forcing a reboot. Windows' graphics stack is supposed to be able to gracefully handle driver updates, but clearly, some bug or problem was preventing the updated Intel driver from being reinitialised. Once those initial setup tasks were behind me, I experienced two more problems. First, sleep/wake was entirely broken and simply did not work. It turns out Windows 11 really doesn't like S3 sleep, and I had to specifically go into my laptop's Dasharo Coreboot firmware to switch to S0ix get sleep/wake to work on Windows 11. Windows defaults to something it calls "Modern Standby", which requires the S0ix state to be enabled. You can also disable Modern Standby which would presumably make sleep/wake work with S3 (?), but this is a whole ordeal and clearly not something Microsoft wants you to do. Of course, the correct way of handling this would be for Windows 11 to adapt its sleep/wake settings to what the firmware reports, but alas. Another problem were the laptop's cooling fans seemingly leading lives of their own, spinning up loudly at entirely random times, irrespective of use. It was so bad and loud

08 Jul 2026 10:27pm GMT

With July being Disability Pride Month, GNOME's Sophie Herold published a blog post taking stock of where GNOME stands on this front, progress that's been made, as well as areas where the project comes short. One particular paragraph from her introduction really hits the nail on the head about accessibility discussions in tech circles: The reality of tech communities is that they are often ableist and elitist. Probably more so than the average population. If a user or contributor struggles with a tool, blame is shifted to a "skill issue," if an interface is simplified to make it accessible to more people, it's "dumbed down". Assistive technologies are often developed by abled people, without involving and paying disabled people. This also leads to an attitude where contributors expect gratefulness from disabled people for providing them with the most basic needs. All these issues are also not absent from the GNOME community. ↫ Sophie Herold Even as someone who isn't disabled and doesn't use any tools classically shelved under the "accessibility" moniker, I encounter the attitudes she mentions in the quoted paragraph basically every day. While we can have normal, productive discussions and differences of opinion about accessibility - for instance, I strongly believe robust theming support is absolutely crucial to accessibility, while the wider GNOME community does not - the dismissive attitudes towards people with accessibility needs in the software world is shameful. Even if you don't have accessibility needs today, you will definitely be needing them at some point in your life. If accessibility isn't one of the first words you jot down on your mood board or whatever when you start a new software project, you've already done millions of people a massive disservice. Get educated, learn what you can about accessibility, listen to people with accessibility needs, and make your software better for everyone. You'll thank yourself one day.

08 Jul 2026 10:23pm GMT

Linux Mint's Cinnamon is one of the last desktops to still not support Wayland, and is relegated to only being compatible with legacy X11 environments. With the next release of Cinnamon, however, this is finally going to change. We worked really hard on Wayland and we got to the point where it feels solid and the experience is almost on par with X11. Wayland support will no longer be considered "experimental". In the next version of Cinnamon, both X11 and Wayland will be fully supported. ↫ Clement Lefebvre on the Linux Mint blog The next release of Cinnamon, version 6.8, will be part of the next release of Linux Mint, scheduled for Christmas of this year.

08 Jul 2026 10:07pm GMT

About a month ago, Flathub announced a ban on slopcoded applications. Evangelos "GeopJr" Paterakis, developer of a number of popular Linux applications and ton of other things, did some research into just how many applications tagged with "AI slop", a tag Flathub reviewers used to keep track of slopcoded applications submitted to Flathub, actually survived the test of time. The results are exactly what you'd expect. Of the 120 unique repos, 32 were maintained and 88 were abandoned. No seriously, a big portion of them was completely deleted, nowhere to be found, others stopped 6 months ago, right after submitting to Flathub. ↫ Evangelos "GeopJr" Paterakis That's absolutely soul-crushing. Why should Flathub's reviewers spend their precious, limited time talking to lazy slopcoders' "AI" agents to get their slopcoded applications into Flathub, when 70% of these applications are abandoned or outright deleted from existence within mere months of being submitted? Minimal effort for the slopcoders, maximum effort for the reviewers. Just dump a bunch of shitty code over the fence, let a chatbot handle the interactions with the reviewers, and pretend you made a valuable contribution. This is the contradiction slopcode enthusiasts really don't want to talk about. If these "AI" tools are so great, where is all the amazing new software? Where's the massive gains in software quality? Isn't the story that "AI" tools do the menial work, giving programmers more time to focus on improving their software? Reality does not seem to match the story we're being sold. Despite these slopcode tools being out and available for years now, there's no influx of great applications and other software, there's no rise in software quality, nothing. What we mostly seem to be getting are slopcoded projects nobody, not even their "creators" care about, so they just get abandoned and deleted as quickly as they were dredged up from the bottom of the programming barrel. These aren't applications created because someone wanted them to exist; these are applications created because some mid programmer got high on their "AI" supply and fancied themselves better at programming than they really are - only to realise once the comedown hits they've got crappy, barely working, entirely unmaintainable gibberish vaguely looking like code nobody can make head nor tails of. And then they abandon the project, ready for the next high - leaving everyone else to clean up their mess. What a miserable workflow.

07 Jul 2026 11:18pm GMT

Only a few days ago we had Linux on the Mega Drive, and someone took that as a challenge, so now we have Linux on the Atari Jaguar. The Jaguar has a very different architecture than the Mega Drive, but does happen to use a processor from the same 68000-family. Interestingly enough, to this day, Linux has architecture code for the 68000-family of processors. 68040, 68030, 68010… and even the original base 68000 processor. All neatly structured under arch/m68k/. ↫ Joel Bueno And, well, that means Linux can indeed be made to work on the Jaguar, with some hacking and magic, of course.

07 Jul 2026 9:06pm GMT