When installing lilo on the boot record of a drive that isn't the boot
drive, the installation gets the message (hdc1 used for example):
Warning: hdc1 is not on the first disk
printed over it (which it then prints partly over with the boot-disk
creation dialog). This should really be handled better, maybe grab the
stderr from lilo and return it to the installer in a dialog box. What
would REALLY be nice is if the user could be warned of stuff like that
before he ever got that far in the process, though.
This defect is considered MUST-FIX for Winston Beta-5
This defect has been re-classified as MUST-FIX for Winston Gold-release
The installer team has decided to handle this issue as a future feature.
Moving to RESOVLED - DEFERRED from CLOSED - DEFERRED
*** Bug 17358 has been marked as a duplicate of this bug. ***
*** Bug 18660 has been marked as a duplicate of this bug. ***
How did you get the MBR written to something other than the first drive?
I cannot reproduce this problem w/o more information.
Closing due to inactivity.
OK, apparently I only _thought_ I replied to this bug. Here goes:
I never said "master boot record", I said "boot record". I was installing to
hdc1 on a computer that had Windows 2000 on hda1. It was complaining because,
even though it was writing LILO to disk, it wasn't going to get executed as
hdc1 wasn't active and hdc wasn't even the boot drive. Hence a "warning" and
not an "error", it is just saying "this isn't going to help much unless you
rearrange your drives".
I would _much_ rather see a generic error handling system than trying to solve
this particular problem. I seriously thought you were joking asking me how
to "reproduce the problem", and now I see this "closing due to inactivity"
notice. Just go into the code, find wherever it is you exec lilo, redirect its
stderr to its stdout, change it to a popen, grab the output, and shove it in a
window. A general solution to "what happens when LILO generates an error" is
the way to go here, that way when LILO gets some new error ability added you
don't need to keep screwing with the installation program.
Related to bug 14204.
*** This bug has been marked as a duplicate of 14204 ***