David C. Rankin wrote:
Aaron Kulkis wrote:
David C. Rankin wrote:
Listmates,
How do I prevent Yast from deleting my working kernel when I do a kernel update?
It isn't deleted.
Your old kernel will still be in /boot, and will there will be a symbolic link /boot/vmlinuz.old pointing to it.
To boot the previous kernel, you intervene during the boot-up process, and add ".old" appropriately to the boot-line when it comes up in grub.
Additionally, you can always add an entry to grub to make this even easier.
NOTE... I don't have an "old" kernel on my machine right now, so my reply is based on personal memory.
What do I need to copy or rename so I can restore a working config if Yast and/or the new kernel borks my system? I recall this discussion, but googling, I can't find the old posts. With all the recent YOU kernel update problems, I want to make sure I can get back to my old kernel and config. Thanks!
I wish it worked that way, but yast in 10.3 does _delete_ the old kernel and _removes_ the installed modules for the old kernel. The module tree for the old kernel remains in /lib/modules, but any custom modules (wifi, etc) are deleted on the kernel upgrade. This killed a production box when kernel update crashed after setting the vmlinuz and initrd links to the new kernel even though the crash occurred before the new kernel was actually installed.
I have used the method suggested by Ken to download the kernel, kernel-source and kernel-syms and then install manually with rpm -ivh. This works the way yast use-to-work. The new kernel is installed and the old kernel and all old modules are left intact. Proper grub menu.lst entries are created for both the new and old kernels. Once verified, the old kernel can be removed either through yast or with rpm -e and the menu.lst entries are properly removed as well.
The only negative side effect of the rpm -ivh install is on online-update that still thinks it needs to install the new kernel. Manually changing the OU select options for the kernel fixes this problem.
Hi, I actually got it right with yast somehow. I think it is because I locked (it displays a padlock symbol) my kernel in yast to stop it from trying to upgrade and mess up my configuration. then I upgraded to a 2.6.24 strain and I ended up with a dual boot screen, for both kernels, on startup. It might also be part of the new 11.0 yast of course. Use 11.0 yast very carefully as it still has some irritating bugs. I haven't destroyed my system yet though. Try locking it and see what happens. Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org