Mailinglist Archive: opensuse-factory (341 mails)
| < Previous | Next > |
Re: [opensuse-factory] was multiversion support in zypp.conf ever added to 11.0?
- From: Peter Poeml <poeml@xxxxxxx>
- Date: Tue, 17 Feb 2009 15:29:12 +0100
- Message-id: <20090217142912.GU14919@xxxxxxx>
On Thu, Feb 05, 2009 at 12:45:12AM +0100, Eberhard Moenkeberg wrote:
rpm -e --justdb kernel-$version
should achieve the same; it is what I used until I settled for yum.
On 11.x (with new enough libzypp, i.e. from 11.1 or newer), I use zypper
with the new "multiversion" feature. It is simple to configure and does
the job - Stano has blogged about it here:
http://lizards.opensuse.org/2009/02/03/do-you-want-multiple-kernels-on-your-system/
Peter
--
Contact: admin@xxxxxxxxxxxx (a.k.a. ftpadmin@xxxxxxxx)
#opensuse-mirrors on freenode.net
Info: http://en.opensuse.org/Mirror_Infrastructure
SUSE LINUX Products GmbH
Research & Development
Hi,
On Wed, 4 Feb 2009, Rob OpenSuSE wrote:
2009/2/4 Eberhard Moenkeberg <emoenke@xxxxxxx>:
So providing the kernel that worked is required. Updating zypper
alone is not a solution!
Presumably someone who runs 11.0 actually backs up their system?
That would not help.
A "native" OpenSUSE/SLES/SLED system just has one kernel to boot.
And if it does't, you won't reach your backups with ease.
Well I actually had the problem, due to update being screwed up, and I
sorted it fairly simply, with a Live CD, the rpm(8) man page, chroot &
mkinitrd, and fetching known good kernel rpm's. Fetching the files
from backup would have been even simpler.
Surely someone has the rpm's still? This issue has been the same in
SuSE for ages and folk have muddled through, even though this was
obviously severely compromising the enterprise worthiness of the
distro.
I can live with it, but it is nasty, and against YaST's philosophy.
If YOU is offering a kernel update, it brings a popup window.
I then do
cd /lib/modules
mkdir x
cp -al `uname -r` x/
cd /boot
mkdir x
cp -a *`uname -r`* x/
cd /usr/src
cp -al linux-`uname -r`* x/
then ack the popup, and after YOU has finished, I copy the saves back to
..
This way, my old, but running kernel is still valid - I can delay the
reboot as long as I like and enter an additional, "safe" boot target into
the grub or lilo setup.
YaST is still wasting /etc/lilo.conf and /boot/grub/menue.lst regularly in
this case, but that is a different point if you need something to argue
against the "quality" which I will not reflect upon here.
rpm -e --justdb kernel-$version
should achieve the same; it is what I used until I settled for yum.
On 11.x (with new enough libzypp, i.e. from 11.1 or newer), I use zypper
with the new "multiversion" feature. It is simple to configure and does
the job - Stano has blogged about it here:
http://lizards.opensuse.org/2009/02/03/do-you-want-multiple-kernels-on-your-system/
Peter
--
Contact: admin@xxxxxxxxxxxx (a.k.a. ftpadmin@xxxxxxxx)
#opensuse-mirrors on freenode.net
Info: http://en.opensuse.org/Mirror_Infrastructure
SUSE LINUX Products GmbH
Research & Development
| < Previous | Next > |