-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, 3 Aug 2003 13:13:46 -0500, Otto Haliburton wrote:
> Knowing where the GRUB directory is doesn't have anything to do with > knowing where things are located. The MBR is in the 1st sector of the > drive we agree. Once GRUB is called it goes to a particular location on > the disk to load stage1 (that particular location on linux just happens > to be /boot/grub). I suggest you go to /boot/grub and see what is in > that directory. Again I am saying something very simple. If it knows > where stage1 is then it knows where stage2 is!!!!!!!!!!!!!!!!!!!1 *sigh* No. Because 1) stage1 is the MBR and NOT the file in grub directory, 2) two completely different techniques are used to load stage1.5 and stage2. While the physical location of stage1.5 is hardcoded into the MBR, the location of stage2 is not. At a later point in the booting process, GRUB is able to access the ext2 file-system directly and *then* can access stage2 and any file on its root partition. But all this is irrelevant. Ashley is confronted with a problem where GRUB stage1 (the MBR!) fails/hangs. IMO, and I've mentioned that earlier, the only reason can be that it gets a wrong BIOS drive Id or loads wrong sectors due to geometry mismatch. We don't know what role primary slave drive plays when it is removed. Hence I don't have any other comment. Btw, since I'm tired of your replies in this thread, welcome to my ~/.procmailrc! Don't expect another reply from me. - -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/LVbU0iMVcrivHFQRAsXmAJ9BndNBko84D+EutCyewq0VPBsHAACfUAro 429/pTz0rncvSaMZLzbO34k= =gJCZ -----END PGP SIGNATURE----- -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
