Based on the actual bug report, because the people working on this are volunteers and the workaround is simple.
If you think fixing bugs like these is a worthwhile endeavour, chip in some money or volunteer. There are many ways for people volunteer that aren’t writing code, so if you aren’t a software developer don’t let that discourage you.
He wants everyone to become prompt engineers sloperators.
This take is so cold it could make solid helium.
(I agree FWIW)
Shhhh no choose, only Kubuntu.
Becoming addicted to tea and drinking it constantly can help solve the dehydration issue.
Oh I’m not complaining that action was taken. The issue is that the tools available to us are antithetical to copyleft. All the takedown means is that nobody gets access to this code, whereas what we need is for everyone to get access to it under the proper license.
We really need a better answer to stuff like this than DMCA takedowns. They make sense for someone who doesn’t want their stuff made available at all, but it’s kinda the opposite of what’s needed for copyleft violations.
To be fair, Windows has had standby issues forever, so the only thing that’s different here from 20 years ago is that Linux does it reliably.
Doubly evil given that GPU prices are still ridiculous.
Daily driving Kubuntu 26.04
I think OP is talking about the fact that most new projects use “main” now, so “master” likely indicates an older project.
I was once on a video call with my sister, walking around the house and getting more and more frustrated as I did so. Eventually she asked me what I was looking for.
“I CAN’T FIND MY GODDAMN PHONE!”
She burst out laughing.
…that’s not what they’re doing though?
Those patches get either pulled from upstream or built in-house and shared to upstream. Just like in Debian, and just like in the regular Ubuntu releases, the package is based on some upstream version and then the deb packaging applies the patch sets as listed in the diff tarball.
Here’s what the latest kernel for Ubuntu 26.04 look like: https://launchpad.net/ubuntu/+source/linux/6.17.0-6.6
Those same tarballs are available for any Ubuntu package by running apt source <pkg> as long as you’ve configured the matching deb-src repositories.
You mean things like cloud-init, juju, a ton of work they do directly upstream on openstack, hardware certifications (which include things like getting vendors to upstream their drivers into the mainline kernel — something even Google has struggled with for Android), and making it more feasible for more companies to run Linux by providing the sort of long-term support that the community just doesn’t prioritise?
Red Hat charge for access to the RHEL binaries. That’s literally why CentOS came into existence.
Everything that’s in main gets released to everyone with the security fixes. Canonical’s security team works on those.
The stuff in the universe repo is owned by the Ubuntu community (not by Canonical), so anyone can submit those fixes, but it depends on the Masters of the Universe, who are all volunteers, to get it upstreamed.
The extra Ubuntu Pro updates for the universe repo come from when someone who’s paying for Ubuntu Pro asks Canonical to make a patch. The source is still available to anyone, so someone could take that patch and then submit it to the community who maintains the universe repo.
Once the 5 years of standard support ends, then the only way to get additional fixes is through Ubuntu Pro, but if Canonical writes those fixes they also submit them back upstream (as opposed to if they grab a specific patch from upstream — and even then it’s still available on Launchpad regardless.
The reason nobody’s made a CentOS but for Ubuntu Pro is that it’s way easier to submit the patches through the community (and become part of that community who approves packages) than it is to spin up all the infrastructure that would be needed.
As someone who owns several RISC-V devices the primary thing preventing usable (low end) RISC-V laptops is the GPUs. Most RISC-V silicon has Imagination GPUs, and the current state of the drivers there is “proprietary drivers stuck on an old LTS kernel.”
If someone makes an RVA23 compliant chip with open mainstreamable drivers and a BXS-4-64 GPU (or, better yet, somehow manages to license a GPU from Intel or AMD for it), that’ll be a cash cow.
If by “WRECK” you mean “improve” yes.
I think it’s also fair to say this can be considered research into his take on LLMs.