On Fri, Jan 25, 2008 at 08:13:23PM -0500, David Kramer wrote: > I have a relatively new F8 box. I let the update notifier do its update > last night, and got a new kernel. However, there wasn't a matching nvidia > or lirc module. I know how these things happen, but I would have thought > my yum plugins would have prevented it from getting installed: > > # rpm -qa | egrep '(kernel|kmdl|kmod|yum-plugin)' > kmod-nvidia-2.6.23.9-85.fc8-169.07-1.lvn8 > mikmod-3.2.2-2.fc7 > yum-fedorakmod-1.1.10-1.fc8 > kernel-headers-2.6.23.14-107.fc8 > kmod-nvidia-169.07-1.lvn8 > ivtv-kmdl-2.6.23.9-85.fc8-1.0.3-135.fc8 > kernel-2.6.23.9-85.fc8 > yum-kernel-module-1.1.10-1.fc8 > yum-plugin-kmdl-0.7-9.fc8 > lirc-kmdl-2.6.23.9-85.fc8-0.8.3-73_cvs20071109.fc8 > kernel-2.6.23.14-107.fc8 > > Shouldn't yum-plugin-kmdl prevent a kernel from installing if the matching > kmdls are not available? No, because suppose a foo-kmdl is being swallowed into the kernel rpm from 2.6.40 to 2.6.41 or otherwise making an external kmdl unneccessary after a kernel upgrade. There wouldn't be any foo-kmdl for that kernel and yum-plugin-kmdl would block the update of the kernel for no reason. yum-plugin-kmdl's job is to make sure all kernels, old and new get the same kmdls if they exist and at an asyncronous time, e.g. it will detect kmdls shipping in later than the kernel rpm did. > Is there another way to accomplish this? Upgrading the kernel w/o kmdls is not a problem - booting into it may be, so just don't boot a long as the kmdls haven't made it to your system. Having said that there is an automated kmdl rebuild project for kmdl2 waiting to be released. It will allow you to have automatically dkmdls built by your own system if you want it to do so. -- Axel.Thimm at ATrpms.net
Attachment:
pgpj8PgSookY3.pgp
Description: PGP signature
