mezlo

I'm running CentOS 5.2 but have been using LILO for my bootloader until I started getting a conflict between it and a syslinux update. I switched to GRUB, configured and tested it, then removed LILO.

Everything seems to work just fine except that anytime grubby runs (kernel update, manually, etc), it gives the error "grubby: unable to open /boot/boot.b: No such file or directory". I know boot.b is part of LILO so removing it is what removed boot.b

My question is, do I need to worry about this error since the system boots just fine? Also, is there a way to stop this error from occurring other than reinstalling LILO?

Mez

Looking for Linux Hosting? Click Here

Jonathan183

Welcome to the forums Mez
I have not got CentOS on any of my systems at the moment so I can't check ... but does this help?

mezlo

The article itself did not help at all. However, I noticed that lilo.conf mentioned /boot/boot.b so I checked and sure enough, /etc/lilo.conf still existed. I renamed it and the error was gone.

I'd actually looked at that article yesterday before asking my question but it didn't sink in at that time.

Thanks for the indirect help.

Mez

Jonathan183

Glad your sorted ... and thanks for sharing the solution. I use grub for all my installs ... so I was not sure if the Lilo install created the /etc/kernel-img.conf on the linked page for NewKernel. I looked on an Arch and OpenSUSE install and neither had the file.

Can you mark the thread as solved ...