Slashdot Mirror
Kernel 2.4.23 Released
MikeCapone writes "As if we didn't already have enough articles about Linux kernel releases, Marcelo Tosatti has released the final 2.4.23 Linux kernel. Check out the changelog at Kerneltrap."
← Back to Stories (view on slashdot.org)
I'm still using 2.4.18!
The ChangeLog is a long one, I wonder if the patches will be ported to 2.6 as well....
/. now announces releases of non-major kernels? Seems odd to me to announce the release of the 2.4.23 kernel, now maybe if it were the 2.6.0 kernel, that would be something to talk about. . .
YOU'RE WINNER !
Another lame blog
..really any point upgrading? 2.6 should be out in a couple of weeks.
With this long changelog, I don't know what's important and what is not. Is there any reason to update from 2.4.22?
ftp.us.kernel.org and ftp.ca.kernel.org aren't updated yet, so I guess we're free to slashdot the main kernel.org server back to the stone age? :)
I'm a newbie to linux kernel updating. Would anyone like to educate me on the process, or point me to a place I can learn.
-Kevin
No, it's better...it runs MPlayer...which plays realmedia without all of the Real Networks ads!!!
Irony??? I've got maids to do that.
I know I'm going to be modded down for this, but everytime somebody mentions the kernel I can't help but picture Tux with a big bucket of Pop-Corn. I know it's wrong, but I just can't help it.
how is this funny?
Hopefully, this fixes some nasty kernel oopses that occur when using the pl2303 usb-serial driver. I've had a lot of trouble with this when using my Deluo GPS.
on the 2.4 and 2.6 releases? with 2.6 so close to release ... is there much point to having a 2.4+x release out? are the changes made to the new 2.4 already in the 2.6, or is it still newer stuff which hasnt been put into 2.6?
Belive me, this is better than most of their jokes....
ITS a PENGUIN: We are cool and hysterical.... No you're not. Ocelot, maybe, buy penguins are just passe...
Still no cryptoloop. CryptoAPI is in there. but the darn cryptoloop driver, which makes cryptoAPI actually useful isn't in there yet.
What a waste, all my USB keys and compact flash are encrypted. I guess I'll just see if OpenBSD supports my videocard yet. *sigh*
“Common sense is not so common.” — Voltaire
I don't want to sound like a troll, but does anybody else this comment is wholly inappropriate to be included in the text??
If I had written that as a post, I'd get tossed into -1, Flamebait before you know it. Yet the editors are seemingly bigger flamebaiters and trolls than the readers.
Seriously, if michael has such a problem with Debian, write a comment, and face the moderation and the replies. If he can't do that, then don't bother creating shit like that.
and that realplayer had linux versions on year zero or something..
when it was still 'the thing' for internet radio over dialup.
Was there ever a 2.5 Kernel? Did they ever do anything in that area or was that tossed into an enternal void? Just curious...
Oh how I hate the colonel, with his wee beady eyes and the smug look on his face... Oh, you're gonna buy my chicken, oooooohhhhhhhh!
"Anyone that has ever gotten an idea based on any of my work and done something better with it-good for you."--J.Carmack
How short our memories are.
Remember the early 2.4 series? Remember the problems? The major rewrites of the VM?
Ah but this is slashdot. Thinking things through isn't really practiced much here.
c-span==masochistic++
i was using dos shell last year this time. i too, am using 2.4.18 (flooppy/bf2 build via Debian-Woody). i'm wonderring if there/where is 2.4.20 ...or if this is something that i'll have to trust the debian people to make sure it's stable before they allow it.
or, i could just go and look for it.
i think i may just do that.
so yes...point of this post: is there a 2.4.20 ?
GENERATION 26: The first time you see this, copy it into your sig on any forum and add 1 to the generation.
I'll be waiting for 2.6 to mature before I take the plunge, I stayed on 2.2 after the 2.4 release and I was VERY happy to be working away without fear as thousands of 2.4 users were scared to unmount drives, had to deal with a broken-and-fixed-and-swapped VM, and other minor stupidity.
I for one don't really see anything good for _ME_ in 2.6, the parts of the kernel I use are actually in better repair under 2.4 (framebuffer and OSS, mostly). I've tried recent 2.6-test builds, and the small performance gains and better 'full throttle process niceness' were barely noticeable to me.
I'll stick to 2.4 until 2.6 is in good-enough shape to move comfortably into. I'll let everyone else sweat it out.
I'm not AGAINST 2.6, I welcome it's development and release, but 2.4 is as great a product as it ever was, and I can wait.
"Sometimes, I think Trent just needs a cup of hot chocolate and a blankie." -Tori Amos on Nine Inch Nails
No it wouldn't. Most of the developers would sit there with a calculator converting the hex to decimal just to understand what the hell is going on. This would be a huge waste of time and productivity.
.h and .c files from the server and upload the assembly files instead. But, even that is not the best solution, we should just upload the binary files and let the true hackers continue on in straight 1s and 0s. I bet development would increase at an exponential rate then. Oh wait, no it wouldn't.
But, if you're so hell bent on your idea, why stop there? Run all the code through gcc and have it generate assembly output. Then remove all the
Humans like things they can understand, computers like things computers can understand. Since it is humans developing the software, it is the compilers job to understand how to translate (and the people who write the compilers.)
-- Fighting mediocrity one bad post at a time.
When will the Cisco drivers for WiFi cards be fixed? It's pretty annoying to have to use modules from older Kernels to get a Cisco card working...nobody seems to care though !
Anyone else find it interesting that Intel is working on x86-64 code? Or am I reading too much into this...
len.brown:intel.com:
o [ACPI] fix x86_64 build errors
o [ACPI] fix x86_64 !CONFIG_ACPI build
o 2.4.23 build x86_64 build fixes
o x86_64 build fix from previous cset
o [ACPI] sync some i386 ACPI build fixes into x86_64 to fix !CONFIG_ACPI build
(Note some non-x86-64 changes omited from excerpt)
Wishful thinking probably.
If he merged them, I would no longer have to fight my way around these two to manage to squeeze GrSecurity and FreeSwan on top, since the GrSecurity and FreeSwan crowd would have already done the work of making their patches compatible with a pre-emptive and low-latency enabled vanilla upstream source. For some reason, beleive I would not be the only one to cheer up if this happened.
Mario? Would you happen to be reading this thread and willing to explain your position in regards to this?
Software is not supposed to be about how to work around a useability issue. - Ken Barber
lol. :)
and kudos on the nice computer, too.
that's great. best reply so far
GENERATION 26: The first time you see this, copy it into your sig on any forum and add 1 to the generation.
to debians uber-high standards. this comes as a total shock...i thought for some reason the kernel used was fairly up to date, the next kernel 2.4.19 for those who want to toy with the new stuff(sarge), or 2.5.x for the people with hardware to spare...(sid) but i am mistaken, it seems. :)
GENERATION 26: The first time you see this, copy it into your sig on any forum and add 1 to the generation.
Nothin like a new kernel to break the deadlock on stiff joints... I notice some much needed updates have been done to the pl2303 USB-Serial driver... which I use to talk to my cellphone (motorolla v100), but have had issues with... namely hanging, and not letting go of the device... I'm hopeing the fixes solved this bug... Just goes to show, its still very much a work in progress, and hopefully, the progress, and change, never ends.
Microft
-Beware of he who would deny you access to information, for in his heart, he dreams himself your master.
If I remember, I will post my results it here....
=========
Together, we will drive the rats from the tundra.
Ah well, to bad the all-new-and-shiny grsecurity for 2.4.23 isn't out yet.
But keep me as freak--I'd like to think I am. I don't think anyone else replies to me as much--and you even write more than I do in the original.
-Libertarian secular transhumanist
... you're wanting to leave your production servers to HIM??
[codifex@unknown codifex]$ uname; uname -r
Linux
2.4.23
Compile and install went pretty smooth except for the es1371 garbage... After I switched input core to compiled in instead of module that is... heh.
Recompiled my Vortex sound - no prob.
Downloaded latest NVidia driver - nice automatic configurator and installer - Bravo NVidia!
Good to go in record time. Linux just keeps getting better and better. Now to beat on it.
Codifex Maximus ~ In search of... a shorter sig.
I just compiled 2.4.23 in Fedora core1 and succussfully booted it. However, when I try to run kde I get the following error:
cannot set up thread-local storage: kernel too old for thread-local storage support
Can anyone help solving this problem?
Or anything, really. Let's see:
Obviously I like something about it, or I'd have left by now.
I'm not too happy with 2.0. I used it because it came packaged with an OS and just for once, in the interest of speed I relaxed my rule of always building Apache from source (which would have been 1.x, of course) and accepted the package. I had several weird problems with 2.x on 2 different machines. Random errors in mod_perl, which I spent a lot of time trying to nail down until I switched to 1.3.x, solving it. And the part that really pisses me off - Apache 2.x inserts a bunch of garbage into each line in the error log, and the docs say you can't turn this off. That was the last straw for me. I sincerely hope 1.3.x is maintained forever.
In all my experience with 1.3.x, I never felt the anger and frustration that commercial software can cause, but 2.x did it with that brain-dead misfeature.
Software is not supposed to be about how to work around a useability issue. - Ken Barber
Why the hell do you want packages? I use packages when they're available. When they're not, I compile. My system runs smoothly and there are no troubles.
This is probably one of the last 2.4 releases, I bet no one develops on 2.4 when 2.6 is out, (Maybe still getting those whines about that red hat patched 2.4.20 has bugs!)
2.6 needs much testing, and I think somewhere at 2.6.{2,3,4} it's pretty stable, because users don't have the guts to upgrade to anything with {pre,rc,test} on it.
I myself have been involved with testing since 2.5.60 something, and I can just say that the kernel devel team is doing a great work.
Quit slashdot today: http://www.cs.washington.edu/homes/klee/misc/slash dot.html
Kerneltrap.org also has good kernel news, and provides links to the discussion from the ML.
I have about 15 dual-processor machines with 1-2 GB that didn't work at all well with 2.4.x kernel. The memory management was simply crap. Forking a couple of copies of the program below consistently put the system into a permanent comatose state. (Search for 'kswapd problems' for discussion and ineffective patches.)
On the other hand 2.6.test11 works beautifully. For me, the 2.4 kernel is history.
int i; int k; char *j;
main(){
for (i=1;i2000000000;i*=2) {
printf("%d\n",i); fflush(stdout);
j = (char *)malloc(i);
printf("-- %d\n",j); fflush(stdout);
if (j == NULL) break;
for (k=0;ki;k++) j[k] = 1;
}
return 0;
}
Software is not supposed to be about how to work around a useability issue. - Ken Barber