Am Montag, den 12.06.2006, 15:36 +1000 schrieb Danny Yee: > I was a bit shocked to notice that yum did this overnight: > > Jun 12 05:49:27 Erased: kernel > Jun 12 05:49:55 Installed: kernel-smp.i686 2.6.16-1.2133_FC5 > Jun 12 05:50:12 Installed: kernel.i686 2.6.16-1.2133_FC5 > Jun 12 05:50:13 Updated: autofs.i386 1:4.1.4-25 > Jun 12 05:50:18 Erased: xorg-x11-drv-nvidia > Jun 12 05:50:31 Erased: kmod-nvidia-smp > > In order to put the latest kernel onto my machine, it not only removed > the older kernel (which shouldn't happen, according to my understanding > of yum.conf defaults) but also, along with that, the nvidia modules. > This stops X working... Interesting. Well, the behavior in general is by design: The installonlyn-Plugin for yum will remove older kernels and yum of course will remove all things depending on it. In this case: kmod-nvidia-smp and xorg-x11-drv-nvidia, because a newer kmod wasn't available for updating (is is now -- sorry, livna can only starting building modules when the kernel becomes available and livna maintainers need some sleep now and then, too. The situation might improve if we had more contributors that help maintaining the drivers). Anyway: The plugin doesn't remove the currently running kernel, which means in this case: there was no nvidia-kernel-module for the current kernel installed. The init script of xorg-x11-drv-nvidia should disable the nvidia driver in that case, so "This stops X working..." should not happen. CU thl
