Re: [suse-sles-e] keep old kernel after kernel upgrade

From: Matthias Eble (matthias.eble_at_mailing.kaufland-informationssysteme.com)
Date: Thu Mar 09 2006 - 17:19:34 CET 

Message-ID: <44105596.4030709@mailing.kaufland-informationssysteme.com>
Date: Thu, 09 Mar 2006 17:19:34 +0100
From: Matthias Eble <matthias.eble@mailing.kaufland-informationssysteme.com>
Subject: Re: [suse-sles-e] keep old kernel after kernel upgrade

Lars Müller schrieb:
> On Thu, Mar 09, 2006 at 11:48:58AM +0100, fritz fuchs wrote:
>
>>maybe a stupid question, i am sure i have read it
>>somewhere but i can't remember ..
>>
>>where can i configure to keep the old kernel after
>>upgrading via YOU to new kernel ?
>
>
> This is not possible with YOU.
>
> rpm -ivh <new kernel package> works well and also readjusts the sym
> links in /boot as required. Download the required Kernel RPM and
> install it from the command line.
>
> It's a good strategy to keep at least the last running kernel installed.
> From this point you'll never run in any Kernel update trouble. ;) Also
> ensure to remove unneeded Kernels with rpm -e kernel-default-2.6.5-7.204
> e.g. as you else might run in out of space of /boot.
>
> Lars

hi!
we are running a few servers on sp2 and want to update them using YOU.
The problem is, that we have to keep the kernel and glibc on sap
certification level (exactly SP3), but want to install the latest
patches for all the other packages. Is it a good way to simply install
all recommended patches and then downgrade the kernel and glibc with
rpm -e and then do a new install the packages from a sp3 with rpm -i?
Or sth. like rpm -U --force to install the older rpms?

I also thought about using the "Taboo Yes" in yast (Software
instllation) and then starting YOU but the taboo state only stays until
the next yast start.

I noticed some strange (to me) output when executing /lib(64)/libc.so.6
in the shell while exploring the glibc/kernel patch behavior. It claims
to be..
GNU C Library stable release version 2.3.5 (20050720), by Roland McGrath

but rpm -qf reports
glibc-2.3.3-98.61

This sounds a bit confusing to me but I discovered this on multiple
installations. Is there a simple explanation to this one?

thanks in advance
matthias

---------------------------------------------------------------------
To unsubscribe, e-mail: suse-sles-e-unsubscribe@suse.com
For additional commands, e-mail: suse-sles-e-help@suse.com

This archive was generated by hypermail 2.1.7 : Thu Mar 09 2006 - 17:19:45 CET