Re: installing new kernel packages

[Paul E Condon <pecondon@peakpeak.com>]

On Wed, Jan 07, 2004 at 05:24:07PM -0800, Paul Yeatman wrote:
> I'm curious what are other peoples' practices when installing a new
> kernel package for a kernel version already installed (and the one you
> are likely already booted to).  The new package may be for the same
> kernel version but for a different release(?) of that version as with
> the newly released package(s) for kernel-image-2.4.18-1-*.  When one
> attempts this, s/he is confronted with an alarming message that is not
> very clear.  

Look at /lib/modules/ . It contains sub-directories that are named by
kernel version. With this knowledge, the message should not be so alarming.
Just rename the directory that you are about to clobber in order to get
it out of harms way.

> Because of this, I play it very safe and usually boot to a
> different kernel version, 'rm -rf' the /lib/modules of the kernel I'm
> replacing and then install the new package before booting back into the
> kernel of the new package.  I'm questioning whether this is really
> necessary.  I know that with Red Hat, new kernel packages are simply
> installed, no questions asked (if they are not on the "packages to
> skip" list).
> 
> 

-- 
Paul E Condon           
pecondon@peakpeak.com