Joey Hess <joeyh@debian.org> writes:
> I've finished and tested the debian-cd patch for using vesamenu. Did
> notice one problem. When the vesamenu is used, "default64" does not
> behave the same as it normally does in syslinux. Rather than setting the
> default that's used then enter is pressed, it makes syslinux
> *immediately* start booting the amd64 installer with no chance for
> interaction.
>
> So unless it gets fixed[1], default64 can't be used on vesamenu images,
> and I've disabled it. Instead, you need to manually pick amd64 off the
> menu when booting a multiarch image.
>
> Is this a big problem? At least there is a menu, with "AMD64 install"
> visible on it. (Maybe that would be better named "64 bit install" to
> avoid the amd/ia64/x86_64 confusion..)
I think that when we have the menu it's even better to let the user to
choice instead of setting it for him.
> I've created 3 test CD images that use vesamenu:
>
> http://kitenet.net/~joey/tmp/vesamenu/
>
> My feeling is that this is basically ready to go and is quite unlikely
> to break anything in the beta2 timeframe if applied soon.
Ack.
> PS, the win32-loader.ini file on the multi-arch CDs lists kernel/initrd
> images for amd64, but not for i386. Seems wrong.
Robert, could you take a look at it?
--
O T A V I O S A L V A D O R
---------------------------------------------
E-mail: otavio@debian.org UIN: 5906116
GNU/Linux User: 239058 GPG ID: 49A5F855
Home Page: http://otavio.ossystems.com.br
---------------------------------------------
"Microsoft sells you Windows ... Linux gives
you the whole house."