From: Alexei_Roudnev (Alexei_Roudnev_at_exigengroup.com)
Date: Thu Mar 09 2006 - 22:42:46 CET
Message-ID: <02da01c643c2$67624e10$6f31a8c0@sjc.exigengroup.com> From: "Alexei_Roudnev" <Alexei_Roudnev@exigengroup.com> Date: Thu, 9 Mar 2006 13:42:46 -0800 Subject: Re: [suse-sles-e] keep old kernel after kernel upgrade
It's true - usually it works fine; but sometimes you still must be aware of
the difference. For example, if I use network installation, I cannot instal
SP3 system if I use boot kernel from Sp2 system; if you keep old kernel, you
must kept old modules and so on/
Generally it is minor issue - YOU do not remove kernel which is not active,
so all you need to do is to add (manually) safe kernel into the system and
into grub menu, and then you can run YOU etc without risk to lost the whole
system.
----- Original Message -----
From: "Lars Müller" <lmuelle@SuSE.de>
To: "Alexei_Roudnev" <Alexei_Roudnev@exigengroup.com>
Cc: "fritz fuchs" <swatcher2005@yahoo.de>; <suse-sles-e@suse.com>
Sent: Thursday, March 09, 2006 1:27 PM
Subject: Re: [suse-sles-e] keep old kernel after kernel upgrade
On Thu, Mar 09, 2006 at 11:34:50AM -0800, Alexei_Roudnev wrote:
> Yes, it is all YOU bug (it do not keep previous kernel correctly). I
better
> prefer to specify that some kernels are _sticked_.
>
> Unfortunately, there are more dependencies - for example, /lib/modules
must
> have modules from kernel, and mkinitrd changed between kernel versions.
This is solved with the kernel RPMs provided by SuSE since UL 1/ SLES 8
SP 2 IIRC. The following output is from a current SLES 9 system:
---------------------------------------------------------------------
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 - 22:41:25 CET