From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)
I have a triple OS system, with WinNT owning the MBR, and just Linux on
the second drive. I use bootpart to extract the lilo boot sector and make
it a menu choice in boot.ini. During the install, at the end of copying
ths selected modules, the install hung. In the console window, I saw a
message that the boot record wasn't on the first drive.
Steps to Reproduce:
1. Custom install
2. Linux on second drive
3. NT on first drive
4. Lilo boot in boot partition
5. Pick modules
6. System hangs after copying modules
Actual Results: I looked at the various consoles, saw that things had
come to a screeching halt and decided to power down. I used bootpart to
extract the boot sector and replaced the old one (C:\bootlinx.rh7). The
system was able to boot linux, but the disk had to be fsck'd.
Expected Results: The message about the boot partition not being on the
first drive should have been displayed in gui mode, along with the
ramifications. The system should have shut down gracefully.
Brent please investigate.
When you say 'modules', do you mean software packages? When I think of modules,
I think of the device drivers that are loaded by the kernel.
Yes, the 'modules' are the various groups of packages you can install. On RH7,
what happened after the packages installation was that you were prompted to
make a boot disk.
I think that this problem has been fixed. I don't think it has anything to do
with the bootloader, though. We were seeing some problems with machines hanging
at the end of install, but the machines that we have here that were doing this
aren't doing it anymore. I'm resolving this bug as fixed in rawhide. However,
if you see this problem in the future, please reopen this bug. Thanks for your