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."

Comments

No cryptoloop?

[OrangeTide]

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*

Re:Is there..

[sydb]

You've already been advised but let me add more weight.

You see that third number in the release? 2.4.x? It keeps going up, and the main reason for it going up is to fix bugs.

When the speed of increment slows, I can feel confident there are less bugs! Other people have suffered them, found them, and fixed them! Call me a freeloader...

Actually I have reported bugs in kernels before and got them fixed. But I don't find kernel bugs on production machines, I find them on test boxes.

Of course, if your don't care too much about stability on your box, that's fine, do what you want. But in that case, what is the point of your post? :-)

Re:Is there..

[dracocat]

I should not imagine even mission critical production environments sticking with 2.4 after 2.6 is released.

Nope. There is no way we will be moving to 2.6. The boxes we have running 2.4 now will be running 2.4 untill the day they die. I imagine any mission critical environments will be doing the exact same thing as we are.

With new servers you put into production, you may consider 2.6 depending on speed/feature requirements. But existing mission critical machines will never be upgraded.

Think about it, you have a machine and a system that is working. What exactly are you trying to fix? Make it faster? If it was too slow for you, you would have already bought more hardware. So, its not too slow, its been working fine and has been tested. You would have to be mad to upgrade the thing.

Mission critical boxes usually always keep the same kernel version until the day the die.

Why aren't pre-emptive and low-latency merged?

[Quietti]

Noticing that these two famous patches are already merged into kernel 2.6 and have received plenty of praises when they were first introduced to the 2.4 crowd before, I really wonder what's keeping Mario from merging them into 2.4 as well.

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?