On Sun, 2006-09-24 at 19:53 -0500, Les Mikesell wrote: > On Sun, 2006-09-24 at 17:48, Ric Moore wrote: > > > > > > Yum shouldn't have removed the running kernel, so recovery > > > should have been a matter of hitting a key during reboot, > > > selecting the old kernel with the down-arrow key, and > > > hitting enter. Still, it would be nice if it didn't > > > break the system in the first place when it should be > > > moderately easy to detect that a new kernel isn't > > > going to work yet. > > > > Yeah, I went into yum and configured it to save 3 kernels, which is what > > I did back when, only it was that way just now. <sigh> > > The default 2 should have been enough unless you did two > updates that each installed a new kernel without rebooting > and noticing the problem. More than likely that is what happened, but I do reboot more frequently now than I ever did in the old days. There are far too many chancy apps stressing the kernel out just because of the potential horsepower of the processors to utilize. I want bigger faster toys and the envelope is pushed hard. Maybe we need a blue screen of death too... with a gut-shot penguin on it. Mea Culpa! Ric -- ================================================ My father, Victor Moore (Vic) used to say: "There are two Great Sins in the world... ...the Sin of Ignorance, and ...the Sin of Stupidity. Only the former may be overcome." R.I.P. Dad. Linux user# 44256 Sign up at: http://counter.li.org/ http://www.sourceforge.net/projects/oar http://www.wayward4now.net ================================================
