From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1KItjl-0006ol-8W for mharc-grub-devel@gnu.org; Tue, 15 Jul 2008 19:15:13 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KItji-0006ng-Qy for grub-devel@gnu.org; Tue, 15 Jul 2008 19:15:10 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KItjh-0006mV-Fq for grub-devel@gnu.org; Tue, 15 Jul 2008 19:15:10 -0400 Received: from [199.232.76.173] (port=55510 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KItjh-0006mP-Ap for grub-devel@gnu.org; Tue, 15 Jul 2008 19:15:09 -0400 Received: from ns39764.ovh.net ([91.121.25.85]:39367 helo=nexedi.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KItjg-0006go-Ul for grub-devel@gnu.org; Tue, 15 Jul 2008 19:15:09 -0400 Received: from [10.8.0.46] (unknown [10.8.0.46]) by nexedi.com (Postfix) with ESMTP id 34C093DC75 for ; Wed, 16 Jul 2008 01:20:47 +0200 (CEST) From: "Yoshinori K. Okuji" Organization: enbug.org To: The development of GRUB 2 Date: Wed, 16 Jul 2008 01:15:07 +0200 User-Agent: KMail/1.9.9 References: <1216040584.9995.52.camel@dv> <200807152304.17448.okuji@enbug.org> <1216161099.8266.28.camel@dv> In-Reply-To: <1216161099.8266.28.camel@dv> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807160115.07363.okuji@enbug.org> X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 3) Subject: Re: Next release? X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jul 2008 23:15:11 -0000 On Wednesday 16 July 2008 00:31:39 Pavel Roskin wrote: > On Tue, 2008-07-15 at 23:04 +0200, Yoshinori K. Okuji wrote: > > I am sorry, but can I ask why you want to remove device.map? Did I miss > > any discussion? > > There was a short discussion, but I write it more concisely now. > > 1) We don't want to cache anything. Any cached information risks to > become stale. > > 2) We don't want to rely on knowing how BIOS would see the devices at > the boot time. If GRUB is installed in a way that more than one drive > is involved, it's our responsibility to do it reliably or not at all. > > 3) We don't want floppies or any unrelated drives to be touched when > they are not involved. OK. Then how do you install GRUB into (hd1) in a development machine, which is (hd0) in a booting machine? When GRUB may not correctly determine BIOS drives, do you want to just give up? Regards, Okuji