El 30/5/2016 21:07, "Samuel Thibault" escribió:
>
> Yes, that should be correct. Note that it's the 30_os-prober.in file
> which needs to be modified. Also, since this is an upstream file, you
> should probably contact upstream to get it integrated there, so Debian
> doesn't
Hello,
Rodrigo Valiña Gutiérrez, on Thu 26 May 2016 12:05:37 +0200, wrote:
> -
> --- 30_os-prober 2016-02-05 18:30:35.0 +0100
> +++ 30_os-prober-3 2016-05-26 11:54:35.819822599 +0200
> @@
On Wed, May 25, 2016 at 11:20 PM, Samuel Thibault
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
Hello,
Rodrigo Valiña Gutiérrez, on Wed 25 May 2016 17:53:47 +0200, wrote:
>mach_device="`echo "${grub_device}" | sed -e
> 's/(\(hd.*\),msdos\(.*\))/\1s\2/'`"
> + hurd_device=`${grub_probe} --device ${DEVICE}
> --target=compatibility_hint | sed 's/,msdos/s/'`
Why adding another
Package: grub-common
Version: 2.02~beta2-22+deb8u1
Severity: normal
Tags: patch
The script /etc/grub.d/30_os-prober does not provide the correct device name
for booting the Hurd, e.g. when installed with crosshurd.
The bug also applies to the grub version currently in sid.
The patch changes
5 matches
Mail list logo