On Tue, Feb 17, 2009 at 04:31:18PM +0100, Eberhard Moenkeberg wrote:
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.
Splendid idea. Thanks.
--noscripts can be useful, as well. Otherwise the bootloader config might be touched, which poses a risk in itself. But the config needs to be closely watched anyway, if a kernel is going to be updated. (I forgot to mention it before.) (And I routinely find myself deinstalling the suspend package; because it has a habit of recreating *all* initrds in its postinstall script, which I'm not fond of.) Peter -- Contact: admin@opensuse.org (a.k.a. ftpadmin@suse.com) #opensuse-mirrors on freenode.net Info: http://en.opensuse.org/Mirror_Infrastructure SUSE LINUX Products GmbH Research & Development