Dear Hilmar,
Maybe the GRUB team already know the problem, and I hope this bug fixed in
the next release.
In the meanwhile, yes, you can change /etc/grub.d/10_linux like following.
-------------------
cat << EOF
echo $(printf "$(gettext "Loading Linux %s ...")" ${version})
linux16 ${rel_dirname}/${basename}
root=${linux_root_device_thisversion} ro ${args}
EOF
if test -n "${initrd}" ; then
cat << EOF
echo $(gettext "Loading initial ramdisk ...")
initrd16 ${rel_dirname}/${initrd}
EOF
fi
cat << EOF
------------------
Regards,
-----Original Message-----
From: hill...@web.de [mailto:hill...@web.de]
Sent: Sunday, February 07, 2010 12:30 AM
To: Choe, Hyun-ho
Cc: 567...@bugs.debian.org
Subject: Re: Bug#567239: Same boot failure with VMWare guest in
1.98~20100128-1
On 06.02.10 Choe, Hyun-ho (choehyu...@gmail.com) wrote:
Hi,
> Try to change linux/initrd to linux16/initrd16 in grub.cfg. In
> GRUB, you can change command line manually.
>
Thanks for the hint! However the next grub update/installation will
overwrite the file. Hence I guess it is a better idea to modify
/etc/grub.d/10_linux . Do you know which modifications have to be
done in this file?
Thanks in advance,
Hilmar
--
sigmentation fault
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
