Prev: Linux equivalent of Telnet?
Next: File encryption
From: Daniel James on 10 Jan 2008 07:19
In article news:<ob2f55-vki.ln1(a)zoogz.gregorie.org>, Martin Gregorie wrote:
> > Could you not have used 3rd-party software such as OnTrack Disk Manager?
> >
> That would be OK for 'doze - I've used it in the past - but don't
> forget that GRUB uses BIOS services, so the fact that the BIOS couldn't
> see the disk means that GRUB won't boot from it.

That doesn't follow. If it worked for DOS (which uses the BIOS) it would
work with GRUB. What might not work with linux is the handover between the
BIOS+DiskManager and protect-mode drivers ... but IIRC that could be made to
work.

> I have a hazy memory that I was able to install Linux in the bigger disk
> but then couldn't boot from it. At that point I read up on GRUB and
> discovered its BIOS dependency.

You were using the BIOS without any augmentation, so it wouldn't have worked
as GRUB needed to read the kernel (with its proetct-mode HDD drivers) from
the big disk, which BIOS couldn't see (but BIOS+DM might). You could
probably have got it to work by putting GRUB and /boot on the small disk and
the rest of linux on the big one.

All water under the bridge now, though.

Cheers,
Daniel.






First  |  Prev  | 
Pages: 1 2 3 4 5 6 7 8 9
Prev: Linux equivalent of Telnet?
Next: File encryption