On Wed, 12 Jan 2005 08:42:32 -0500 (EST), Matthew Saltzman <mjs@xxxxxxxxxxxxxxx> wrote: > On Tue, 11 Jan 2005, Dave Jones wrote: > > > On Tue, Jan 11, 2005 at 08:48:39PM -0600, Erich Noll wrote: > > > > > rpm -Uv kernel-2.6.10-1.737_FC3.i686.rpm > > > > Don't do this. Always rpm -i kernel rpm's, as using -U can > > really break things badly if something goes wrong. > > This problem is a bit different than usual, as the packages have the same > release/version numbers. No it is not. rpm -ivh --replacepkgs --replacefiles are the options to be used. > But this doesn't really help him out of his jam... > > This is exactly the moment (and almost the only moment) to use "rpm > --force". Boot to an older kernel (you do have an older kernel installed, > don't you?), then "rpm -Uvh --force kernel-2.6.10-1.737_FC3.i686.rpm". > Then reboot to the updated kernel. How is the person going to keep the old working kernel when you tell them to use rpm -Uvh --force??? rpm -Uvh wipes out every other kernel on the system and leaves you with a kernel that you do not know works. And as for 'force', this is very dangerous practice if you do not know what is going on. Please refrain from advising anyone to use this. I have detailed much better options to use in this case. N.Emile... -- Registered Linux User # 125653 (http://counter.li.org) Certified: 75% bastard, 42% of which is tard. http://www.thespark.com/bastardtest
