News for hackers. Stuff that matters.
Re:Linux gives up on 6-year LTS kernels, says they’re too mu... by athrun on Wednesday September 20, 2023 @10:09PM (#37592488)
As an ex-Novell/SUSE employee this makes sense to me. Upstream is supposed to keep marching onwards.

Backporting is _so_ much work. And it's unfortunately not sexy work either, so it's always going to be hard attracting unpaid contributors for it.

If you need stability and long term support as a customer, you have companies like RedHat or SUSE whose entire point is providing 10+ years maintenance on these components.

Re:Linux gives up on 6-year LTS kernels, says they’re too mu... by structural on Wednesday September 20, 2023 @10:38PM (#37592632)
Unfortunately, none of these companies providing 10+ years of maintenance are doing so for most embedded devices. We either need to get SoC vendors to update their kernel baselines regularly This is hard, we've been trying for a decade and not seen much progress. Alternately, get them to backport fixes and patches (there's actually been quite a bit of progress here in getting them to actually take updates from the stable kernel at all! And that's getting thrown away now...)
Re:Linux gives up on 6-year LTS kernels, says they’re too mu... by worthless-trash on Wednesday September 20, 2023 @10:57PM (#37592732)
If they got their fixes upstream , they would be pulled into the same build tree that centos and rhel uses.
Re:Linux gives up on 6-year LTS kernels, says they’re too mu... by dcow on Wednesday September 20, 2023 @11:37PM (#37592938)
Which really makes you understand why the lgpl was a defeat.
Re:Linux gives up on 6-year LTS kernels, says they’re too mu... by tremon on Friday September 22, 2023 @08:53AM (#37611365)
What do you mean? The Linux kernel isn't licensed under the LGPL.
Re:Linux gives up on 6-year LTS kernels, says they’re too mu... by qznc on Thursday September 21, 2023 @01:15AM (#37593458)
The effect of EU’s Cyber Resilience Act will be interesting. It requires maintenance, at least for security fixes.
Re:Linux gives up on 6-year LTS kernels, says they’re too mu... by athrun on Thursday September 21, 2023 @01:41AM (#37593611)
Exactly. It sounds like currently there's no money to be made supporting old embedded devices (in the consumer space at least), because no one is on the hook for long term maintenance.

Regulations _could_ change the incentives, and create a market for long term servicing. Regulations are hard to get right though...

Re:Linux gives up on 6-year LTS kernels, says they’re too mu... by WJW on Thursday September 21, 2023 @03:28AM (#37594305)
Old devices getting support from the Linux team is only one of the ways this can play out though. Some other ways I can think of:

- Old devices are phased out sooner. - Moving away from linux towards proprietary embedded OSes that do provide support. - No doubt some companies will try just ignoring the regulations

Re:Linux gives up on 6-year LTS kernels, says they’re too mu... by danieldk on Thursday September 21, 2023 @03:50AM (#37594477)
Or maybe vendors will be incentivized to actually upstream kernel patches, plus stop making 10 different models every year for weird market segmentation reasons.
Re:Linux gives up on 6-year LTS kernels, says they’re too mu... by ladyanita22 on Thursday September 21, 2023 @05:08AM (#37595089)
Nobody will move out of Linux, and old devices won't be phased out sooner, at least not in s significant manner.
Re:Linux gives up on 6-year LTS kernels, says they’re too mu... by robertlagrant on Thursday September 21, 2023 @06:04AM (#37595529)
They could also provide the devices without an OS, and point you at the recommended open source ISO to download.
Re:Linux gives up on 6-year LTS kernels, says they’re too mu... by TheLoafOfBread on Thursday September 21, 2023 @07:11AM (#37595964)
If it is not standard x86, then good luck.
Re:Linux gives up on 6-year LTS kernels, says they’re too mu... by bee_rider on Thursday September 21, 2023 @11:54AM (#37599529)
“Old devices are phased out sooner” seems like an OK solution with some caveats.

It is nice that it makes the cost of not supporting things visible to the users. Assuming “phased out” means the device will actually stop operating; “Company X’s devices have a short lifetime” is an easy thing for people to understand.

I suspect consumers will look for brands that don’t have this reputation, which should give those well behaved brands a boost.

Although, if it does turn out that just letting devices die is the common solution, maybe something will need to be done to account for the additional e-waste that is generated.

Moving toward proprietary OSes; hey, if it solves the problem… although, I don’t see why they’d have an advantage in keeping things up to date.

It is possible that companies will just break the law but then, that’s true of any law.

Re:Linux gives up on 6-year LTS kernels, says they’re too mu... by fnordpiglet on Thursday September 21, 2023 @12:30PM (#37600075)
This won’t make more money available for supporting old devices, it’ll just make the long term profitability of any device significantly lower and therefore less competition and innovation.

A smarter regulation would have been required non-commercial use firmware source disclosures to allow non competitive long term maintenance by owners.

Re:Linux gives up on 6-year LTS kernels, says they’re too mu... by graemep on Thursday September 21, 2023 @09:04AM (#37597038)
Who is responsible for complying with it? If a Chinese or American manufacturer of an embedded device that does not have a presence in the EU fails to provide updates what happens?

How many of the companies producing this stuff have the skills to fix kernel security bugs?

It will end up being tickbox regulatory compliance and will create barriers to competition, especially from FOSS: https://pyfound.blogspot.com/2023/04/the-eus-proposed-cra-la...

Re:Linux gives up on 6-year LTS kernels, says they’re too mu... by nudgeee on Thursday September 21, 2023 @06:34AM (#37595721)
Isn’t this what the Civil Infrastructure Platform (CIP) initiative [0] was also proposing? Maintenance of Linux kernels on the 10+ year horizon aimed at industrial use cases. Has backing from Toshiba, Hitachi, Bosch, Siemens, Renesas, etc, though a marked lack of chip vendors as members (apart from Renesas). Not really sure how well it is going though.

[0] https://wiki.linuxfoundation.org/civilinfrastructureplatform...

Re:Linux gives up on 6-year LTS kernels, says they’re too mu... by pxc on Thursday September 21, 2023 @07:48AM (#37596252)
> Unfortunately, none of these companies providing 10+ years of maintenance are doing so for most embedded devices.

But why do these devices need special kernels anyway? Isn't that the real problem?

Re:Linux gives up on 6-year LTS kernels, says they’re too mu... by Const-me on Thursday September 21, 2023 @08:08AM (#37596429)
Linux kernel doesn't have ABI for device drivers. The device manufacturers either can't or won't publish the drivers as a part of Linux kernel, that's why they fork Linux instead.
Re:Linux gives up on 6-year LTS kernels, says they’re too mu... by kelnos on Thursday September 21, 2023 @02:25PM (#37601805)
Not sure who the "we" is that you refer to, but Google (and Samsung, and other Android manufacturers, as well as companies building other Linux-based embedded/IoT devices) could band together and create a "Corporate Embedded Linux Consortium", and pool some money together to pay developers to maintain old kernel versions.

If the mainline kernel devs are uncomfortable allowing those to be official kernel.org releases, that's fine: the CELC can host the new versions themselves and call the versions something like "5.10.95-celc" or whatever.

I don't get why this is so difficult for people to grasp: if you want long-term maintenance of something, then pay people to maintain it long-term. It's a frighteningly simple concept.

But yes, it'd be better for SoC vendors to track upstream more closely, and actually release updates for newer kernel versions, instead of the usual practice of locking each chip to whatever already-old kernel they choose from the start. Or, the golden ideal: SoC vendors should upstream their changes. But fat chance of that happening any time soon.

> (there's actually been quite a bit of progress here in getting them to actually take updates from the stable kernel at all! And that's getting thrown away now...)

I found this statement kinda funny. If the original situation was that they wouldn't take updates from the stable kernels, then what were all those unpaid developers even maintaining them for? It's bad enough that it's (for most people) unrewarding work that they weren't getting paid for... but then few people were actually making use of it? Ouch. No wonder they're giving up, regardless of any progress made with the SoC vendors.

Re:Linux gives up on 6-year LTS kernels, says they’re too mu... by leonheld on Monday September 25, 2023 @06:32PM (#37651636)
>SoC vendors should upstream their changes. But fat chance of that happening any time soon

I honestly do not understand why SoC vendors don't put the extra 1% effort in upstreaming their stuff. I've seen (and worked with) software that is lagging 3 to 4 years behind upstream developed by these vendors and if you diff it against upstream it's like 10 small commits, granted, these commits are generally hot garbage.

Re:Linux gives up on 6-year LTS kernels, says they’re too mu... by throwawaymqsh on Thursday September 21, 2023 @05:09AM (#37595105)
> it's unfortunately not sexy work

What comprises sexy work in programming?

Re:Linux gives up on 6-year LTS kernels, says they’re too mu... by xnorswap on Thursday September 21, 2023 @05:20AM (#37595192)
I don't know what the definition of "sexy work" is, but rewarding work in programming is solving interesting problems.

Backporting fixes isn't generally interesting problem solving.

Re:Linux gives up on 6-year LTS kernels, says they’re too mu... by rkta on Thursday September 21, 2023 @06:52AM (#37595849)
And so everyone has his own kink. I'd love to backport patches maintaining some legacy code base.
Re:Linux gives up on 6-year LTS kernels, says they’re too mu... by UncleMeat on Thursday September 21, 2023 @10:59AM (#37598623)
This is the root of so much of our software quality problem. “I want to work on something shiny” outweighs “I have pride in this software and want to keep it healthy.”
Re:Linux gives up on 6-year LTS kernels, says they’re too mu... by xnorswap on Thursday September 21, 2023 @11:29AM (#37599136)
Personally I love working on legacy software, I actually dislike greenfield projects, but even in the context of legacy software and system maintenance, backporting fixes would still not rate highly or provide much in the way of interesting work for me.
Re:Linux gives up on 6-year LTS kernels, says they’re too mu... by tremon on Friday September 22, 2023 @08:56AM (#37611396)
I'd say there's enough software developers that enjoy doing the latter. It's mostly the external motivation (both in community standing and in payments) that push people to shiny new things.
Re:Linux gives up on 6-year LTS kernels, says they’re too mu... by samtho on Thursday September 21, 2023 @05:15AM (#37595161)
New features, typically.
Re:Linux gives up on 6-year LTS kernels, says they’re too mu... by esrauch on Thursday September 21, 2023 @08:04AM (#37596392)
Are you flagging the word "sexy" or are you asking whether some important projects are fun and exciting and other important projects boring?

Surely maintaining 40 year old bank Cobol code is important but it's not considered fun and exciting. Rewriting half of skia from C++ into Rust is arguably not important at all but it's exciting to the point that it reasonably could make the front page of HN.

Re:Linux gives up on 6-year LTS kernels, says they’re too mu... by neurostimulant on Friday September 22, 2023 @03:38AM (#37609073)
> If you need stability and long term support as a customer, you have companies like RedHat or SUSE whose entire point is providing 10+ years maintenance on these components.

Is that even feasible for projects like the Android kernel that distributes their fork to vendors when RedHat forbid redistribution of their source code?