Perhaps, but I'm less worried about the new features just incorporated, than I am about the fact that I'm still applying the same patches to 2.4.23 and 2.4.24 that I was on 2.4.7. Giant waste of a lot of people's time. And, who's to say we won't have a similar problem with 2.6?
As we all know, just because 2.6 has been released, doesn't mean the 2.4 series won't see more releases. I expect IBM to keep providing their patches to apply against those higher releases so that people who won't be installing 2.6 anytime soon aren't stuck with older, perhaps vulnerable kernels as time goes on. In that situation, we will _still_ be putting on the same patches as we have since the early 2.4 days. Not a good thing, and if it's something that can get fixed by some community activism, then why not? Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Arnd Bergmann Sent: Friday, February 06, 2004 1:08 PM To: [EMAIL PROTECTED] Subject: Re: Kernel 2.4.24 qeth.o - unresolved symdol show_trace -snip- AFAICT, it is unlikely that the new features from this code drop will ever make it into Marcello's tree because he is in maintainance mode. Nor will there be recommended code drops for Linux versions past 2.4.21 on developerWorks, because IBM is also in maintainance mode... Arnd <><
