Red Hat Bugzilla – Bug 859
Last modified: 2014-08-04 18:22:58 EDT
Mostly a FYI bug:
I installed on a brand new, never before used, disk.
(I mean NEVER used, which is critical.) (On C:, that
is the primary drive address.)
After the installation completed, LILO couldn't boot
to Linux; it turns out that no partition on that disk was
marked bootable. When the installer runs, it should
mark the partition bootable (or at least ask if it should),
so that something comes up. (I don't at this point
remember the exact message, but I do remember that it
was unhelpful in figuring this out; obviously I finally
did, but it was painful.)
(It's not unreasonable that the best fix for this is
mostly, if not totally, documentation.)
P.S. I installed the system on a new PCChips M577
mainboard, with the "features" of ChipAway Virus and
PC-cillin97. One or both of those thinks that LILO is
a virus (didn't track down which, just turned off the
checking in the BIOS setup). (There's some irony
about LILO being a virus :-) ).
I was unable to get the system to fail to boot. But the installer does
not mark the partition containing the /boot directory as active as it
probably should. This leads to believe that certain hardware
combinations can cause the system to fail to boot and some don't. I am
assigning it to a developer for further review.
Fixed in next release.