|
Home > Archive > Linux/Unix > September 2001 > Need a lil help
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Boulware5 2001-09-03, 9:35 pm |
| Ok, I have no idea where to post this because it involves Windows 2000 as well as Linux. I'll try it here first. I put Red Hat 7.1 on a second HD (the other drive containing Win2k). I could have sworn I avoided putting LILO on the Win2k disk, but somehow someway it affected my MBR and LILO came up with ONLY Linux as a boot option. I put /dev/hdg1 as where I wanted LILO (I have it on promise ultra IDE card, so I assume hdg1 is the first partition on the second harddrive.) Maybe my problem was that I didn't put LILO on hdg5, which is where the /boot partition is I think. So what I had to do is boot from the Windows 2000 CD and get into the recovery console. From there I just used the fixboot command to repair the MBR. It wrote a new partition table and that fixed it. So now I can boot into win2k and Linux ONLY with the Linux boot floppy. So my question really boils down to is what changes can I make to my boot.ini file and/or lilo.conf to not have to boot linux off the floppy each time - rather - have Linux AND Windows 2000 on LILO. Browsing around I saw something that said you can add c:\bootsect.red = "RedHat Linux" to boot.ini; is that all I add and if so what is bootsect.red and where would that be? Thanks  | |
| ccieToBe 2001-09-04, 1:20 pm |
| quote: Originally posted by Boulware5
Ok, I have no idea where to post this because it involves Windows 2000 as well as Linux. I'll try it here first. I put Red Hat 7.1 on a second HD (the other drive containing Win2k). I could have sworn I avoided putting LILO on the Win2k disk, but somehow someway it affected my MBR and LILO came up with ONLY Linux as a boot option. I put /dev/hdg1 as where I wanted LILO (I have it on promise ultra IDE card, so I assume hdg1 is the first partition on the second harddrive.) Maybe my problem was that I didn't put LILO on hdg5, which is where the /boot partition is I think. So what I had to do is boot from the Windows 2000 CD and get into the recovery console. From there I just used the fixboot command to repair the MBR. It wrote a new partition table and that fixed it. So now I can boot into win2k and Linux ONLY with the Linux boot floppy. So my question really boils down to is what changes can I make to my boot.ini file and/or lilo.conf to not have to boot linux off the floppy each time - rather - have Linux AND Windows 2000 on LILO. Browsing around I saw something that said you can add c:\bootsect.red = "RedHat Linux" to boot.ini; is that all I add and if so what is bootsect.red and where would that be? Thanks
I suggest looking at the lilo.conf man page. Chances are you'll just need to edit the lilo.conf file, then reinstall LILO by typing "lilo" at the command prompt, logged in as root. There may be a way to get boot.ini to recognize Linux, but I doubt it. | |
| Boulware5 2001-09-04, 2:39 pm |
| When I fixed the MBR in recovery console, It had to remove lilo from where it was before. After changing lilo.conf, and running lilo, does it automatically put lilo in the location you specify, which in my case would be the /boot partition of the 2nd drive? | |
| ccieToBe 2001-09-04, 3:34 pm |
| quote: Originally posted by Boulware5
When I fixed the MBR in recovery console, It had to remove lilo from where it was before. After changing lilo.conf, and running lilo, does it automatically put lilo in the location you specify, which in my case would be the /boot partition of the 2nd drive?
I'm not sure. I would guess that it places LILO where you specified when you first installed Linux, but I haven't done that much post intall work lilo configuration. I'm sure there are some command arguments you can make to specify where lilo should go. If I were you I'd just try issuing "lilo" and see what happens. Even if something does go wrong you can just boot off of your LILO floppy again and read the docs to find out what command to issue. |
|
|
|
|