Posted by
CmdrTaco
on from the stuff-to-download dept.
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.
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.
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.
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 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.
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.
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.