change the option name root to root-directory for grub-install, update the FAQ.
This commit is contained in:
parent
b92f3d57e2
commit
a92313f507
5 changed files with 48 additions and 9 deletions
|
@ -11,7 +11,7 @@ order for everybody to participate it.
|
|||
|
||||
Technically speaking, GNU GRUB has many features that are not
|
||||
seen in the original GRUB. For example, GNU GRUB can be installed on
|
||||
UNIX-like operating system (i.e. GNU/Linux) via the grub shell
|
||||
UNIX-like operating system (such as GNU/Linux) via the grub shell
|
||||
@file{/sbin/grub}, it supports Logical Block Address (LBA) mode that
|
||||
solves the 1024 cylinders problem, and @kbd{@key{TAB}} completes a
|
||||
filename when it's unique. Of course, many bug fixes are done as well,
|
||||
|
@ -109,6 +109,29 @@ $ ./configure --with-binutils=/usr/local/bin
|
|||
If you follow the instructions above but GRUB still crashes, probably
|
||||
there is a serious bug in GRUB. @xref{Reporting bugs}.
|
||||
|
||||
@item GRUB hangs up when accessing my SCSI disk.
|
||||
|
||||
Check if you have turned on the support for INT 13 extension (LBA). If
|
||||
so, disable the support and see if GRUB can now access your SCSI
|
||||
disk. This will make it clear that your SCSI BIOS sucks.
|
||||
|
||||
For now, we know the following doesn't provide working LBA mode:
|
||||
|
||||
@table @asis
|
||||
@item
|
||||
Adaptec AIC-7880
|
||||
@end table
|
||||
|
||||
In the case where you have such a SCSI controller unfortunately, you
|
||||
cannot use the LBA mode, though GRUB still works fine in the CHS mode
|
||||
(so the well-known 1024 cylinders problem comes again to you).
|
||||
|
||||
@strong{Caution:} Actually it has not been verified yet if this bug is
|
||||
due to the SCSI BIOS or GRUB itself, frankly speaking. Because the
|
||||
developers haven't seen it by their own eyes. This is why it is
|
||||
desirable that you investigate the cause seriously if you have the
|
||||
skill.
|
||||
|
||||
@item Why doesn't Linux (FreeBSD, NetBSD, etc.) become Multiboot-compliant?
|
||||
|
||||
Please ask the maintainers. If all free kernels were
|
||||
|
|
|
@ -14,7 +14,7 @@ print this message and exit
|
|||
\fB\-v\fR, \fB\-\-version\fR
|
||||
print the version information and exit
|
||||
.TP
|
||||
\fB\-\-root\fR=\fIDIR\fR
|
||||
\fB\-\-root\-directory\fR=\fIDIR\fR
|
||||
install GRUB images under the directory DIR
|
||||
instead of the root directory.
|
||||
.TP
|
||||
|
|
|
@ -1388,10 +1388,15 @@ Print a summary of the command line options and exit.
|
|||
@item --version
|
||||
Print the version number of GRUB and exit.
|
||||
|
||||
@item --root=@var{dir}
|
||||
@item --root-directory=@var{dir}
|
||||
Install GRUB images under the directory @var{dir} instead of the root
|
||||
directory. This option is useful when you want to install GRUB into a
|
||||
separate partition and a removable disk.
|
||||
separate partition or a removable disk. Here is an example when you have
|
||||
a separate @dfn{boot} partition which is mounted on @file{/boot}:
|
||||
|
||||
@example
|
||||
grub-install --root-directory=/boot '(hd0)'
|
||||
@end example
|
||||
|
||||
@item --grub-shell=@var{file}
|
||||
Use @var{file} as the grub shell. You can append arbitrary options to
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue