Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1NIe8z-0004R7-97 for mharc-grub-devel@gnu.org; Thu, 10 Dec 2009 03:13:01 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NIe8x-0004QF-CI for grub-devel@gnu.org; Thu, 10 Dec 2009 03:12:59 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NIe8s-0004Ly-PD for grub-devel@gnu.org; Thu, 10 Dec 2009 03:12:59 -0500 Received: from [199.232.76.173] (port=59527 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NIe8s-0004Lv-MW for grub-devel@gnu.org; Thu, 10 Dec 2009 03:12:54 -0500 Received: from smarthost03.mail.zen.net.uk ([212.23.3.142]:36870) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NIe8s-0005v6-A6 for grub-devel@gnu.org; Thu, 10 Dec 2009 03:12:54 -0500 Received: from [82.69.40.219] (helo=riva.pelham.vpn.ucam.org) by smarthost03.mail.zen.net.uk with esmtp (Exim 4.63) (envelope-from ) id 1NIe8r-0007e6-Ba for grub-devel@gnu.org; Thu, 10 Dec 2009 08:12:53 +0000 Received: from cjwatson by riva.pelham.vpn.ucam.org with local (Exim 3.36 #1 (Debian)) for grub-devel@gnu.org id 1NIe8q-0004tM-00; Thu, 10 Dec 2009 08:12:52 +0000 Date: Thu, 10 Dec 2009 08:12:52 +0000 From: Colin Watson To: The development of GNU GRUB Message-ID: <20091210081252.GI6439@riva.ucam.org> References: <20091207142806.GB6439@riva.ucam.org> <20091207172522.GA31361@riva.ucam.org> <20091209214915.GF7093@thorin> <20091209230443.GH6439@riva.ucam.org> <20091210005527.GB15546@thorin> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091210005527.GB15546@thorin> User-Agent: Mutt/1.5.18 (2008-05-17) X-Originating-Smarthost03-IP: [82.69.40.219] X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) Subject: Re: [RFC] Dynamic device.map X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GNU GRUB List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Dec 2009 08:12:59 -0000 On Thu, Dec 10, 2009 at 01:55:27AM +0100, Robert Millan wrote: > On Wed, Dec 09, 2009 at 11:04:43PM +0000, Colin Watson wrote: > > I'm trying to figure out how to make Debian's grub-installer operate > > without a device.map; it has various legacy bits and pieces that need > > conversion, and I'm working on these. > > > > Along the way, though, I noticed that grub-install still unconditionally > > creates a device.map. This seems likely to become confusing if devices > > are changing around a lot, since it's never updated. I'd like to get to > > the point where it doesn't do this by default. How about we add support > > for an option to disable this, and make grub-installer and the Debian > > maintainer scripts pass it once they're ready? Some time later, we can > > flip the default value. > > Why is this option necessary? If we removed automated generation of > device.map, user can still call grub-mkdevicemap manually. Certainly, but I would like to be able to deliver a system that does not generate a device.map by default. > But first we'd need to figure out what we do with the "set root=xxx" > backward compatibility hack. Has it been a while long enough that > we can remove support for GRUB installs that didn't come with UUID > support? > > If we don't do anything on grub-mkconfig side and remove device.map, we'll > end up with things like "set root=(/dev/sda1)" which is not just useless > but also utterly confusing. No, I don't think we will. grub-probe is perfectly capable of mapping /dev/sda1 to (hd0,1) even without device.map; it's just that that mapping will be solely dependent on device iteration order at the time you run grub-mkconfig. (As opposed to whatever device iteration order happened to be the first time you installed GRUB, for the nearly-everyone who never edited device.map by hand ...) -- Colin Watson [cjwatson@ubuntu.com]