i wrote:
> > https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-9.0.0-amd64
> > With OVMF, GRUB2 is in charge and works fine.

Samuel Thibault wrote:
> That's probably sheer luck.
>     [ Part 2, Image/PNG 545 KB. ]

Wow. That's really unusable.
The appearance of Hurd's GRUB menu is ill, but because of the correct
graphics every second arrow key one can navigate and trust the result
of the key even if it is not visible.

Did you already talk to Steve McIntyre about the appearance of amd64
on your VM ?

> >   -rw-r--r-- 1 root root 512 Mar 23  2015 /usr/lib/grub/i386-pc/boot.img

> Note that the script gets executed on Debian GNU/Hurd, not Debian
> GNU/Linux. Perhaps for some reason there's a bug in the Hurd version.
> ...
> Better investigate the Hurd version first before contacting them,
> perhaps it's a target-specific issue.

It looks as if already the blob boot.img on my amd64 Debian 8 has the
problem with the misused partition table byte range.
(On GNU/Hurd it could only be better than that.)
The first 512 bytes of the 2017 Hurd ISO are the same as in my locally
installed file /usr/lib/grub/i386-pc/boot.img .

The GRUB targets are the same in both cases: "i386-pc", which i understand
is initially the 16 bit aspect of x86 plus BIOS INT services, and maybe
later 32 bit code.
There are no indications that 64 and 32 bit machines are distinguished at
that level.

> Coordination between GNU projects?  You're dreaming a bit :)

rms urges us to do so. Since we don't follow his wish to use Lisp
we have to find other ways to please him. :))

Have a nice day :)


Reply via email to