🚀 go-pugleaf

Hmmm I think I have a little more to add after some investigations...

First of all my own particular "doesn't have a valid boot signature"
error is:

1. Nothing to do with getting the partition name wrong. I can mount it
from a boot disk... and its the right one.

2. Nothing to do with trying to *UNINSTALL* lilo.

I have nooticed that I get the error at the end of a kernel install.
('make install' from /usr/src/linux). And I think I didnt get the
problem until after I did a kernel install.

I maybe wrong here but I think lilo takes a look at the partitions its
about to add, and checks to see if there is a bootable OS there. If
there is not (or it belives there is not) it gives the error. This
leaves us two possibilities:

1. Lilo cant see a bootable OS even though it is there. Maybe there is a
fault with lilo which means it cant see a bootable OS created by the new
red hat 6 source files.

2. The red hat 6 source if generating an unbootable kernel. Unlikely.

I think lilo cant see a bootable red hat 6 OS.

So im digging deeper... probably into the lilo source.

Ile report back.


Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.