[101069] in RedHat Linux List
Re: 2.0.36-1 kernel upgrade question
daemon@ATHENA.MIT.EDU (Jyan-Min Fang)
Tue Nov 24 14:10:07 1998
Date: Tue, 24 Nov 1998 14:11:15 -0500 (EST)
From: Jyan-Min Fang <fang@beamer8.physics.yale.edu>
To: "Sven N. Thommesen" <sthomme@aub.mindspring.com>
cc: redhat-list@redhat.com
In-Reply-To: <199811241758.MAA26962@camel8.mindspring.com>
Resent-From: redhat-list@redhat.com
Reply-To: redhat-list@redhat.com
why not just use
rpm -Uvh kernel-headers-2.0.36-1.i386.rpm kernel-source-2.0.36-1.i386.rpm
to upgrade the kernel source and headers file? no need to leave the old
source and headers around. After all, you still have to recompile the
kernel if you install the source and headers, don't you?
I think "rpm -ivh" is suggested for the kernel-2.0.36-1.i386.rpm and
kernel-modules-2.0.36-1.i386.rpm.
Jyan-Min Fang
"Today, I consider myself the luckiest man on the face of the earth"
--- Lou Gehrig --- Go, Yankees!
On Tue, 24 Nov 1998, Sven N. Thommesen wrote:
>
> Just installed Apollo, and decided to upgrade with the errata packages.
> Since there are new versions of the kernel (2.0.36-1 upgrade from
> 2.0.36-0.7), I decided to do that one as well. I unearthed an ancient
> document on redhat's web site on how to upgrade kernels with rpm, and tried
> to follow the recipe. No joy.
>
> Here's what happened:
>
> # rpm -ivh kernel-2.0.36-1.i386.rpm kernel-headers-2.0.36-1.i386.rpm
>
> kernel ######################
> kernel-headers cannot be installed
> /usr/src/linux-2.0.36/include/asm-i386/bugs.h
> conflicts with files from kernel-headers-2.0.36-0.7
> <snip: multiple messages of the same sort>
>
> OK, in /usr/src we have directory linux-2.0.36 and link 'linux' pointing to
> that directory. I tried to rename the linux-2.0.36 directory to something
> else, but I still got the same error messages. Q: is there some hidden link
> to that directory sitting somewhere else?
>
> Being paranoid, I did
>
> # cp -a linux-2.0.36 linux-2.0.36-0.7
> # rm linux
>
> Then
>
> # rpm -ivh --force kernel-headers-2.0.36-1.i386.rpm
>
> which went fine. Result: the directory /usr/src/linux-2.0.36 had been
> updated with new files.
>
> Now, the question: IF the include files for 2.0.36-1 are different from
> those for 2.0.36-0.7, will the old 2.0.36-0.7 kernel now boot ??? (I don't
> want to risk finding out the hard way ...) If so, doesn't Redhat have some
> more work to do re: making rpm based kernel upgrades painless?
>
> [If the upgrade had been to 2.0.37, of course, a new directory of that name
> would have been created under /usr/src and the question does not come up.]
>
> ANYHOW, here's my take on upgrading from 2.0.36-0.7 to 2.0.36-1. Those who
> see errors, please point them out. This procedure worked for me -- both old
> and new kernels boot.
>
> // ----------------------------------------------------
>
> # cd /usr/src
> # rm linux
> # cp -a linux-2.0.36 linux-2.0.36-0.7
>
> # cd /updates/kernels
> # rpm -e kernel-iBCS [don't need that one]
> # rpm -e kernel-pcmcia-cs [nor that one]
> # rpm -ivh kernel-2.0.36-1.i386.rpm
> # rpm -ivh --force kernel-headers-2.0.36-1.i386.rpm
>
> # cd /usr/src
> # rm linux
> # mv linux-2.0.36 linux-2.0.36-1
> # ln -s linux-2.0.36-1 linux
>
> # cd /etc
> # vi lilo.conf [add a stanza for the new kernel vmlinuz-2.0.36-1]
> # /sbin/lilo
>
> # shutdown -r now
>
> // -------------------------------------------------------------
>
>
> --
> PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
> http://www.redhat.com http://archive.redhat.com
> To unsubscribe: mail redhat-list-request@redhat.com with
> "unsubscribe" as the Subject.
>
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com http://archive.redhat.com
To unsubscribe: mail redhat-list-request@redhat.com with
"unsubscribe" as the Subject.
