On Mon, 09 Oct 2000, J�rgen Zimmermann wrote:
> Hello,
> I have a current cooker installation with the grub bootloader
> and noticed, that a kernel install/upgrade does not modify
> grub's menu, but instead does ALWAYS update /etc/lilo.conf,
> even if it does not exist, and "lilo" is uninstalled
> (using "--nodeps"...)
>
> This is a behaviour which can render a running system by a simple
> kernel install in a "not startable" system...
I've run into several cases where a kernel update can render a grub-based
system unbootable. Since then, I always do the following:
# rpm -Fvh <kernel-sources, kernel-header, kernel-doc>
# rpm -ivh <kernel, kernel-secure>
# cd /boot/grub
# vim menu.lst - add my backup copies
# ./install.sh - this doesn't ship with the x bit on by default
Since I started doing this a month+ ago, I've never had an unbootable system
.../Ed
--
Ed Wilts, Mounds View, MN, USA
mailto:[EMAIL PROTECTED]
