On Sun, 2006-09-24 at 22:59, Matthew Saltzman 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. > > How would the kernel RPM know? It can't depend on the NVidia module. How would anyone know? If lsmod says a module is loaded and you can't get that module for a new kernel it's probably not a real good idea to make that new kernal the default for the next boot. > You can set UPDATEDEFAULT in /etc/sysconfig/kernel---that gives you some > manual control. You could, if you knew yourself that a needed module wasn't available. But you probably don't know that without using something like yum to check... -- Les Mikesell lesmikesell@xxxxxxxxx
