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)
/. 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
Not everyone plans on upgrading to 2.6.0 the moment it comes out.
It's hard to be religious when certain people are never incinerated by bolts of lightning.
Because some ppl are still running 2.4 in production environments...the headline is actually kinda wrong...the kernel will actually have new releases...they will just be maintanence releases...only, no new drivers, etc...just bug fixes...
For instance, there was a new release of the 2.2 kernel as early as March of this year.
Some people like doing fast development and implementing new features. Others like fine-tuning, perfecting what has gone before.
As there needs to be both progress, and stable platforms to work with, this multiple-tier system seems just about right to me.
Some of the changes in 2.6 are keeping me from upgrading right now. :)
- change in mouse behaviour (speed, access to extra buttons)
- some 3rd party modules not updated (nforce2 nic drivers, vmware)
- I've heard cd burning has issues
- I can updated the 2.4.x kernels without any huge worries that my remote server will blow up and require me to get some co-lo monkey to try to fix it
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.
That's why you're not in charge of a mission critical production environment. Those who are know that an increase in performance is not worth a decrease in reliability. 2.6.0 is not going to be as stable and reliable as 2.4.23 is, just as 2.4.0 wasn't as stable as 2.2.18.
It's hard to be religious when certain people are never incinerated by bolts of lightning.
Did you miss the early 2.4.x kernels? The 2.4 kernel was nicknamed "the kernel of pain" for a reason. The VM madness was so horrid where I work -- it could be relied upon to clobber MySQL every time the load got moderately high -- that we immediately rolled back to whatever the latest 2.2.x kernel was at the time.
The fact that Linux is the product of an open development process certainly improves code quality, but it doesn't mean that all of the major bugs have been worked out before it's been subjected to the full power of real world production use.
Proud member of the Weirdo-American community.
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.
>Your assumptions here seem to be more like guesses.
No it's right on the money. Unless you are waiting for some specific feature, a business with mission critical application/services will not upgrade to a newly released OS.
The Apache Software Foundation found this out when they released 2.0. After six month, very little sites were running Apache 2.0. It wasn't because it was bad product, it was simply because 1.3.x worked pefectly for them.
Why upgrade when your site is running perfectly? When our site is down, we have to refund the customers money. That was about $10,000 a day. So is it worth upgrading productions site, when your current site is working perfectly, at a risk of $10,000 a day? I'd wait until 2.6.12+ or so before I'd even think it.
Now 2.6 on a development site ( mirror of production) is another issue. That's where 2.6 starts it life in our company.
Heck, Solaris 10 is about to come out, who's even upgraded to Solaris 8?
2D only.. so why do you have a radeon again? You should've saved yourself the money and bought a Matrox G450 or something for $30. It's got better/faster 2D accelleration I hear anyways. And it consumes a lot less power than Radeon or GeForce.
:)
But really. I need proper GLX support since I like to goof around with that stuff. And I refuse to use windows, because I don't feel like paying for it and I have ethical problems with stealing windows.
“Common sense is not so common.” — Voltaire