- cross-posted to:
- linux@lemmy.eco.br
- cross-posted to:
- linux@lemmy.eco.br
Good. Either big tech chip in and start helping maintain the LTS kernels or pay a respectable salary to those who maintain it.
Big tech won’t chip in is my bet. My company maintains its own version of Linux that has some specific certifications. Updating that box requires an act of god. My bet is that the companies that can afford to will create their own “LTS” versions that just get older and older, and more broken and exploited as time goes on…
Sorry, long night at work =/
Eventually they’ll do some ring fencing and call the problem solved.
Pretty sure all big tech companies already have engineers on payroll for this specific reason. Intel, Microsoft, Google, Amazon have SWEs working on the kernel, networking, even DEs for their own needs and integrations.
And yet still the maintainers don’t want to maintain 6 yo kernels because it’s cumbersome and an unpaid position.
Unpaid? A lot of kernel devs do get paid, especially the core ones that would be looking after this stuff.
75% – The share of all kernel development that is done by developers who are being paid for their work.
https://www.pingdom.com/blog/linux-kernel-development-numbers/
Big tech won’t suffer. They will just fork and maintain (and probably enshittify) their own kernel.
Small and mid tech will suffer, however. The article just mentions Android as the prime example for embedded systems and forgets to mention that 80-90% of industrial embedded systems run on Linux.
Those will either be driven to Microsoft’s shitty half-done, hardly documented embedded OS versions or some company rises as the white knight offering and maintaining LTS Linux kernels. Both scenarios will increase cost of course that will eventually come out of us consumers’ pockets. The former, worse scenario will make industrial applications less secure on top.
Do Redhat and SUSE not maintain their own LTS kernels for their enterprise distributions?
Does big tech run 6 yo kernels? This seems like a corporation problem not wanting to spend the money properly maintaining their systems. If big tech isn’t dogfooding a 6yo kernel, it doesn’t make sense to do it.
Yes, according to the article, while this doesn’t affect the PC/server as much because the distributions take care of security for the most part, where this will have problems is the phone/IoT space (which is why Linux initially started maintaining 6 yo kernels, to cater to that market).
It’s not like most phones are getting updates past two years at this point anyway, and while it would be nice if we could actually get software updates and keep our devices longer, I have my doubts that is ever going to happen on Android. I have more faith that someday I’ll get my dream RISC-V powered phone with several Linux distros to choose between or even dual boot.
IoT devices are a slightly different story, but I’m skeptical that Linux offering 6 year kernels has made a meaningful difference in those devices actually getting updates.
The article points out that the kernel version used in a phone is basically frozen when development of the device starts. They’re suggesting that at 2 years of support, the kernel will be EOL about when the phone is released.
That is the real problem, why is it frozen so early? Why not keep it up to date for more of the development lifecycle rather than shipping a 2 year old kernel. It is not like you have to worry about OTA updates if you have not shipped it yet,
Drivers from 3rd party. Didn’t work on phone development, but was part of a company that developed setup boxes.
We will get a kernel from broadcom with all the necessary drivers that was tested for that configuration. Updating was very hard without support and might cost a lot.
See the Fairphone, you might be surprised
Or Samsung phones, they have 4 or 5 years of updates.
Fairphone is targeting 8-10 years with the new model
Think printers, factory machines and so on. If they run Linux and not Windows CE, it’s always an ancient kernel.
Big tech chipping in is how we get Amazon spyware/Microsoft apps built into OS. I agree with respectable salary for developers. I think if Linux org ran the same campaign as Wikipedia it would gather a lot more donations. The whole world runs on some form of the Linux kernel.
That’s not how the Linux kernel works…
The final decision on what is merged into the kernel is Linus’ decision and that’s how it’s been the last 30 years.
Microsoft bakes spyware into the operating system because they own the NT kernel and the Windows OS.
Amazon clones the Linux kernel, modifies it and adds it’s own garbage software, then builds it.
The main Linux kernel is free of any spy shit and that’s how it’s likely going to remain.
While I agree, Linus isn’t getting younger and as we are seeing, long time lead maintainers are starting to step down. It would be a shame if Linux kernel and subsequently it’s OS’s, turns into what happened to Android. We see it happening time and time again (e.g. Reddit, Twitter), when there is the possibility for more revenue, these companies will kill anything that was developed 'for the people ’
At least any spy shit that we know of. Just look at the obfuscated C contest what’s possible in that abomination of a language.
Any code that is anywhere near that unreadable let alone purposefully obfuscated is not making it past the review process
Sorry, I meant the Underhanded C contest. This is a contest for code that looks benign, but does something completely different.
I find it that being on the latest kernel is more stable than using an ancient one.
Do you run a desktop environment as opposed to servers with server class hardware?
If you use LTS sofware, then you have to live with problems that were fixed years ago.
This is the best summary I could come up with:
The other big problem is the burnout from maintainers, which are often unpaid and could use a lot more support from the billion-dollar companies that benefit from using Linux.
The problem was that on PCs, two years only represents the time between kernel updates, so that’s a fine timeline.
Embedded devices tend not to update the kernel, though, so those “two years” represent most of the development cycle and the entire consumer support window, and that’s not long enough.
The original picture Google painted in 2017 was that phones take two years to be developed and that the kernel is locked in near the beginning of the engineering process.
That’s going to start a new window of support, remember, so even with a paltry two years of ownership, that’s a six-year-old kernel.
Rumor has it that the Pixel 8 will have a longer support window, so maybe we’ll see major kernel updates launch with that phone.
The original article contains 842 words, the summary contains 156 words. Saved 81%. I’m a bot and I’m open source!
Oh no… anyway…
Does this matter in a meaningful way? I mean, isn’t the kernel itself extremely stable and compatible anyway? Upgrading to a new version every two years doesn’t seem that onerous, but then again I’m not ruining specialty hardware, so I don’t know.
Matters for servers, but if companies doesn’t want to transistion they can just pay for extended support from some other company I guess.
Based and true