From: Felix Zielcke
Date: Mon, 07 Dec 2009 11:39:22 +0100
> The one mount point case is now fixed in r1917
> See Subject: `handling mount points in grub-mkrelpath' from me for the
> patch.
Seems to work properly now. The paths all start with "//" but
I guess that's ok.
Thanks!
__
From: Felix Zielcke
Date: Mon, 07 Dec 2009 23:06:46 +0100
> Am Montag, den 07.12.2009, 03:24 -0800 schrieb David Miller:
>> In fact I don't see why these scripts don't do that, and relatively
>> resolve the /boot directory whatever seperately.
>
> Because it's faster to just call once for the d
Am Montag, den 07.12.2009, 03:24 -0800 schrieb David Miller:
> In fact I don't see why these scripts don't do that, and relatively
> resolve the /boot directory whatever seperately.
Because it's faster to just call once for the directory
make_system_path_relative_to_its_root() instead of once for
From: Felix Zielcke
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
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-2
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 su
