Return-Path: <phcoder@gmail.com>
Received: from ?82.130.80.24? (hg-public-dock-24-dhcp.ethz.ch [82.130.80.24])
        by mx.google.com with ESMTPS id 28sm8296921fkx.17.2009.03.23.03.11.58
        (version=SSLv3 cipher=RC4-MD5);
        Mon, 23 Mar 2009 03:11:58 -0700 (PDT)
Message-ID: <49C7606E.1070404@gmail.com>
Date: Mon, 23 Mar 2009 11:11:58 +0100
From: phcoder <phcoder@gmail.com>
User-Agent: Thunderbird 2.0.0.21 (X11/20090318)
MIME-Version: 1.0
To: David Miller <davem@davemloft.net>
Subject: Re: GRUB device names wrt. ieee1275
References: <49C61E3D.3040901@gmail.com>	<20090322.153022.233646325.davem@davemloft.net>	<49C6C0E2.7020308@gmail.com> <20090322.181308.135919853.davem@davemloft.net>
In-Reply-To: <20090322.181308.135919853.davem@davemloft.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

David Miller wrote:
> From: phcoder <phcoder@gmail.com>
> Date: Sun, 22 Mar 2009 23:51:14 +0100
> 
>> You could do it the way similar to how it's done on i386-pc:
>> jmp use_hardcoded
>> <code to retrieve boot block path>
>> use_hardcoded:
>> And then the grub-setup tool nops out the first jump if stage2
>> resides on a disk different than where bootblock is
> 
> Sure we could do that.
> 
> But I'm trying to figure out why to bother with this if I
> already have all of the (tested) logic and infrastructure to
> fill in the device path already?

What about booting from removable device? In this case you can't assume 
that device path during install is still valid at booting
> 
> It just seems like another case in the matrix which needs to
> be tested, and can thus go wrong.


-- 

Regards
Vladimir 'phcoder' Serbinenko