From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with archive (Exim 4.43)
	id 1NHbhm-0005yP-R3
	for mharc-grub-devel@gnu.org; Mon, 07 Dec 2009 06:24:38 -0500
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NHbhl-0005xc-Al
	for grub-devel@gnu.org; Mon, 07 Dec 2009 06:24:37 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NHbhk-0005wU-HC
	for grub-devel@gnu.org; Mon, 07 Dec 2009 06:24:36 -0500
Received: from [199.232.76.173] (port=54068 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NHbhk-0005wI-7b
	for grub-devel@gnu.org; Mon, 07 Dec 2009 06:24:36 -0500
Received: from 74-93-104-97-washington.hfc.comcastbusiness.net
	([74.93.104.97]:41393 helo=sunset.davemloft.net)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <davem@davemloft.net>) id 1NHbhj-0001N8-Oj
	for grub-devel@gnu.org; Mon, 07 Dec 2009 06:24:35 -0500
Received: from localhost (localhost [127.0.0.1])
	by sunset.davemloft.net (Postfix) with ESMTP id D492124C6E2;
	Mon,  7 Dec 2009 03:24:34 -0800 (PST)
Date: Mon, 07 Dec 2009 03:24:34 -0800 (PST)
Message-Id: <20091207.032434.220077475.davem@davemloft.net>
To: grub-devel@gnu.org, fzielcke@z-51.de
From: David Miller <davem@davemloft.net>
In-Reply-To: <1260182362.2908.5.camel@fz.local>
References: <20091206.233053.45905914.davem@davemloft.net>
	<1260182362.2908.5.camel@fz.local>
X-Mailer: Mew version 6.2 on Emacs 23.1 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3)
Cc: 
Subject: Re: mkrelpath doesn't do what it should...
X-BeenThere: grub-devel@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: The development of GNU GRUB <grub-devel@gnu.org>
List-Id: The development of GNU GRUB <grub-devel.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/grub-devel>,
	<mailto:grub-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/grub-devel>
List-Post: <mailto:grub-devel@gnu.org>
List-Help: <mailto:grub-devel-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/grub-devel>,
	<mailto:grub-devel-request@gnu.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Dec 2009 11:24:37 -0000

From: Felix Zielcke <fzielcke@z-51.de>
Date: Mon, 07 Dec 2009 11:39:22 +0100

> Am Sonntag, den 06.12.2009, 23:30 -0800 schrieb David Miller:
>> I was trying to figure out why the kernel image paths generated
>> automatically for me by grub-mkconfig were not correct.
>> 
>> I have /boot on a seperate partition, but in the generated config
>> files it uses paths like /boot/vmlinux-2632 etc.
>> 
>> The problem is grub-mkrelpath and it's usage in the scrips such as
>> "10_linux".
>> 
>> "/boot" is given to "grub-mkrelpath", and this results in
>> the identical "/boot" in rel_dirname.
>> 
>> So all the paths emitted by 10_linux end up being "/boot" based
>> instead of "/" based.
>> 
>> grub-mkrelpath seems to do the right thing if I pass it a full path,
>> f.e. giving it "/boot/vmlinux" emits the correct "/vmlinux"
> 
> The one mount point case is now fixed in r1917
> See Subject: `handling mount points in grub-mkrelpath' from me for the
> patch.

Thanks I'll have a look.

Locally for testing, I changed the 10_linux script to pass the
complete image path name to the device root relative pathname
resolver.  That worked just as well.

In fact I don't see why these scripts don't do that, and relatively
resolve the /boot directory whatever seperately.