From: Eberhard Moenkeberg (emoenke_at_gwdg.de)
Date: Sat Dec 22 2007 - 02:03:07 CET
Date: Sat, 22 Dec 2007 02:03:07 +0100 (CET) From: Eberhard Moenkeberg <emoenke@gwdg.de> Message-ID: <Pine.LNX.4.64.0712220157000.19492@gwdu05.gwdg.de> Subject: Re: [suse-sles-e] Upgrade to SLES9 SP4 results in non-bootable systems when using SATA
Hi,
On Fri, 21 Dec 2007, Alexei_Roudnev wrote:
> No, it is not really possible to run old kernel in ALL cases.
>
> Examples:
> - if ocfs2-tools changed, you can't run old kernel and new ocfs2-tools;
> - if iscsi is changed, you can't run old iscsi module in the kernel and new
> iscsi daemon.
> - other examples do exists.
>
> Such cases are not common - in most cases, you can run old kernel on the new
> system, at least as a last resort mode (with some restrictions).
I bet we will not get a solution which is able to cover these exreme
cases...
> And yes, most Linux distros allows to revert to the previous kernel after the
> upgrade (or keep all kernels available
> until explicit removal). I love such behaviour much more then existing (in
> SuSe) one.
The SUSE guys themselves don't love the current behaviour I guess.
> It require, of course, to keep all, kernel, initrd, modules in /lib/modules,
> and source in /usr/src .
>
> Ideally I should configure _## of back kernels_ and/or configure _I'd like to
> keep this one kernel for a safe mode_.
This should be easy doable if they come out with a solution, but I guess
we will stay naked on our own forever with these extra dependencies from
your examples (which are not rare).
Viele Grüße
Eberhard Mönkeberg (emoenke@gwdg.de, em@kki.org)
---------------------------------------------------------------------
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 : Fri Dec 21 2007 - 15:03:25 CET