Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 19 May 2005 01:45:34 +0200
From:      Matthias Buelow <mkb@incubus.de>
To:        Doug White <dwhite@gumbysoft.com>
Cc:        Dan Nelson <dnelson@allantgroup.com>
Subject:   Re: Boot loader cant identify ntfs?
Message-ID:  <428BD39E.4070109@incubus.de>
In-Reply-To: <20050518162535.B87264@carver.gumbysoft.com>
References:  <1472.172.16.0.199.1116447692.squirrel@172.16.0.1> <20050518202836.GA82926@dan.emsphone.com> <428BA866.1050501@incubus.de> <20050518162535.B87264@carver.gumbysoft.com>

next in thread | previous in thread | raw e-mail | index | archive | help

Doug White wrote:

> Then the space problem just migrates.  There's a limited amount of space
> in the disklabel for bootblocks and I think we're pushing that.

Errm. /boot/loader doesn't reside in the 2nd stage, does it?
I mean, there is a boot menu (the Forth-run thing with the ASCII
daemon).  If that's running in protected mode already, then one could
jump back to real mode and boot into the selected disk/partition from
there.  I can't really see the problem?

Alternatively, I'd just not display the ?? for "unrecognized"
partitions.  Just present the disk/partition choice with perhaps the
FreeBSD partitions marked and the others unmarked.  But "??" really
looks like an error (and while at that, remove that horrible *BEEEEEEP*
please).

mkb.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?428BD39E.4070109>