OSnews

I need to post about this because if I don't, people will get mad. Cook will continue on as Apple CEO through the summer, with Ternus set to join Apple's Board of Directors and take over as CEO on September 1, 2026. Cook is going to transition to chairman of the board at Apple, and he will assist with certain aspects of the company, including engaging with policymakers around the world." Juli Clover at MacRumors This concludes OSNews' coverage of Keeping Up With the Yacht Class, but rest assured, every other tech site will be milking this for weeks to come. You will still be worrying about how to pay for your next tank of gas.

Have you ever tried clicking the back button in your browser, only to realise the website you're on somehow doesn't allow that? Out of all the millions of annoyances on the web, Google has decided to finally address this one: they're going to punish the search rankings of websites that use this back button hijacking. Pages that are engaging in back button hijacking may be subject to manual spam actions or automated demotions, which can impact the site's performance in Google Search results. To give site owners time to make any needed changes, we're publishing this policy two months in advance of enforcement on June 15, 2026. Google Search Central It's always uncomfortable when Google unilaterally takes actions such as these, since rarely do Google's interests align with our own as users. This is in such rare case, though, and I can't wait to see this insipid practice relegated to the dustbin of history.

LXQt, the desktop environment which is effectively to KDE what Xfce is to GNOME, has released version 2.4.0. Quite a few changes in this release are further refinements and fixes related to LXQt's adoption of Wayland, but there are also a ton of small fixes, improvements, and small new features that have nothing to do with Wayland at all. There are also a few layout cleanups to make some dialogs and panels look a bit tidier and nicer. Note that LXQt supports both X11 and Wayland equally, and the choice of which to use is up to you. If you're using LXQt, you've already seen a few of these changes in point releases of its components, so not everything listed in the release notes might be news to you.

The title of my article on age verification in Linux and other operating systems had a for now" added for a reason, and here we are, with two members of the US Congress introducing a bill to add age verification to operating systems. The text of the proposed bill was only published today, and it's incredibly vague and wishy-washy, without any clear definitions and ton of open-ended questions. Still, if passed, the bill would require actual age verification, instead of mere voluntary age reporting that current state-level bills cover. It also seems to eschew the concept of age brackets, giving application developers access to specific ages of users instead. It's a vague mess of a bill that no sane person would ever want passed, but alas, sanity is a rare commodity these days, especially in US Congress. It's introduced by Democrat Josh Gottheimer and Republican Elise M. Stefanik, so it has that bipartisan sheen to it, which could increase its odds of going anywhere. At the same time, though, US Congress is about as useful as a box of matches during a house fire, so for all we know, this will end up going nowhere as its members focus on doing absolutely nothing to reign in the flock of coked-up headless chickens passing for an executive branch over there. If something like this gets passed, every US-based operating system - which includes most open source operating systems and Linux distributions - will probably fall in line when faced with massive fines and legal pressure. This isn't going to be pretty.

Tribblix, the Illumos distribution focused on giving you a classic UNIX-style experience, doesn't only support x86. It also has a branch for SPARC, which tends to run behind its x86 counterpart a little bit and has a few other limitations related to the fact SPARC is effectively no longer being developed. The Tribblix SPARC branch has been updated, and now roughly matches the latest x86 release from a few weeks ago. The graphical libraries libtiff and OpenEXR have been updated, retaining the old shared library versions for now. OpenSSL is now from the 3.5 series with the 3.0 api by default. Bind is now from the 9.20 series. OpenSSH is now 10.2, and you may get a Post-Quantum Cryptography warning if connecting to older SSH servers. zap install' now installs dependencies by default. zap create-user' will now restrict new home directories to mode 0700 by default; use the -M flag to choose different permissions. Support for UFS quotas has been removed. Tribblix release notes There's no new ISO yet, so to get to this new m34 release for SPARC you're going to have to install from an older ISO and update from there.

Another Haiku monthly activity report, but this time around, there's actually a big ticket item. Haiku has been in a pretty solid and stable state for a while now, so the activity reports have been dominated by fairly small, obscure changes, but during March a major milestone was reached for the ARM64 port. smrobtzz contributed the bulk of the work, including fixes for building on macOS on ARM64, drivers for the Apple S5L UART, fixes to the kernel base address, clearing the frame pointer before entering the kernel, mapping physical memory correctly, the basics for userland, and more. SED4906 contributed some fixes to the bootloader page mapping, and runtime_loader's page-size checks. Combined, these changes allow the ARM64 port to get to the desktop in QEMU. There's a forum thread, complete with screenshots, for anyone interested in following along. waddlesplash While it's only in QEMU, this is still a major achievement and paves the way for more people to work on the ARM64 port, possibly increasing its health. There's tons of smaller changes and fixes all over the place, too, as usual, and the team mentions beta 6 isn't quite ready yet, still. Don't let that stop you from just downloading the latest nightly, though - Haiku is mature enough to use it.

The editor in chief of this blog was born in 2004. She uses the 1997 window manager, Enlightenment E16, daily. In this article, I describe the process of fixing a show-stopping, rare bug that dates back to 2006 in the codebase. Surprisingly, the issue has roots in a faulty implementation of Newton's algorithm. Kamila Szewczyk I'm not going to pretend to understand any of this, but I know you people do. Enjoy.

Modern laptops promise a kind of magic. Shut the lid or press the sleep button, toss it in a backpack, and hours, days, or weeks later, it should wake up as if nothing happened with little to no battery drain. This sounds like a fairly trivial operation - y'know, you're literally just asking for the computer to do nothing - but in that quiet moment when the fans whir down, the screen turns dark, and your reflection stares back at you, your computer and all its little components are actually hard at work doing their bedtime routine. Aymeric Wibo at the FreeBSD Foundation A look at how suspend and resume works in practice, from the perspective of FreeBSD. Considering FreeBSD's laptop focus in recent times, not an unimportant subject.

A few weeks ago, Microsoft made some concrete promises about fixing and improving Windows, and among them was removing useless AI" integrations. Applications like Notepad, Snipping Tool, and others would see their AI" features removed. Well, it turns out Microsoft employs a very fringe definition of the concept. Microsoft seems to have stripped away mentions of the Copilot" brand in the Windows Insider version of the Notepad app. The Copilot button in the toolbar is gone, and instead, you'll find a writing icon which will present you AI-powered writing assistance, such as rewrite, summarize, tone modification, format configuration, and more. Additionally, AI features" in Notepad settings has been renamed to Advanced features" and it allows users to toggle off AI capabilities within the app. Usama Jawad at Neowin If the recent changes to Notepad are any indication, it seems Microsoft is, actually, not at all going to reducing unnecessary Copilot entry points", as they worded it, but is merely just going to rename these features so they aren't so ostentatiously present. At least, that seems to be the plan for Notepad, and we'll have to see if they have the same plans for the other applications. I mean, they have to push AI" or look like fools. I just don't understand how a company like Microsoft can be so utterly terrible at communication. While I personally would want all AI" features yeeted straight from Windows, I'm sure a ton of people are just fine with the features being less in-your-face and stuffed inside a normal menu alongside all the other normal features. They could've just been honest about their intentions, and it would've been so much better. Like virtually every other technology company, Microsoft just seems incapable of not lying.

Ever heard of a condition called bixonimania? Did you search the internet or ask your AI" girlfriend about some symptoms you were experiencing, and this was its answer? Well... The condition doesn't appear in the standard medical literature - because it doesn't exist. It's the invention of a team led by Almira Osmanovic Thunstrom, a medical researcher at the University of Gothenburg, Sweden, who dreamt up the skin condition and then uploaded two fake studies about it to a preprint server in early 2024. Osmanovic Thunstrom carried out this unusual experiment to test whether large language models (LLMs) would swallow the misinformation and then spit it out as reputable health advice. I wanted to see if I can create a medical condition that did not exist in the database," she says. Chris Stokel-Walker at Nature And AI" ate it up like quality chocolate. It started appearing in the answers from all the popular AI" tools within weeks, and later even started showing up as references in published literature, indicating that scientists copy/paste references without actually reading them. This is clearly a deeply concerning experiment, and highlights there may be many, many more nonsensical, fake studies being picked up by AI" tools. Of course, I hear you say, it's not like propagating fake or terrible studies is the sole domain of AI", as there are countless cases of this happening among actual real researchers and scientists, too. The issue, though, is that the fake studies concerning bixonimania" were intentionally made to be as silly and obviously ridiculous as possible. It references Starfleet Acadamy, the lab aboard the Enterprise, the University of Fellowship of the Ring, and many other fake references instantly recognisable as such by real humans. In fact, the studies even specifically mention that this entire paper is made up" and fifty made-up individuals aged between 20 and 50 years were recruited for the exposure group". It would take any human only a few seconds after opening one of these papers to realise they're entirely fake - yet, the world's most advanced AI" tools gobbled them up and spit them back out as pure fact within mere weeks of their publication This shouldn't come as a surprise. After all, AI" tools have no understanding, no intelligence, no context, and they can't actually make sense of anything. They are glorified pachinko machines with the output - the ball - tumbling down the most likely path between the pins based on nothing but chance and which pins it has already hit. AI" output understands the world about as much as the pachinko ball does, and as such, can't pick up on even the most obvious of cues that something is a fake or a forgery. It won't be long before truly nefarious forces start doing this very same thing. Why build, staff, and maintain a troll farm when you can just have AI" generate intentional misinformation which will then be spread and pushed by even more AI"? Remember, it took one malicious asshole just one long since retracted fake paper to convince millions that vaccines cause autism. I shudder to think how many people are accepting anything AI" says as gospel.

Version 7.0 of the Linux kernel has been released, marking the arbitrary end of the 6.x series. Significant changes in this release include the removal of the experimental" status for Rust code, a new filtering mechanism for io_uring operations, a switch to lazy preemption by default in the CPU scheduler, support for time-slice extension, the nullfs filesystem, self-healing support for the XFS filesystem, a number of improvements to the swap subsystem (described in this article and this one), general support for AccECN congestion notification, and more. See the LWN merge-window summaries (part1, part2) and the KernelNewbies 7.0 page for more details. corbet at LWN.net You can compile the kernel yourself, or just wait until it hits your distribution's repositories.

It shouldn't be a surprise that companies - and for our field, technology companies specifically - working with the defense industry tends to raise eyebrows. With things like the genocide in Gaza, the threats of genocide and war crimes against Iran, the mass murder in Lebanon, it's no surprise that western companies working with the militaries and defense companies involved in these atrocities are receiving some serious backlash. With that in mind, it seems Red Hat, owned by IBM, is desperately trying to scrub a certain white paper from the internet. Titled Compress the kill cycle with Red Hat Device Edge", the 2024 white paper details how Red Hat's products and technologies can make it easier and faster to, well, kill people. Links to the white paper throw up 404s now, but it can still easily be found on the Wayback Machine and other places. It's got some disturbingly euphemistic content. The find, fix, track, target, engage, assess (F2T2EA) process requires ubiquitous access to data at the strategic, operational and tactical levels. Red Hat Device Edge embeds captured, analyzed, and federated data sets in a manner that positions the warfighter to use artificial intelligence and machine learning (AI/ML) to increase the accuracy of airborne targeting and mission-guidance systems. Delivering near real-time data from sensor pods directly to airmen, accelerating the sensor-to-shooter cycle. Sharing near real-time sensor fusion data with joint and multinational forces to increase awareness, survivability, and lethality. The new software enabled the Stalker to deploy updated, AI-based automated target recognition capabilities. If the target is an adversary tracked vehicle on the far side of a ridge, a UAS carrying a server running Red Hat Device Edge could transmit video and metadata directly to shooters. Red Hat white paper titled Compress the kill cycle with Red Hat Device Edge" I don't think there's something inherently wrong with working together with your nation's military or defense companies, but that all hinges on what, exactly, said military is doing and how those defense companies' products are being used. The focus should be on national defense, aid during disasters, and responding to the legitimate requests of sovereign, democratic nations to come to their defense (e.g. helping Ukraine fight off the Russian invasion). There's always going to be difficult grey areas, but any military or defense company supporting the genocide in Gaza or supplying weapons to kill women and children in Iran is unequivocally wrong, morally reprehensible, and downright illegal on both an international and national level. It clearly seems someone at Red Hat feels the same way, as the company has been trying really hard to memory-hole this particular white paper, and considering its word choices and the state of the world today, it's easy to see why. Of course, the internet never forgets, and I certainly don't intend to let something like this slide. We all know companies like Microsoft, Oracle, and Google have no qualms about making a few bucks from a genocide or two, but it always feels a bit more traitorous to the cause when it's an open source company doing the profiting. It feels like Red Hat is trying to have its cake and eat it too, by, as an IBM subsidiary, trying to both profit from the vast sums of money sloshing around in the US military industrial complex as well as maintain its image as a scrappy open source business success story shitting bunnies and rainbows. It's a long time ago now that Red Hat felt like a genuine part of the open source community. Most of us - both outside and inside of Red Hat, I'm sure - have been well aware for a long time now that those days are well behind us, and I guess Red Hat doesn't like seeing its kill cycle this compressed.

If you want to run FreeBSD on a laptop, you're often yanked back to the Linux world of 20 years ago, with many components and parts not working and other issues such as sleep and wake problems. FreeBSD has been hard at work improving the experience of using FreeBSD on laptops, and now this has resulted in a list of laptops which work effortlessly with the venerable operating system. There's only about 10 laptops on the list so far, but they do span a range of affordability and age, with some of them surely being quite decent bargains on eBay or whatever other used stuff marketplace you use. If you want to use FreeBSD on a laptop, but don't want to face any surprises or do any difficult setup, get one of the laptops on this list - a list which will surely expand over time.

It may sound unbelievable to some, but not everyone has a datacenter beast with 128GB of VRAM shoved in their desktop PCs. Around the world people tell the tale of a particularly fierce group of Linux gamers: Those who dare attempt to play games with only 8 gigabytes of VRAM, or even less. Truly, it takes exceedingly strong resilience and determination to face the stutters and slowdowns bound to occur when the system starts running low on free VRAM. Carnage erupts inside the kernel driver as every application fights for as much GPU memory as it can hold on to. Any game caught up in this battle for resources will surely not leave unscathed. That is, until now. Because I fixed it. Natalie Vock The solution is to use cgroups to control the kernel's memory eviction policies, so that applications that should get priority when it comes to VRAM allocation - like games - don't get their memory evicted from VRAM to system RAM. Basically, evict everything else from VRAM before touching the protected application. This way, something like a game will have much more consistent access to more VRAM, thereby reducing needless memory evictions that harm performance. It's a clever solution that makes use of a ton of existing Linux tools, meaning it's also much easier to upstream, implement, and support. Excellent work.

You might have seen this, one of the strangest and most primitive experiences in macOS, where you're asked to press keys next to left Shift and right Shift, whatever they might be. Perhaps I can explain. Marcin Wichary It seems pretty obvious to me that's what it was for, but I guess many normal, regular people have never seen anything but one particular keyboard configuration (ANSI for Americans, ISO for some Europeans, etc.) keyboards. Perhaps they don't realise that not only are there ANSI keyboards with other layouts, but also entirely different keyboard configurations (mainly ISO and JIS). Interestingly, my home country of The Netherlands uses a US English layout on an ANSI configuration, but of course, it's the US International variant, either with deadkeys or using AltGr for the various accented/special characters we use. In my current country of residence, Sweden, they use this utterly wild and incomprehensible ISO layout where Shift unlocks characters on the bottom of keys, while AltGr unlocks characters at the top, the exact opposite of literally every other keyboard I've ever used (US Int'l, classic Dutch (no longer used), German, French, etc.). It's utterly bizarre, but entirely normal to my Swedish wife. We cannot use each other's keyboards.

This post aims to be a high level introduction to using USB for people who may not have worked with Hardware too much yet and just want to use the technology. There are amazing resources out there such as USB in a NutShell that go into a lot of detail about how USB precisely works (check them out if you want more information), they are however not really approachable for somebody who has never worked with USB before and doesn't have a certain background in Hardware. You don't need to be an Embedded Systems Engineer to use USB the same way you don't need to be a Network Specialist to use Sockets and the Internet. Nik WerWolv" A bit of a generic title, but the article details how to write a USB driver.

The months keep coming, and thus, the monthly progress reports keep coming, too, for Redox, the new general purpose operating system written in Rust. This past month, there's been considerable graphics improvements, better deadlock detection in the kernel, improved Unicode support thanks to switching over to ncurses library variant with Unicode support, and much more. Alongside these, you'll find the usual long list of kernel, driver, and relibc changes, bugfixes, and improvements. This month also covered three topics we've already discussed individually: Redox' new no-AI" code policy, capability-based security in Redox, and the brand-new CPU scheduler.

Since its launch in 2007, the Wii has seen several operating systems ported to it: Linux, NetBSD, and most-recently, Windows NT. Today, Mac OS X joins that list. In this post, I'll share how I ported the first version of Mac OS X, 10.0 Cheetah, to the Nintendo Wii. If you're not an operating systems expert or low-level engineer, you're in good company; this project was all about learning and navigating countless unknown unknowns". Join me as we explore the Wii's hardware, bootloader development, kernel patching, and writing drivers - and give the PowerPC versions of Mac OS X a new life on the Nintendo Wii. Bryan Keller And all of this, because someone on Reddit said it couldn't be done. It won't surprise you to learn that the work required was extensive, from writing a custom bootloader to digging through the XNU source code, applying binary patches to the kernel during the boot process, building a device tree, writing the necessary drivers, and so much more. Even just setting up a development environment was a pretty serious undertaking. Especially writing the drivers posed an interesting and unique challenge, as the Wii doesn't use PCI to connect and expose its hardware components. Instead, components are connected to a dedicated SoC with its own ARM processor that talks to the main Wii PowerPC processor, exposing hardware that way. This meant that Keller had to write a driver for this chip first, before moving on to the device drivers for devices connected to this ARM SoC - graphics drivers, input drivers, and so on. After a ton more work and overcoming several complex roadblocks, we now have Mac OS X 10.0 Cheetah on the Nintendo Wii. Amazing.

From 2024, but still accurate and interesting: Plan 9 is unique in this sense that everything the system needs is covered by the base install. This includes the compilers, graphical environment, window manager, text editors, ssh client, torrent client, web server, and the list goes on. Nearly everything a user can do with the system is available right from the get go. moody This is definitely something that sets Plan 9 apart from everything else, but as moody - 9front developer - notes, this also has a downside in that development isn't as fast, and Plan 9 variants of tools lack features upstream has for a long time. He further adds that he think this is why Plan 9 has remained mostly a hobbyist curiosity, but I'm not entirely sure that's the main reason. The cold and harsh truth is that Plan 9 is really weird, and while that weirdness is a huge part of its appeal and I hope it never loses it, it also means learning Plan 9 is really hard. I firmly believe Plan 9 has the potential to attract more users, but to get there, it's going to need an onboarding process that's more approachable than reading 9front's frequently questioned answers, excellent though they are. After installing 9front and loading it up for the first time, you basically hit a brick wall that's going to be rough to climb. It would be amazing if 9front could somehow add some climbing tools for first-time users, without actually giving up on its uniqueness. Sometimes, Plan 9 feels more like an experimental art project instead of the capable operating system that it is, and I feel like that chases people away. Which is a real shame.

Anos is a modern, opinionated, non-POSIX operating system (just a hobby, won't be big and professional like GNU-Linux) for x86_64 PCs and RISC-V machines. Anos currently comprises the STAGE3 microkernel, SYSTEM user-mode supervisor, and a base set of servers implementing the base of the operating system. There is a (WIP) toolchain for Anos based on Binutils, GCC (16-experimental) and Newlib (with a custom libgloss). Anos GitHub page It's written in C, runs on both x86-64 and RISC-V, and can run on real hardware too (but this hasn't been tested on RISC-V just yet). For the x86 side of things, it's strictly 64 bit, and requires a Haswell (4th Gen) chip or higher.

This year sees 35 years since 2.11BSD was announced on March 14, 1991 - itself a slightly late celebration of 20 years of the PDP-11 - and January 2026 brought what looks to be the venerable 16-bit OS's biggest ever patch! Much of the 1.3 MB size is due to Anders Magnusson, well-known for his work on NetBSD and the Portable C Compiler. Since 2.11BSD's stdio was not ANSI compliant, he's ported from 4.4BSD. BigSneakyDuck at Reddit There's an incredible amount of work in here on this old variant of BSD, including fixes for old bugs and tons of other changes. This, the 499th patch for 2.11BSD, is so big, in fact, that vi on 2.11BSD can't handle the size of the files, so you're going to need to cut them up with sed, for which instructions are included. It's quite unique to see such a big update on the 35th anniversary of an operating system.

Anyone remember the KDE 4.0 themes Oxygen and Air? Well, several KDE developers have been working tirelessly to bring them back, which means they're patching it up, fixing bugs, and generally making these classic themes work well in the current releases of KDE Plasma 6. The last post regarding work on fixing Oxygen was a month and a half ago. With all that's happened in between, it feels like so much more time has actually passed. With this post, I'd like to do a sort of mid-term update summing up all of the improvements done so far. These improvements are not just my work, but also, as you'll see, the work of the lead Oxygen designer Nuno Pinheiro, of several seasoned KDE developers, and of new contributors to Oxygen as well. Filip Fila The effort to bring these themes back go much beyond just making them nominally work; the developers and designers are also making sure the themes work properly with all the new features that have come to KDE since the 4.x and 5.x days, like adaptive and floating panels, various forms of blur, and a ton more - which includes making sure the themes are fully compatible with Wayland, which introduced a slew of new visual glitches and issues to these old themes in recent years. They are also working on improving, updating, and expanding the Oxygen icon set, which should surely bring back a ton of memories. This work involves not just designing new icons for applications and other things that didn't exist back when Oxygen was current, but also fixing old icons that look blurry on modern setups, addressing cases where monochrome and colourful icons mismatch, and so on. They're clearly taking this very seriously. It seems to be an organic effort more and more people got involved with as time passed, and they're aiming to have these themes ready for Plasma 6.7, to be released in June of this year. You can already try the current versions today, but they do require the absolute latest version of KDE Plasma to work properly. More improvements are planned for the coming weeks. This whole thing brings a massive smile to my face, and is such a perfect illustration of why I love the KDE project and its approach and spirit. At this point in time, I personally can't imagine using any other desktop environment.

This is a great post, but obviously it hasn't convinced me: The folks waving their arms and yelling about recent models' capabilities have a point: the thing works. This project finished in three weeks. Compare that to Ringspace, a similarly-sized project that took me about six months of nights and early mornings to complete, while not doing my day job or being Dad to an amazing, but demanding toddler. I simply could not have built this project as well or as quickly without help. And as other developers have noted, this is the help that's showing up. I'm not entirely onboard with Mike Masnick's optimistic view of this technology's democratizing power. I don't think it's as easy to separate the tech from its provenance or corporate control. But CertGen, my certificate application, exists now. It didn't and couldn't without the help of a tool like Claude Code. Open source in particular needs to reckon with this, because the current situation of demanding developers starve and bleed themselves dry without support isn't tenable. We need to grapple with this. I'm not yet sure how it all breaks down, and anyone who says they do is lying, foolish, or fanatical. Michael Taggart If you disregard that AI" models are trained on stolen data, that such data was prepared by exploited workers, that AI" data centres have a hugely negative impact on the environment, that AI" data centers are distorting the entire computing market, that AI" models they feed the endless firehose of intentional misinformation, that they are wreaking havoc in education, that they increase your reliance on American big tech companies, that you pay AI" companies for taking your work, that AI" models are a vital component in the technofascist wet dreams of their creators, that they are the cornerstone of politicians' dream of ending anonymity, and that they contribute to racist and abusive policing, then yes, sometimes, they produce code that works and isn't total horseshit. It's a deeply depressing reversed what have the Romans ever done for us?" that makes me sad, more than anything. I've seen so many otherwise smart, caring, and genuine people just shove all of these massive downsides aside for the mere novelty, the peer pressure, the occasional sense that their lines of code" metric is going up. It's the digital equivalent of rolling coal.

If you're using Windows or macOS and have Adobe Creative Cloud installed, you may want to take a peek at your hosts file. It turns out Adobe adds a bunch of entries into the hosts file, for a very stupid reason. They're using this to detect if you have Creative Cloud already installed when you visit on their website. When you visit https://www.adobe.com/home, they load this image using JavaScript: https://detect-ccd.creativecloud.adobe.com/cc.png If the DNS entry in your hosts file is present, your browser will therefore connect to their server, so they know you have Creative Cloud installed, otherwise the load fails, which they detect. They used to just hit http://localhost:<various ports>/cc.png which connected to your Creative Cloud app directly, but then Chrome started blocking Local Network Access, so they had to do this hosts file hack instead. thenickdude at Reddit At what point does a commercial software suite become malware?

An ultra-lightweight real-time operating system for resource-constrained IoT and embedded devices. Kernel footprint under 10 KB, 2 KB minimum RAM, preemptive priority-based scheduling. TinyOS GitHub page Written in C, open source, and supports ARM and RISC-V.

Another major improvement in Redox: a brand new scheduler which improves performance under load considerably. We have replaced the legacy Round Robin scheduler with a Deficit Weighted Round Robin scheduler. Due to this, we finally have a way of assigning different priorities to our Process contexts. When running under light load, you may not notice any difference, but under heavy load the new scheduler outperforms the old one (eg. ~150 FPS gain in the pixelcannon 3D Redox demo, and ~1.5x gain in operations/sec for CPU bound tasks and a similar improvement in responsiveness too (measured through schedrs)). Akshit Gaur Work is far from over in this area, as they're now moving on to replacing the static queue logic with the dynamic lag-calculations of full EEVDF.

You'd think if there was one corner of the open source world where you wouldn't find drama it'd be open source office suites, but it turns out we could not have been more wrong. First, there's The Document Foundation, stewards of LibreOffice, ejecting a ton of LibreOffice contributors. In the ongoing saga of The Document Foundation (TDF), their Membership Committee hasdecidedto eject from membership all Collabora staff and partners. That includes over thirty people who have contributed faithfully to LibreOffice for many years. It is interesting to see a formal meritocracy eject so many,based on unproven legal concerns and guilt by association. This includes seven of the top ten core committers of all time (excluding release engineers) currently working for Collabora Productivity.The move is the culmination of TDF losing a large number of founders from membership over the last few years with: Thorsten Behrens, Jan Kendy' Holesovsky, Rene Engelhard, Caolan McNamara, Michael Meeks, Cor Nouws and Italo Vignolino longer members. Of the remaining active founders, three of the last four are paid TDF staff (of whom none are programming on the core code). Micheal Meeks The end result seems to be that Collabora is effectively forking LibreOffice, which feels like we're back where we were 15 years ago when LibreOffice forked from OpenOffice. There seems to be a ton of drama and infighting here that I'm not particularly interested in, but it's sad to see such drama and infighting result in needless complications for developers, end users, and distributors alike. As if this wasn't enough, there's also forking drama in OnlyOffice land, the other open source office suite, licensed under the AGPL. This ope source office suite has been forked by Nextcloud and IONOS into Euro-Office, in pursuit of digital sovereignty in the EU. It's also not an entirely unimportant detail that OnlyOffice is Russian, with most of its developers residing in Russia. Anyway, the OnlyOffice team has not taken this in stride, claiming there's a violation of the AGPL license going on here, specifically because OnlyOffice adds contradictory attribution terms to the AGPL. It's a complicated story, but it does seem most experts in this area seem to disagree with OnlyOffice's interpretation. We're in for another messy time.

This is the first of a series of articles in which you will learn about what may be one of the silliest, most preventable, and most costly mishaps of the 21st century, where Microsoft all but lost OpenAI, its largest customer, and the trust of the US government. Axel Rietschin It won't take long into this series of articles before you start wondering how anyone manages to ship anything at Microsoft. If even half of this is accurate, this company should be placed under some sort of external oversight.

I assume I don't have to explain the difference between big-endian and little-endian systems to the average OSNews reader, and while most systems are either dual-endian or (most likely) little-endian, it's still good practice to make sure your code works on both. If you don't have a big-endian system, though, how do you do that? When programming, it is still important to write code that runs correctly on systems with either byte order (see for example The byte order fallacy). But without access to a big-endian machine, how does one test it? QEMU provides a convenient solution. With its user mode emulation we can easily run a binary on an emulated big-endian system, and we can use GCC to cross-compile to that system. Hans Wennborg If you want to make sure your code isn't arbitrarily restricted to little-endian, running a few tests this way is worth it.

I don't like to cover current events" very much, but the American government just revealed a truly bewildering policy effectively banning import of new consumer router models. This is ridiculous for many reasons, but if this does indeed come to pass it may be beneficial to learn how to homebrew" a router. Fortunately, you can make a router out of basically anything resembling a computer. Noah Bailey I genuinely can't believe making your own router with Linux or BSD might become a much more widespread thing in the US. I'm not saying it's a bad thing - it'll teach some people something new - but it just feels so absurd.

Why do so many people keep falling for the same trick over and over again? With an over $400 billion gap between the money invested in AI data centers and the actual revenue these products generate, Silicon Valley slowly returned to the tested and trusted playbook: advertising. Now, ads are starting to appear in pull requests generated by Copilot. According to Melbourne-based software developer Zach Manson, a team member used the AI to fix a simple typo in a pull request. Copilot did the job, but it also took the liberty of editing the PR's description to include this message: Quickly spin up Copilot coding agent tasks from anywhere on your macOS or Windows machine with Raycast." David Uzondu at Neowin It turns out that Microsoft has added ads to over 1.5 million Copilot pull requests on GitHub, and they're even appearing on GitLab, one of the GitHub alternatives. The reasoning is clear, too, of course: AI" companies and investors have poured ungodly amounts of money in AI" that is impossible to recover, even with paying customers. As such, the logical next step is ads, and many AI" companies are already starting to add advertising to their pachinko machines. It was only a matter of time before Copilot would start inserting ads into the pull requests it ejaculates over all kinds of projects. This isn't the first time a once-free service turns on its users, but it's definitely one of the quickest turnarounds I've ever seen. Usually it takes much longer before companies reach the stage of putting ads in their products to plug any financial bleeding, but with the amount of money poured into this useless black hole, it really shouldn't be surprising we're already there. I'm sure Copilot's competitors, like Claude, will soon follow suit. They're enshittifying Git, and developers are just letting it happen. No wonder worker exploitation is so rampant in Silicon Valley.

By reimplementing these features using capabilities, we made the kernel simpler by moving complex scheme and namespace management out of it which improved security and stability by reducing the attack surface and possible bugs. At the same time, we gained a means to support more sandboxing features using the CWD file descriptor. This project leads the way for future sandboxing support in Redox OS. As the OS continues to move toward capability-based security, it will be able to provide more modern security features. Ibuki Omatsu Redox seems to be making the right decisions at, crucially, the right time.

Of course, it was only a matter of time before the time-honoured tradition of the demoscene also got infected by AI". For me personally, generative AI ruins much of the fun. I still enjoy creating pixel art and making little animations and demos. My own creative process remains satisfying as an isolated activity. Alas, obvious AI generated imagery - as well as middle-aged men plagiarizing other, sometimes much younger, hobbyist artists - makes me feel disappointed and empty. It's not as much about effort as it is about the loss of style and personality; soul, if you will. The result is defacement, to echo T. S. Eliot, rather than inspired improvement. Even in more elaborate AI-based works, it's hard to tell where the prompt ends and the pixelling begins. Carl Svensson A wonderful explanation of the rather unique views on originality, stealing, plagiarism, and related topics within the demoscene, which certainly diverge from many other places.

This guide describes how you can install a Plan 9 network on an OpenBSD machine (it will probably work on any unix machine though). The authentication service (called authsrv" on Plan 9) is provided by a unix version: authsrv9. The file service is provided by a program called u9fs". It comes with Plan 9. Both run from inetd. The (diskless) cpu server is provided by running qemu, booted from only a floppy (so without local storage). Finally, the terminal is provided by the program drawterm. The nice thing about this approach is that you can use all your familiar unix tools to get started with Plan 9 (e.g. you can edit the Plan 9 files with your favorite unix editor). I'm assuming you have read at least something about Plan 9, for example the introduction paper Plan 9 from Bell Labs. Mechiel Lukkien If you're running OpenBSD, you're already doing something better than everyone else, and if you want to ascend to the next level, this is a great place to start. Of course, the final level, where you leave your earthly roots behind and become a being of pure enlightened energy, is running Plan 9 on real hardware as the universe intended, but let's not put the cart before the horse. One day, all of humanity will just be an endless collection of interconnected cosmic Plan 9 servers, more plentiful than the stars in the known universe.

Towards the end of 2024, Dennis Biesma decided to check out ChatGPT. The Amsterdam-based IT consultant had just ended a contract early. I had some time, so I thought: let's have a look at this new technology everyone is talking about," he says. Very quickly, I became fascinated." Biesma has asked himself why he was vulnerable to what came next. He was nearing 50. His adult daughter had left home, his wife went out to work and, in his field, the shift since Covid to working from home had left him feeling alittle isolated". He smoked a bit of cannabis some evenings to chill", but had done so for years with no ill effects. He had never experienced a mental illness. Yet within months of downloading ChatGPT, Biesma had sunk 100,000 (about 83,000) into a business startup based on a delusion, been hospitalised three times and tried to kill himself. Anna Moore at The Guardian These stories are absolutely heart-wrenching, and it doesn't just happen to people who have had a history of mental illness or other things you might associate with priming someone for falling for" an AI" chatbot. Just a few years in, and it's already clear that these tools pose a real danger to a group of people of indeterminate size, and proper research into the causes is absolutely warranted and needed. On top of that, if there's any evidence of wrongdoing from the companies behind these chatbots - intentionally making them more addictive, luring people in, ignoring established dangers, covering up addiction cases, etc. - lawsuits and regulation are definitely in order. Only yesterday, Facebook and Google lost a landmark trial in the US, ruling the companies intentionally made social media as addictive as possible, thereby destroying a person's life in the process. Countless similar lawsuits are underway all over the world, and I have a feeling that in a few years to decades, we'll look at unregulated, rampant social media the same way we look at tobacco now. Perhaps AI" chatbots will join their ranks, too.

Today,we'reexcited to announce a significant step forward in our ongoing commitment toWindowssecurity and system reliability: theremovaloftrust for all kerneldrivers signed by thedeprecatedcross-signed root program. This update will helpprotect our customers by ensuring that onlykerneldriversthat the Windows Hardware Compatibility Program (WHCP) have passedand been signed can be loaded by default. To raise the bar for platform security, Microsoft will maintain an explicit allow list of reputable drivers signed by the cross-signed program.Theallow list ensures a secure and compatible experience for alimited number of widely used, and reputable cross-signed drivers. This new kernel trust policy appliestosystems running Windows 11 24H2, Windows 1125H2,Windows 11 26H1,and Windows Server 2025in theApril 2026Windows update. All futureversions ofWindows11and Windows Server will enforce the new kernel trust policy. Peter Waxman at the Windows IT Pro Blog The cross-signed root program was discontinued in 2021, and ran since the early 2000s, so I think it's fair to no longer automatically assume such possibly old and outdated drivers are still to be trusted.

I'll never grow tired of reading about the crazy tricks the Windows 95 development team employed to make the user experience as seamless as they could given the constraints they were dealing with. During the 16bit Windows days, application installers could replace system components with newer versions if such was necessary. Installers were supposed to do a version check, but many of them didn't follow this guidance. When moving to Windows 95, this meant installers ended up replacing Windows 95 system components with Windows 3.x versions, which wasn't exactly a goods thing. So, they came up with a solution. Windows 95 worked around this by keeping a backup copy of commonly-overwritten files in a hidden C:\Windows\SYSBCKUP directory. Whenever an installer finished, Windows went and checked whether any of these commonly-overwritten files had indeed been overwritten. If so, and the replacement has a higher version number than the one in the SYSBCKUP directory, then the replacement was copied into the SYSBCKUP directory for safekeeping. Conversely, if the replacement has a lower version number than the one in the SYSBCKUP directory, then the copy from SYSBCKUP was copied on top of the rogue replacement. Raymond Chen All of this happened entirely silently, and neither the installers nor the user had any idea this was happening. The Windows 95 team tried other solutions, like just making it impossible to replace system components with older versions entirely, but that caused many installers to break. Some installers apparently even went rogue and would create a batch file that would replace the system components upon a reboot, before Windows 95 could perform its silent fixes. Wild. I used Windows 95 extensively, and had no idea this was a thing.

The U.S. Federal Communications Commission said on Monday it was banning the import of all new foreign-made consumer routers, the latest crackdown on Chinese-made electronic gear over security concerns. China is estimated to control at least 60% of the U.S. market for home routers, boxes that connect computers, phones, and smart devices to the internet. David Shepardson at Reuters I'm sure the American public will be thrilled to find out yet another necessity has drastically increased in price.

It's the end of an era: Apple has confirmed to 9to5Mac that the Mac Pro is being discontinued. It has been removed from Apple's website as of Thursday afternoon. The buy" page on Apple's website for the Mac Pro now redirects to the Mac's homepage, where all references have been removed. Apple has also confirmed to 9to5Mac that it has no plans to offer future Mac Pro hardware. Chance Miller at 9To5Mac If a Mac Pro falls in the back of the Apple Store and there's no one around to hear it, does it make a sound?

Several US states, the country of Brazil, and I'm sure other places in the world have enacted or are planning to enact laws that would place the burden of age verification of users on the shoulders of operating system makers. The legal landscape is quite fragmented at this point, and there's no way to tell which way these laws will go, with tons of uncertainties around to whom these laws would apply, if it targets accounts for application store access or the operating system as a whole, what constitutes an operating system in the first place, and many more. Still, these laws are already forcing major players like Apple to implement sharing self-reported age brackets with application developers (at least in iOS), so there's definitely something happening here. In recent weeks, the open source world has also been confronted with the first consequences of these laws, as both systemd and xdg-desktop-portal have responded to operating system-level age verification laws in, among other places, California and Colorado, by adding birthDate to userdb (on systemd's side) and developing an age verification portal (on xdg-desktop-portal's side) for use by Flatpaks. The age verification portal would then use the value set in usrdb's birthDate as its data source. The value in birthDate would only be modifiable by an administrator, but can be read by users, applications, and so on. Crucially, this field is entirely optional, and distributions, desktop environments, and users are under zero obligation to use it or to enter a truthful value. In fact, contrary to countless news items and comments about these additions, nothing about this even remotely constitutes as age verification", as nothing - not the government, not the distribution or desktop environments, not the user - has to or even can verify anything. If these changes make it to your distribution, you don't have to suddenly show your government ID, scan your face, or link your computer to some government-run verification service, or even enter anything anywhere in the first place. Furthermore, while the xdg-desktop-portal's proposals are still fluid and subject to change, consensus seems to be to only share age brackets with applications, instead of full birth dates or specific ages - assuming anything has even been entered in the birthDate field in the first place. Even if your Linux distribution and/or desktop environment implements everything needed to support these changes and expose them to you in a nice user interface, everything about it is optional and under your full control. The field is of the same type as the existing fields emailAddress, realName, and location, which are similarly entirely optional and can be left empty if desired. Taken in isolation, then, as it currently stands, there's really not much meat to these changes at all. The primary reason to implement these changes is to minimally comply with the new laws in California, Colorado, Brazil, and other places, and it's understandable why the people involved would want to do so. If they do not, they could face lawsuits, fines, or worse, and I don't know about you, but I wouldn't want to be on the receiving end of the western world's most incompetent justice system. Aside from that, these changes make it possible to build robust parental controls, which isn't mentioned in the original commits to systemd, but is clearly the main focal point of xdg-desktop-portal's proposal. This all seems well and good, but given today's political climate in the United States, as well as the course of history, that as it currently stands" is doing a lot of heavy lifting. Rightfully so, a lot of people are worried about where this could lead. Sure, today these are just inconsequential, optional changes in response to what seems to be misguided legislation, but what happens once these laws are tightened, become more demanding, and start requiring a lot more than just a self-reported age bracket? In Texas, for instance, H.B. 1131 requires any commercial entity, including websites, that contains more than one-third sexual material harmful to minors" to implement age verification tools using things like government-issued IDs or bank transaction data to verify visitors' ages before allowing them in. The UK has a similar law on the books, too. It's not difficult to imagine how some other law will eventually shift this much stricter, actual age verification from websites and applications into operating systems instead. What will systemd's and xdg-desktop-portal's developers do, then? Will they comply as readily then as they do now? This is a genuine worry, especially if you already belong to a group targeted by the current US administration, or were face-scanned by ICE at a protest. Large groups of especially religious extremists consider anything that's LGBTQ+ to be sexual material harmful to minors", even if it's just something normal like a gay character in a TV show. It's not hard to imagine how age verification laws, especially if they force age verification at the operating system level, can become weaponised to target the LGBTQ+ community, other minorities, and people protesting the Trump regime. You may think this won't affect you, since you're using an open source operating system like desktop Linux or one of the BSDs, and surely they are principled enough to ignore such dangerous laws and simply not comply at all, right? Sadly, here's where the idealism and principles of the open source world are going to meet the harsh boot of reality; while open source software has a picturesque image of talented youngsters hacking away in their bedrooms, the reality is that most of the popular open source operating systems are actually hugely complex operations that require a ton of funding, and that funding is often managed by foundations. And guess where most popular Linux distributions' and BSD variants' foundations are located? Developers from all over the world may contribute to Debian, but all of its financials and trademarks are managed by Software in the Public Interest, domiciled in New York State. Fedora is part of Red Hat, owned by IBM, and

Usually, when developers or programmers write articles about their experiences developing for a platform they have little to no experience with, the end result usually comes down to they do things differently, therefor it is bad actually", which is deeply unhelpful. This article, though, is from a longtime Windows user and developer, but one who hasn't had to work on native Windows development for a long time now. When he decided to write his own native Windows application to scratch a personal itch, it wasn't a great experience. While I followed the Windows development ecosystem from the sidelines, my professional work never involved writing native Windows apps. (Chromium is technically a native app, but is more like its own operating system.) And for my hobby projects, the web was always a better choice. But, spurred on by fond childhood memories, I thought writing a fun little Windows utility program might be a good retirement project. Well. I am here to report that the scene is a complete mess. I totally understand why nobody writes native Windows applications these days, and instead people turn to Electron. Domenic Denicola Denicola decided to try and use the latest technologies and best practices from Microsoft regarding Windows development, and basically came away aghast at just how shot of an experience it really is. I'm not a developer, but you don't need to be to grasp the severity of the situation after following his development timeline and reading about his struggles. If this is truly representative of the Windows application development experience, it's really no surprise just how few new, quality Windows applications there are, and why even Microsoft's own Windows developers resort to things like React for the Start menu to enabler faster and easier iteration. This is a complete dumpster fire.

These were Sun microcontrollers that run Squawk Java ME directly on metal with gc and all the bells and whistles, created by Sun Microsystems in 2005. The feature mesh networking and tcp/ip and multitasking. Even the drivers are java just like Java OS. They run a command and control server by default and there's graphical network builders and deployment managers (Solarium) they also do some more esoteric stuff like process migration. Penny I have no use for these but I want them. They would've made an excellent addition to my Sun article. There's still a detailed tutorial and informational website up about these things, too.

In recent weeks, systemd has both embraced slopcoding and laid the groundwork for age verification built right into systemd-based Linux distributions, there's definitely been an uptick in people talking about alternative init systems. If you want to gain understanding in a rather classic init system, OpenBSD's is a great place to start. OpenBSD has a delightfully traditional init system, which makes it a great place to start learning about init systems. It's simple and effective. There's a bit of a counter movement in the IT and FOSS worlds rebelling against hyperscaler solutions pushing down into everyone's practices. One of the rallying cries I've been seeing is to remind people that You Can Just Do ThingsTM on the computer. The BSD init system, and especially OpenBSD's is something of a godparent to this movement. init(8) just runs a shell script to start the computer, and You Can Just Do ThingsTM in the script to get them to happen on boot. Overeducated-Redneck.net My main laptop is currently in for warranty repairs, but once it returns, I intend to set it up with either OpenBSD or a Linux distribution without systemd (most likely Void) to see how many systems I can distance from systemd without giving myself too much of a headache (I'm guessing my gaming machine will remain on systemd-based Fedora). I'm not particularly keen on slopcoding and government-mandated age verification inside my operating systems, and I'm definitely feeling a bit of a slippery slope underneath my feet. I have my limits.

Earlier this year, Microsoft openly acknowledged the sorry state of Windows 11, and made vague promises about possible improvements somewhere in the near future, but stayed away from making any concrete promises. Today, the company published a blog post with some more details, including some actual concrete, tangible changes it's going to implement over the coming two months. In coming builds, you'll be able to move the taskbar to any side of the screen, instead of it being locked to the bottom, thereby reintroducing a feature present since Windows 95. They're also scaling back their obsession with ramming AI" in every corner of Windows, and will be removing Copilot integrations from Snipping Tool, Photos, Widgets, and Notepad. Furthermore, and this is a big one among Windows users I'm sure, Windows Update will be placed under user control once again, allowing them to ignore updates, postpone them indefinitely, reboot without applying updates, and so on. These are the tangible improvements we'll be able to point to and say the company kept their word, and they all feel like welcome changes. There's also a few promises that feel far more vague and less tangible, like the ever-present, long-running promise to improve File Explorer". I feel like Microsoft's been promising to fix their horrible file manager for years now, without much to show for it, so I hope this time will be different. The company also wants to improve Widgets, the Windows Insider Program, and the Feedback Hub application. These all feel less tangible, and will be harder to quantify and benchmark. Beyond these first round of improvements that we're supposed to be seeing over the coming two months, Microsoft also promises to implement wider improvements across the board, with the usual suspects like better performance, quicker application launches, improved reliability, lower memory usage, and so on. They also promise to move more core Windows user interface components to WinUI 3, including the Start menu, which is currently written in React. Windows Search is another common pain point among Windows users, and here, Microsoft promises to improve its performance and clearly separate local from online results (but no word on making search exclusively local). There's some more details in the blog post, but overall, it sounds great. However, words without actions are about as meaningful as a White House statement on the war with Iran, so seeing is believing.

When Google said they were going to require verification from every single Android developer that would end the ability to install applications from outside of the Play Store (commonly wrongfully referred to as sideloading"), it caused quite a backlash. The company then backtracked a little bit, and said they would come up with an advanced flow" to make sure installing applications from outside of the Play Store remained possible. Well, Google has detailed this advanced flow", and as everyone expected, it's such a massive list of onerous hoops to jump through they might as well just lock Android down to the Play Store and get it over with. First, if a developer is verified, you can download their applications to your device and install them the same way you can do now. Second, developers with limited distribution accounts", such as students or hobby projects, can share their applications with up to 20 devices without verification. Third, and this is where the fun starts, we have unverified developers - basically what all Android developers sharing applications outside of the Play Store are now. Here's the full advanced flow" as described by Google to allow you to install an application from an unverified developer: Setting aside the fact that developer verification is, in and of itself, a massive problem, I'm kind of okay with a few scary warnings, a disclaimer, and perhaps a single reboot to enable installing applications outside of the Play Store - a few things to make normal people shrug their shoulders and not bother. However, adding enabling developer mode and a goddamn 24-hour waiting period is batshit insanity, and clearly has the intention of discouraging everyone, effectively locking Android to the Play Store. Android is already basically an entirely locked-down, closed-source platform, and once this advanced flow" comes into force, there's virtually no difference between iOS and Android, especially for us Europeans who get similarly onerous anti-user nonsense when trying to install alternative application stores on iOS. I see no reason to buy Android over iOS at this point - might as well get the faster phone with better update support.

What happens if you make a Linux syscall in a Windows application? So yeah, you can make Linux syscalls from Windows programs, as long as they're running under Wine. Totally useless, but the fact that such a Frankenstein monster of a program could exist is funny to me. nicebyte at gpfault.net The fact that this works is both surprising and unsurprising at the same time.

The GNOME team has released GNOME 50, the latest version of what is probably the most popular open source desktop environment. It brings fine-grained parental controls, and the groundwork for web filtering so that in future releases, parents and guardians can set content filters for children. Our own kids are still way too young to have access to computers and the internet, but I'm not sure I'll ever resort to these kinds of tools when the time comes. I didn't have any such controls imposed upon me as a child on the early internet, but then, you can't really compare the '90s internet to that of today. The Orca screen reader received a lot of attention in GNOME 50, with a new preference window, both global and per-application settings, and much more. There's also a brand new reduced motion setting, which will tame the animations in the user interface. Document annotation has been overhauled and modernised, and the file manager has been optimised across the board for better performance and lower memory usage. Remote Desktop also saw a lot of work in GNOME 50. It's now hardware-accelerated using VA-API and Vulkan, and thanks to HiDPI support, the session will properly adapt to the screen being used. Kerberos Authentication support has been added, and you can now use the remote webcam locally. There's way more here, like improved support for variable-refresh rates and fractional scaling, HDR screen sharing, fixes for weird NVIDIA driver nonsense, and much, much more. As always, GNOME 50 will find its way to your distribution soon enough.

PosrtmarketOS, the Linux distribution' for mobile devices, now also has an immutable variant, called Duranium. Duranium is an immutable variant of postmarketOS, built around the idea that your device should just work, and keep working. You shouldn't need to know what a terminal is to keep your device running. Immutable" means the core operating system is read-only and can't be modified while it's running. System updates are applied as complete, verified images rather than individual packages. Either the new image works, or the system falls back to the previous one automatically. No partially-applied state. No debugging audio when you need to make a phone call and no fussing with a broken web browser when you just want to doomscroll cat photos. It also means developers can reproduce the exact state of a user's device, making it much easier to track down and fix issues. Clayton Craft on the postmarketOS blog Duranium is built around the various functionalities and tooling provided by systemd, meaning the project didn't have to reinvent the wheel. It works similarly to other immutable distributions, in that images for the base are downloaded and installed as a whole, with the preferred application installation method being Flatpak. Security-wise, Duranium uses dm-verity to protect /usr, cryptographically verifying data as it's read. The image simply won't boot if anything's been tampered with. LUKS2 is used to encrypt mutable user and operating system data and configuration on the root file system. Duranium is still under heavy development, but it makes sense to implement something like this now, since in the world of mobile devices, this has become the norm. I'm glad postmarketOS is taking these steps, and I sincerely hope I'll eventually be able to use a postmarketOS device with KDE's Plasma mobile shell at some point in the near future in my day-to-day life. This requires both postmarketOS to improve as well as for the regulatory landscape to break the duopoly on banking and government applications held by Android and iOS, and with the state of the US government as it is, this might actually be something Europe's interested in achieving.

DOS didn't have sudo yet. This gross oversight has been addressed. SUDO examines the environment for the COMSPEC variable to find the default command interpreter, falling back to C:\COMMAND.COM if not set. The interpreter is then executed in unprotected real mode for full privileges. SUDO for DOS' Codeberg page A vital tool, for sure.

Once again, social media giants Facebook and TikTok have been caught red-handed. More than a dozen whistleblowers and insiders have laid bare how the companies took risks with safety on issues including violence, sexual blackmail and terrorism as they battled for users' attention. An engineer at Meta, which owns Facebook and Instagram, described how he had been told by senior management to allow more borderline" harmful content - which includes misogyny and conspiracy theories - in user's feeds to compete with TikTok. They sort of told us that it's because the stock price is down," the engineer said. Marianna Spring and Mike Radford at the BBC Meta, TikTok, and Twitter are criminal enterprises, and their executives should be trembling in court instead of scheming on yachts. Their role in legitimising far-right extremism will eventually catch up to them, and once that happens, no yacht is going to keep them safe.