mirror of
https://git.linuxfromscratch.org/lfs.git
synced 2025-03-06 22:28:47 +00:00
grub cfg: Add an explanation for the insmod commands
This commit is contained in:
parent
f0b518a01e
commit
93ec8b32bf
@ -150,6 +150,24 @@ menuentry "GNU/Linux, Linux &linux-version;-lfs-&version;" {
|
||||
}</literal>
|
||||
EOF</userinput></screen>
|
||||
|
||||
<para>
|
||||
The <command>insmod</command> commands load the
|
||||
<application>GRUB</application> modules named
|
||||
<filename>part_gpt</filename> and <filename>ext2</filename>.
|
||||
Despite the naming, <filename>ext2</filename> actually supports
|
||||
<systemitem class='filesystem'>ext2</systemitem>,
|
||||
<systemitem class='filesystem'>ext3</systemitem>, and
|
||||
<systemitem class='filesystem'>ext4</systemitem> filesystems.
|
||||
The <command>grub-install</command> command has embedded some modules
|
||||
into the main <application>GRUB</application> image (installed into
|
||||
the MBR or the GRUB BIOS partition) to access the other modules
|
||||
(in <filename class='directory'>/boot/grub/i386-pc</filename>) without
|
||||
a chicken-or-egg issue, so with a typical configuration these two
|
||||
modules are already embedded and those two <command>insmod</command>
|
||||
commands will do nothing. But they do no harm anyway, and they may
|
||||
be needed with some rare configurations.
|
||||
</para>
|
||||
|
||||
<note><para>From <application>GRUB</application>'s perspective, the
|
||||
kernel files are relative to the partition used. If you
|
||||
used a separate /boot partition, remove /boot from the above
|
||||
|
Loading…
Reference in New Issue
Block a user