Re: Using the --modules option in grub-install

[Arbiel Perlacremaz]

Jordan, you are quite right. I've not to use the --modules option.

From my GNU/Linux PC, I installed grub, without any --modules option on 
an external drive which contains two Windows systems, a Windows 98SE on 
a FAT partition and a Windows XP on a NTFS partition. I then used 
grub-mkconfig to generate the appropriate grub.cfg file. Before pluging 
my external drive out to my other PC as an internal drive, I modified 
the grub.cfg file to discard any menuentry relative to my GNU/Linux PC.

I've been surprised to find only one menuentry for the two windows 
systems, pointing to my Windows 98SE partition, with the label "Windows 
XP". I decided to manually include a second menuentry pointing to my XP 
partition.

The first entry, the one created by grub-mkconfig worked fine. It led my 
to the Windows multiboot menu, whose two entries worked fine. It means 
the partition boot record of my Windows 98SE contains code to handel the 
Windows multiboot

The second entry, the one I created by myself, did not work at all. This 
means the partition boot sector of my Windows XP partition only contains 
gabbage.

Arbiel


Le 21/03/2012 08:38, Jordan Uggla a écrit :
> On Tue, Mar 20, 2012 at 8:39 AM, Arbiel Perlacremaz
> <address@hidden>  wrote:
> > Hi
> >
> > Can somebody please explain me how to specify the names of the modules to be
> > included into the core.img when using the --modules option of grub-install ?
> You should really never need to use the --modules argument, and it's
> rarely actually useful. What are you trying to accomplish?