From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1KLQXh-0004KU-2v for mharc-grub-devel@gnu.org; Tue, 22 Jul 2008 18:41:13 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KLQXd-0004HD-Gf for grub-devel@gnu.org; Tue, 22 Jul 2008 18:41:09 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KLQXb-0004FW-QL for grub-devel@gnu.org; Tue, 22 Jul 2008 18:41:09 -0400 Received: from [199.232.76.173] (port=35749 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KLQXb-0004FJ-IA for grub-devel@gnu.org; Tue, 22 Jul 2008 18:41:07 -0400 Received: from c60.cesmail.net ([216.154.195.49]:52424) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.60) (envelope-from ) id 1KLQXb-0000f4-Fw for grub-devel@gnu.org; Tue, 22 Jul 2008 18:41:07 -0400 Received: from unknown (HELO relay.cesmail.net) ([192.168.1.81]) by c60.cesmail.net with ESMTP; 22 Jul 2008 18:41:05 -0400 Received: from [192.168.0.21] (static-72-92-88-10.phlapa.fios.verizon.net [72.92.88.10]) by relay.cesmail.net (Postfix) with ESMTP id 6C5E5618F22 for ; Tue, 22 Jul 2008 18:41:05 -0400 (EDT) From: Pavel Roskin To: The development of GRUB 2 In-Reply-To: <20080722220942.GC15825@thorin> References: <1216040584.9995.52.camel@dv> <200807160132.18470.okuji@enbug.org> <20080719150624.GD23778@thorin> <200807192216.23882.okuji@enbug.org> <1216673313.11291.24.camel@dv> <20080722213747.GC15111@thorin> <1216764101.5601.15.camel@dv> <20080722220942.GC15825@thorin> Content-Type: text/plain Date: Tue, 22 Jul 2008 18:41:04 -0400 Message-Id: <1216766464.5601.28.camel@dv> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 (2.22.3.1-1.fc9) Content-Transfer-Encoding: 7bit X-detected-kernel: by monty-python.gnu.org: Genre and OS details not recognized. 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, 22 Jul 2008 22:41:09 -0000 On Wed, 2008-07-23 at 00:09 +0200, Robert Millan wrote: > On Tue, Jul 22, 2008 at 06:01:41PM -0400, Pavel Roskin wrote: > > On Tue, 2008-07-22 at 23:37 +0200, Robert Millan wrote: > > > > > > Suppose that we don't have device.map. Then I don't need to add entries > > > > for temporary devices. Also, I won't be able to create a cross-drive > > > > configuration by accident, simple because it won't be allowed by > > > > default. > > > > > > But we could have device.map _and_ a fallback mechanism for when there's > > > no match (e.g. give it a "(dummy0)" drive). > > > > > > I even STR I implemented that in some patch. > > > > The problem was that the reliable information was called "dummy" and > > used as fallback, whereas the unreliable information was used by > > default. > > None of it was intended to be reliable for anything. It was simply a way of > making GRUB non-util code handle system devices that haven't been registered > in device.map, like a temporary USB disk. The boot driver information from BIOS should be considered as more reliable than guess by a userspace program how BIOS might see the drives. There are known buggy BIOSes, but we know how to work it around. -- Regards, Pavel Roskin