Slashdot Mirror
Linux 2.2.8
KrON writes "Linux 2.2.8 Is being upp'ed to mirrors as we speak...
" A few people have noted that a 2.3 directory
has appeared on some of the mirrors, although it is
empty.
← Back to Stories (view on slashdot.org)
← Back to Stories (view on slashdot.org)
Pop over to www.linuxhq.com. If they don't have a change summary up yet, there should be a link to the cutting edge linux site that usually has them.
...to discover that Linus has taken a patch you
sent out twelve hours before marked "please test"
and stuck it into the official kernel, without
saying a word.
Is USB supported? No.
But that doesn't mean it won't be. The code is out there, ready for nice people to test. Uncomment it from config.in and have a go at it, and be sure to check out the project info at the new Linux-usb web site.
I used to play the upgrade-with-every-kernel game, too. That got old, so now I just keep the latest release kernel compiled and lilo set to boot it in case my box crashes (hasn't happend since I got a clue and stopped messing about as root), the power goes out (doesn't happen too frequently), I add/upgrade hardware, or I need to install a kernel that fixes bugs/exploits. I've been running 2.2.5 for 38 days now. I'm going to install more RAM this weekend, so 2.2.8 will go up.
I keep my thirst for upgrades/beta code quenched by occasionally booting my Mac into the latest dev version.
Do you have the binutils rpm installed? the as86 assembler is part of that package....
There's an easy way to get long uptimes - don't upgrade the kernel unless you don't have to. It amazes me all the people whining about HAVING to upgrade the kernel everytime a new one comes out. You don't have to and if you've got a configuration that is working fine, doesn't contain bugs that cause it to crash or have bugs that lead to security exploits, then just leave it be for goodness sake! I played the kernel upgrade game with the 2.1.x on my own workstation but my servers here behind the firewall are running whatever they are running and they'll stay that way until someone comes out with an exploit that can be launched from a Macintosh (we have almost entirely Mac clients) or until I absolutely need one of the new kernel features to do something I need to get done.
I believe the scheduler updates did make it.
There is a lot of new scheduler code in, certainly, and I remember all of the discussion about scheduler issues, but could someone please summarize exactly what they do? Is it just to handle high-load situations with a lot of processes (i.e. Apache), or does it fix a scheduler bug of some kind?
I haven't found a Changelog either, but I went through the diff and noted a lot of changes in the USB tree. You still can't pick it from the menu though (as far as I can tell).
Why waste your time getting the tarball and then doing a 'make config'. The mirrors are fast, but they aren't that fast (and I'm sure your typing isn't either). Get the patch and 'make oldconfig'.
Ummm
/dev
"There's no secret. You just press the accelerator to the floor and keep turning left." -- Bill Vukovich
That is probably the best combination of having the latest kernel, and keeping uptime. I'm running 2.2.2 (with the bug/exploit/whatever that people are talking about), and having 70 days uptime now (the last time it went down was when somebody unplugged the power). But I will probably compile 2.2.8 (aka 2.3.0) any time soon, just in case...
/* Steinar */
(This comment is of course GPLed.)
Could someone kindly point me to a changelog? I've looked and I can't seem to find one. :(
This sig is false.
Rumors say that this is the first version in the 2.2.x series where some problems with the scheduler (that existed since the late 2.1.1xx kernels) are finally ironed out.
I'd like to see what difference this one makes on the 'dreaded' Quad PIII/Quad 100mbit/Hardware RAID/>1GB RAM configuration that is soo popular lately in MS-sponsored 'benchmarks'...
Btw: Who thinks like me that it may be time for one or more larger Linux organisation (like Linux International, RedHat labs, and/or Suse) to setup a high-performance benchmark lab that can be used for in-house benchmarking, and kernel development and optimization of Linux by our cutting-edge Linux developers (linus, alan, david, andrea, donald, stephen, andre, richard, rick, and the o-so many others, including the samba, apache, and squid guys).
--- Hindsight is 20/20, but walking backwards is not the answer.
I put some debs of the new kernel up at my ftp server. They don't have SCSI, SMP, or ISDN, but they've got most everything else.