Slashdot Mirror
Linux 2.5.2 Kernel Released
valdis writes "Amazing.. it's been out over 3 hours and not discussed to death. Well, maybe there's not as many bleeding-edge crazies out there. But if there are, here's what's new. You can get it at the usual place, but please use the mirrors if you can."
Apart from the entire 'slashdot is not freshmeat'-discussion I'd like to note, that maybe slashdot should not mention the URL to the kernel archive, but only the URL for the mirrors-list. I'm sure everyone able to compile and use a 2.5.x kernel is able to find the correct download directory, should he be confronted with a mirror list.
Those of you anxious to contribute by testing I suggest you get acquainted with the following sites:
Linux Kernel Mailing List FAQ (a must read before submitting bugs or oopses)
Good site about kernel hacking (not just for newbies either)
1 Earth is warming, 2 It's us, 3 it's royally bad, 4 we need to take action NOW
I know that this is a troll, but I'll bite: If you want to use Linux, you need to buy Linux-compatible hardware. Just like you wouldn't by a winprinter for a mac or an iPOD for win32 (yet), you shouldn't buy stuff that you know they don't work or work well under linux. This has been pretty well documented.
Instead of bitching around in message forums with your 24.6k modem connection, why don't you spend the time researching what works under linux and what doesn't. Maybe you would have found that there are card readers for every digital film format (compact flash, smartmedia, memorystick, sd etc) that work under linux.
Or maybe, if you can afford "the outrageous price" for the HP printer, you can afford a win32 CD and perhaps then _you_ could do something more than "practice networking skills and use the internet! Whopity-friggin doo!". Or even a mac (which are not expensive compared to a PC. definetly not -especially the imacs).
"I'll do everything within my power, be it donating money to carrying your kids to soccer practice, if you folks will just start writing drivers!"
How about stop bitching and be thankful to the people that _have_ written the million lines of code (including drivers) that make linux usable and enjoyable for us. Oh and start running windows. I have a feeling you two will get along just fine.
Definitely - but you probably won't notice much difference on most machines - his scheduler was intended to address problems particularly with huge systems. A mere 1-CPU or 2-CPU machine isn't going to see the real benefits.
Which isn't to say the patch is worthless on anything less than 4 CPUs - apparently it beats the old scheduler on all benchmarks. But for most of us, scheduling doesn't take a lot of CPU anyway.
"How can you claim that you are anti-crack, while still writing a window manager?" — Metacity README
http://people.redhat.com/mingo/O(1)-scheduler/
I must say that after using it for a few days, I'm impressed. It totally changes the characteristics of multiprocess servers like Apache and PostgreSQL under high load. For example, I've run ApacheBench against a mod_perl script that queries a pgsql database, in the new scheduler I get a mean response time that is N*1.05*concurrency with a standard deviation of less than 1% of the mean. In the old scheduler I'd get a mean that is N*1.07*concurrency with a sd of up to 75% of the mean. So in other words you get essentially the same throughput with both schedulers (O(1) appears slightly faster in my limited testing). But what's more important is that in the O(1) scheduler everyone is treated equally - they all get served in 1.05*N*concurrency, no more, no less -- while with the old scheduler some requests get a response that's 1*N and others get a response all the way up to 4*N*concurrency.
IMHO, it's better to give everyone an equal level of service than to randomly favor one group of users over another.
I don't think it's in the kernel
According to the change log ingo's scheduler changes _are_ integrated.