From owner-freebsd-stable@FreeBSD.ORG Wed May 18 23:44:07 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B2E1F16A4CF for ; Wed, 18 May 2005 23:44:07 +0000 (GMT) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F51843DAE for ; Wed, 18 May 2005 23:44:07 +0000 (GMT) (envelope-from mkb@incubus.de) Received: from drjekyll.mkbuelow.net (p54AAD929.dip.t-dialin.net [84.170.217.41]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id A40212FAD3; Thu, 19 May 2005 01:44:01 +0200 (CEST) Received: from [IPv6:::1] (localhost.mkbuelow.net [IPv6:::1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j4INjYid002879; Thu, 19 May 2005 01:45:35 +0200 (CEST) (envelope-from mkb@incubus.de) Message-ID: <428BD39E.4070109@incubus.de> Date: Thu, 19 May 2005 01:45:34 +0200 From: Matthias Buelow User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050509) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Doug White 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> In-Reply-To: <20050518162535.B87264@carver.gumbysoft.com> X-Enigmail-Version: 0.91.0.0 OpenPGP: id=6FF22C9F; url=http://www.mkbuelow.net/mkbkeys Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit cc: Mike Jakubik cc: stable@freebsd.org cc: Dan Nelson Subject: Re: Boot loader cant identify ntfs? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 May 2005 23:44:07 -0000 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.