On Mon, Feb 04, 2008 at 03:52:45PM -0500, Aaron Kulkis wrote:
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
Oh shit. What knucklehead broke that? </rhetorical>
It never was done any other way, the kernel was and is always replaced. Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org