Your right Alan. If I had been upgrading my Linux over the past
year with each new 2.1.x then 2.2.0 might not be a big step. But coming
from 2.0.36 it is a huge change, and as you say it may take lots of new
rpm files to ever use the new kernels.
My best route is to shut up and enjoy what I have now. Let the
knowlegable people do the right thing. I recall a couple of years ago
hearing guys say they were still using kernel 0.2.3 and had no plans to
upgrade. Why upgrade since it all works fine?
On Sat, 6 Feb 1999, Alan Crosswell wrote:
} Gee Karl, Isn't that a little obnoxious to say about free software?
}
} I'm running ny RedHat 5.2 systems with kernel 2.2.1-ac4 right now:-)
} But then I've been running 2.1 kernels for the last year and I ran
} every one of the nine 2.2.0 pre release kernels, including the last
} one which broke ide-scsi emulation:-(
}
} It should go without saying that if you are going to grab a new kernel
} in advance of the packagers of RedHat or any other distribution having
} yet made it available with their package then you should expect a few
} hard knocks. That's why it's called the bleeding edge. RedHat 5.2
} pre-dates kernel-2.2. When you find a kernel-2.2* RPM at the RedHat
} 5.2 updates site, then I would say the folks at RedHat have integrated
} the kernel into the 5.2 distrubution. You will probably find 20 other
} rpms there that need to be updated to match the new kernel.
}
} 73 de Alan N2YGK
}
}
}
Best wishes
- Karl F. Larsen, [EMAIL PROTECTED] (505) 524-3303 -
