On Wed, 2009-03-25 at 13:39 +0100, Neal H. Walfield wrote:
> Taking a look at grub-mkrescue, it seems that it creates a
> boot/grub/grub.cfg that executes an insmod for each specified module.
> It then copies the overlay files overwriting the just-created
> grub.cfg.
>
> The user's grub.cfg should
Taking a look at grub-mkrescue, it seems that it creates a
boot/grub/grub.cfg that executes an insmod for each specified module.
It then copies the overlay files overwriting the just-created
grub.cfg.
The user's grub.cfg should either be appended to the one created by
grub-mkrescue or there should
Quoting James Collier :
In the case of option 1, grub2 boots straight to the menu as expected.
Typeing 'c' to get to the prompt then 'ls' at the prompt reveals only
the (memdisk) device.
It was expected that at least (hd0,1) for the -hda fat: partition would
be available
Even without the -hda
Hi all,
I'm using GRUB2 from svn (r2039) with qemu.
Steps I take to reproduce:
1. create an overlay directory e.g. /grub2/overlay
2. populate the directory with
overlay/boot
overlay/boot/grub
overlay/goot/grub/grub.cfg
Where grub.cfg contains "some-menuentry" for example I u
