Re: rpm kernel update problem

[Dave Reed <dreed capital edu>]

> From: David Talkington <dtalk prairienet org>
> 
> 
> Ok, it's been awhile since I've tried to use rpm to update a kernel,
> and now I remember why I stopped doing it and rolled my own.  The
> problem which first turned me against kernel rpms is still present --
> certainly not insurmountable for an experienced user, but quite
> devastating for a newbie, and certainly not expected behavior.
> 
> I did what I suspect any normal user would do, which is to install a
> new workstation, mount and cd to the directory containing updates, and
> then do:
> 
> # rpm -Uvh *
> 
> And then reboot.  It works just fine, except that while the kernel is
> replaced with a new version, lilo.conf is not updated.  In this case,
> I forgot to check on it, LILO did not find the kernel it wanted, and
> the system failed to restart.
> 
> I hope that I'm overlooking something glaringly obvious, because this
> has been my experience every time I've tried to use rpm to update a
> kernel.  If only the old kernel were not removed (there's no earthly
> reason to delete it; it should _always_ be kept around until at least
> a successful reboot!), this would not be the catastrophic failure that
> it is.
> 
> - -d

That's why the directions on Red Hat's web site say to use: rpm -ivh
on the kernel RPM.

I think you need to boot with a rescue disk and run lilo. I can't give
specific instructions for doing this.

Good luck.

Dave