What an odd statement to make.
"On Tuesday, a developer going by "Asahi Lina" announced she would be pausing work on Apple GPU drivers indefinitely. Asahi Lina posted on Bluesky: "I no longer feel safe working on Linux GPU drivers or the Linux graphics ecosystem."
https://www.theregister.com/2025/03/20/asahi_linux_asahi_lina/
Unfortunately there's a LOT of that shit going on in FOSS right now.
I'm sure that drivers will be welcome on RedoxOS. At least it is written entirely in Rust, after all.
2025-03-23 15:33 from Nurb432 <nurb432@uncensored.citadel.org>
What an odd statement to make.
"On Tuesday, a developer going by "Asahi Lina" announced she would be
pausing work on Apple GPU drivers indefinitely. Asahi Lina posted on
Bluesky: "I no longer feel safe working on Linux GPU drivers or the
Linux graphics ecosystem."
https://www.theregister.com/2025/03/20/asahi_linux_asahi_lina/
Gonna go out on a limb and assume nothing of value was lost.
The way i read it, she was a critical component in the GPU driver reverse engineering. But, i wont be getting an apple ever again for any reason so i wasn't following it too closely.
Tue Mar 25 2025 22:41:12 UTC from zelgomer
Gonna go out on a limb and assume nothing of value was lost.
9FRONT "THE FRONT END OF TOMORROW" RELEASED ===========================================  NOTABLE CHANGES --------------- The future of 64-bit platforms As we consider the hardware-based future of 9front, we have come to the conclusion that our current situation is unsustainable. When we consider the declining build quality of modern thinkpads, the 9front disorganization committee has reevaluated the common approach how to move forward, and believes it's time to take some bold steps which will carry us strongly into the future. We have surveyed 73 randomly selected users on stackoverflow, and on the strength of the results of this survey, we are confident that nobody will be impacted if 9front dropped amd64 support. Given the huge maintenance cost of immature computer architectures such as mips, 386, arm, arm64 and amd64, we decided to put our focus on the more mature and stable achitectures: power64 and itanuim. Therefore, all architectures other than power64 and itanium are thereby frozen, conserved and promoted to end of life. The advantages are clearly presented here: - The future is 64-bit: Driven by the needs of browser developers, it's become clear that a 32 bit address space is no longer enough. As we work towards expanding Mothra to support modern substandards, we will need room to grow. - Reduced distribution size: We are rapidly approaching the limit of what we can fit on a CD. Because we're uncertain if DVDs can be supported on Itanium, we feel the need to trim the fat. - Hardware more cheaply available: With the recent rise of Ebay, it's become clear that as large corporations bequeath us their wealth of power64 and itanium hardware, the prices of such machines will continue to drop. - Continued hardware popularity: We have done a survey of the popularity of Itanium, and in recent years, the number of active installations has been stable, giving us confidence that the platform will continue well into the future at its current level of market dominance. - Put an end to the "byte order fallacy" problem: With current hardware, we have limited ourselves to little endian byte order. Setting aside fact that the correct answer is: BIG ENDIAN, we feel that it's critical to our success that all processors we support in the future be big-endian. Given that the compilers for power64 and itanium are currently not up to our quality standards in regards to optimal instruction scheduling, the current distribution media only includes the binaries that that have passed our rigorous quality controll process. We believe that with these changes, 9front will replace inferno as the common dominant consumer operating system.
Nevermind on the above. I'm an idiot. its April 1. Of course i didn't catch it until i started actually reading it beyond the headline and image ( which was odd, but its an odd group anyway ).
These 'human things', like this "holiday", i just don't really get.
[ https://containrrr.dev/watchtower/ ]
Watchtower makes life a bit easier if you are running containerized apps in Docker (as opposed to Kubernetes or some other orchestration platform) and you want them kept updated automatically. It's delightfully simple. You run it as a container on the host, and you give it access to the Docker socket (using "-v /var/run/docker.sock:/var/run/docker.sock", of course) and at that point it just launches itself every 24 hours.
During each daily run, it scans Docker Hub (or some other registry you specify) for newer versions of the container images for everything you've got running on your system. When a new version is found, it is downloaded, and the container is re-launched using the same options that were specified when it was originally launched.
I have been running this on all of my Docker workloads for about a week now.
In fact, the instance of Citadel running Uncensored just updated itself earlier today. It's incredible seeing your stuff getting updated to the latest version without having to do anything manually. It's like seeing new features and fixes in a hosted SaaS app, but it's still self-hosted. The best of both worlds, really.
Naturally this is not indicated for every workload, because it assumes that you're accepting whatever QA has been done on every new version of the container image. If you're strict about testing and staging, Watchtower is probably not for you. But for the stuff I've got running here? Perfect. I get new versions of SearXNG several times a week. When I push a new version of Citadel I know it's going to end up on Uncensored without me ever having to do a thing.
Pipeline all the things!
I tried that once, forget which container. Failed miserably. It ended up destroying the container it was supposed to watch. ( thankfully not the data container, just the application )
But then again, not a fan of Docker.
Subject: Linux Kernel to Drop Support for Legacy i486 and Early 586 CPUs
Well there's always NetBSD.
Subject: Re: Linux Kernel to Drop Support for Legacy i486 and Early 586 CPUs
I mean really ... FPU emulation? It's time.
I'm looking forward to the end of all 32-bit x86 support ... but that's probably a while off.
Subject: Re: Linux Kernel to Drop Support for Legacy i486 and Early 586 CPUs
I'm not bothered by operating systems like Linux dropping support for CPUs that old at this point. What bothers me is people who get mad at other people for the unforgivable sin of supporting old hardware in their own free time.
Mon May 05 2025 02:36:00 UTC from IGnatius T Foobar Subject: Re: Linux Kernel to Drop Support for Legacy i486 and Early 586 CPUsIt's been generous to keep them supported for this long. There's no practical reason to keep hardware that old supported by a modern kernel. Retro scenes tend to run retro software anyway, or specialist software like NetBSD that's targeted for those sort of machines.
I mean really ... FPU emulation? It's time.
I'm looking forward to the end of all 32-bit x86 support ... but that's probably a while off.
It's fun to be able to say it works, but it carries with it so much technical debt that it robs the platform of the ability to move forward as well as it could.
NetBSD's position is "well, if there's no way to do functionality xyz in a clean way across every architecture, even the old ones, we just won't do that." And maybe you pay for that in terms of not being able to squeeze out the performance advantages of the very newest chips. There's a place for both approaches.
When I push a new version of Citadel I know it's going to end up on
Uncensored without me ever having to do a thing.
...he says, and then proceeds to break everything :)
Last friday I did some work on Citadel to fix a problem a user was having, and I added some "harmless" flags to the Makefile in the container's Dockerfile.
I built the container image, not noticing that it skipped major parts of the system without failing the build. Saturday morning, Watchtower noticed a new version of Citadel and dutifully pushed it to Uncensored, which went down for hours until I noticed.
Good times!