On Wed, May 25, 2016 at 11:20 PM, Samuel Thibault <sthiba...@debian.org>
wrote:
>
> Why adding another variable, instead of just fixing mach_device? I
> guess grub-probe simply changed something and the mach_device definition
> needs to be updated.
>
> This is really meant to be a mach device name, not a "hurd device name".
>
> Samuel
>
I understand. I did not know the exact terminology. So the patch might boil
down to:
-------------------------------------------------------------------------------------------------
--- 30_os-prober 2016-02-05 18:30:35.000000000 +0100
+++ 30_os-prober-3 2016-05-26 11:54:35.819822599 +0200
@@ -331,7 +331,7 @@
save_default_entry | grub_add_tab
prepare_grub_to_access_device ${DEVICE} | grub_add_tab
grub_device="`${grub_probe} --device ${DEVICE} --target=drive`"
- mach_device="`echo "${grub_device}" | sed -e
's/(\(hd.*\),msdos\(.*\))/\1s\2/'`"
+ mach_device=`${grub_probe} --device ${DEVICE}
--target=compatibility_hint | sed 's/,msdos/s/'`
grub_fs="`${grub_probe} --device ${DEVICE} --target=fs`"
case "${grub_fs}" in
*fs) hurd_fs="${grub_fs}" ;;
-------------------------------------------------------------------------------------------------
So this is one more step to get working flawlessly and out of the box the
procedure at:
https://www.gnu.org/software/hurd/hurd/running/debian/CrossInstall.html
It remains at least to determine whether --readonly is needed, and maybe to
provide a way to boot in single user mode (-s) (needed for the first two
reboots).
By the moment it does not work out of the box yet because of these and
maybe other issues.
Rodrigo.
