Bug#825229: crosshurd: Incompatibility with update-grub. Fails to boot.

[Samuel Thibault <sthibault@debian.org>]

Hello,

Thanks for the gnumach.gz link patch. Ideally the upgrade-grub scripts
should find gnumach* kernels (just like it does when run natively from a
Hurd system), but in the meanwhile the symlink can't hurt.

Rodrigo Valiña Gutiérrez, on Tue 24 May 2016 21:48:58 +0200, wrote:
> Running crosshurd to install in a disk partition and then running update-grub,
...
> Afterwards, the Hurd starts to boot but fails (hangs) with the following error
> (maybe an issue with partition names):
> 
> start ext2fs: ext2fs: device:(hostdisk//dev/sda,msdos2): No such device or address

So it seems the update-grub scripts don't properly translate
hostdisk//dev/sda,msdos2 into hd0s2.  That's where things need to get
fixed.

> Also I have observed that, running "grep TARGET /usr/share/crosshurd/*"
> yields some results with "$TARGET/..." quoted and some others not,
> so if we run crosshurd with a path with spaces, it may fail.

Supporting a path with spaces would not be so easy in the case of the
apt_options variable, where $TARGET is used.  It won't be a matter of
quoting it with " unfortunately.

Samuel