[NBLUG/talk] Re Installing kernel RPM update

HarryH forHarryH at hotmail.com
Sun Jan 11 22:11:02 PST 2004


Mark & Dustin,

Thanks for replying.  I tried rpm -ivh kernel-2.4.20-27.7 and it gave me the
multiple screen messages about file conflicts.  I assume this is due to the
fact that this version is already partially installed.  I am currently
running on kernel-2.4.20-24.7 and have a boot diskette for it in case.
This is what I plan to do:
1. Do rpm -e kernel-2.4.20-27.7 to back out the damaged version.
2. Do rpm -ivh kernel-2.4.20-27.7 to reinstall it.
3. Update grub.conf to ADD the new kernel specs in addition to the older
ones in case of an error.
4. Reboot to test.

I have read where RH says I do not need the kernel-headers & docs unless I
want to modify/compile the kernel - no thanks at this stage of my Linux
career.  Also, I understand rpm will let force " --force[!=0x74] the install
but I am concerned that it may break something given the current, partial
install of the desired kernel.

Any feedback appreciated,
Thanks,
Harry


----- Original Message ----- 
From: "Mark Street" <jet at sonic.net>
To: <talk at nblug.org>
Sent: Sunday, January 11, 2004 3:43 PM
Subject: Re: [NBLUG/talk] Re Installing kernel RPM update


> Do not do an UPgrade on a kernel with RPM....  It will break things.
>
> Do an rpm -ivh kernel-BLAH and install the kernel's side by side.  Reboot
and
> make sure the new kernel works, then remove the old kernel with an rpm -e
> kernel-OLDKERNELVERSION.
>
> I can't remember if kernel-headers is a required package for 7.2 or not...
> anyway.
>
> On Saturday 10 January 2004 23:46, HarryH wrote:
> > Hi,
> > Back on December 25, I did a "up2date -u" from the Red Hat Network for a
> > kernel update to my 7.2 machine.  The up2date process did not go to
total
> > completion, that is it could not run a "sh /sbin/grubby" as I had run
out
> > of "/"  directory space and it could not get to /sbin.  I can tell by
> > looking at /boot that not all is completed.  That problem is now fixed.
I
> > just tried to re-update the kernel with a "rpm -Uvh package name" (same
> > package and version) and it complained that the existing kernel files
> > conflict with the fresh rpm package.  I tried to use the -F option but
that
> > did absolutely nothing.  Do I need to use the "-i" option in order to
force
> > the rpm to overlay the unsuccessful prior install?  Or, should I use the
> > "-e" to try and back it out first?  The best I can tell, the machine is
> > running on the prior version of the kernel.
> >
> > Any info appreciated,
> > Harry
>
> -- 
> Mark Street, D.C.
> Red Hat Certified Engineer
> Cert# 807302251406074
> --
> Key fingerprint = 3949 39E4 6317 7C3C 023E  2B1F 6FB3 06E7 D109 56C0
> GPG key http://www.streetchiro.com/pubkey.asc
>
> _______________________________________________
> talk mailing list
> talk at nblug.org
> http://nblug.org/mailman/listinfo/talk
>



More information about the talk mailing list