add an extra option into the command install, and allow to mount extended partitions.
This commit is contained in:
parent
8fb66b3a69
commit
c6ec01220b
8 changed files with 160 additions and 95 deletions
|
@ -830,7 +830,7 @@ Load an initial ramdisk for a Linux format boot image and set the
|
|||
appropriate parameters in the Linux setup area in memory.
|
||||
@end deffn
|
||||
|
||||
@deffn Command install stage1_file [@option{d}] dest_dev file [addr] [@option{p}] [config_file]
|
||||
@deffn Command install stage1_file [@option{d}] dest_dev stage2_file [addr] [@option{p}] [config_file] [real_config_file]
|
||||
This command is fairly complex, and you should not use this command
|
||||
unless you are familiar with GRUB. In short, it will perform a full
|
||||
install presuming the Stage 2 or Stage 1.5@footnote{They're loaded the
|
||||
|
@ -839,19 +839,23 @@ is in its final install location.
|
|||
|
||||
In slightly more detail, it will load @var{stage1_file}, validate that
|
||||
it is a GRUB Stage 1 of the right version number, install a blocklist for
|
||||
loading @var{file} as a Stage 2. If the option @option{d} is present, the
|
||||
Stage 1 will always look for the actual disk @var{file} was installed on,
|
||||
rather than using the booting drive. The Stage 2 will be loaded at
|
||||
address @var{addr}, which must be @samp{0x8000} for a true Stage 2, and
|
||||
@samp{0x2000} for a Stage 1.5. If @var{addr} is not present, GRUB will
|
||||
determine the address automatically. It then writes the completed Stage 1
|
||||
to the first block of the device @var{dest_dev}. If the options @option{p}
|
||||
or @var{config_file} are present, then it reads the first block of
|
||||
stage2, modifies it with the values of the partition @var{file} was
|
||||
found on (for @option{p}) or places the string @var{config_file} into the
|
||||
area telling the stage2 where to look for a configuration file at boot
|
||||
time. This command preserves the DOS BPB (and for hard disks, the
|
||||
partition table) of the sector the Stage 1 is to be installed into.
|
||||
loading @var{stage2_file} as a Stage 2. If the option @option{d} is
|
||||
present, the Stage 1 will always look for the actual disk
|
||||
@var{stage2_file} was installed on, rather than using the booting
|
||||
drive. The Stage 2 will be loaded at address @var{addr}, which must be
|
||||
@samp{0x8000} for a true Stage 2, and @samp{0x2000} for a Stage 1.5. If
|
||||
@var{addr} is not present, GRUB will determine the address
|
||||
automatically. It then writes the completed Stage 1 to the first block
|
||||
of the device @var{dest_dev}. If the options @option{p} or
|
||||
@var{config_file} are present, then it reads the first block of stage2,
|
||||
modifies it with the values of the partition @var{stage2_file} was found
|
||||
on (for @option{p}) or places the string @var{config_file} into the area
|
||||
telling the stage2 where to look for a configuration file at boot
|
||||
time. Likewise, if @var{real_config_file} is present and
|
||||
@var{stage2_file} is a Stage 1.5, then the Stage 2 @var{config_file} is
|
||||
patched with the configuration filename @var{real_config_file}. This
|
||||
command preserves the DOS BPB (and for hard disks, the partition table)
|
||||
of the sector the Stage 1 is to be installed into.
|
||||
@end deffn
|
||||
|
||||
@deffn Command ioprobe drive
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue