On Thu, 26 Jun 2008 08:16:58 -0700, Craig White wrote:
watching this thread with interest.
I have several Dell Optiplex 320's that will not boot with grub but will
boot with lilo and so I have lilo installed on them.
Is this problem known upstream?
Unfortunately though, kernel updates do produce the error above
(unable
to open /boot/boot.b) generated by grubby. Is there any way around
getting grubby to re-run lilo to execute an update when new kernels are
installed?
With LILO, no. LILO must be rewritten with every change in lilo.conf.
GRUB, on the contrary, must not be rewritten after modifying grub.conf,
because it can read the ext2/ext3 fs directly to load its config file.
If you're interested in where grubby is executed, take a look at
/sbin/new-kernel-pkg which is called by the "kernel" package scriptlets.