vbatts/grub
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

* docs/grub.texi (Installing GRUB using grub-install): Proofread.

Browse source 
(Supported kernels): Likewise.
This commit is contained in:
Colin Watson 2010-10-22 14:17:33 +01:00
parent b65ea15514
commit 0cbcdf0e6f
2 changed files with 15 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
ChangeLog
View file

@ -1,3 +1,8 @@
2010-10-22 Colin Watson <cjwatson@ubuntu.com>
* docs/grub.texi (Installing GRUB using grub-install): Proofread.
(Supported kernels): Likewise.
2010-10-18 Grégoire Sutre <gregoire.sutre@gmail.com> 2010-10-18 Grégoire Sutre <gregoire.sutre@gmail.com>
Make mktemp invocations portable. Make mktemp invocations portable.

19
docs/grub.texi
View file

@ -559,11 +559,12 @@ always. Therefore, GRUB provides you with a map file called the
@dfn{device map}, which you must fix if it is wrong. @xref{Device @dfn{device map}, which you must fix if it is wrong. @xref{Device
map}, for more details. map}, for more details.
On BIOS platforms GRUB has to use a so called embedding zone. On msdos On BIOS platforms GRUB has to use a so-called embedding zone. On msdos
partition tables it's the space between MBR and first partition (called partition tables, this is the space between the MBR and the first partition
MBR gap), on GPT partition it uses a BIOS Boot Partition (a partition (called the MBR gap or the boot track), while on GPT partition tables it
having type 21686148-6449-6e6f-744e656564454649). If you use GRUB on uses a BIOS Boot Partition (a partition with GUID
BIOS be sure to supply at least 31 KiB of embedding zone (512KiB or more 21686148-6449-6e6f-744e656564454649). If you use GRUB on a BIOS system, make
sure that the embedding zone is at least 31 KiB (512KiB or more
recommended). recommended).
If you still do want to install GRUB under a UNIX-like OS (such If you still do want to install GRUB under a UNIX-like OS (such
@ -617,9 +618,9 @@ installation. The format is defined in @ref{Device map}. Please be
quite careful. If the output is wrong, it is unlikely that your quite careful. If the output is wrong, it is unlikely that your
computer will be able to boot with no problem. computer will be able to boot with no problem.
Some BIOSes have a bug of exposing first partition of USB pendrive as a floppy Some BIOSes have a bug of exposing the first partition of a USB drive as a
instead of exposing pendrive as a hard disk (they call it ``USB-FDD'' boot) floppy instead of exposing the USB drive as a hard disk (they call it
In such cases you need to install as following: ``USB-FDD'' boot). In such cases, you need to install like this:
@example @example
# @kbd{losetup /dev/loop0 /dev/sdb1} # @kbd{losetup /dev/loop0 /dev/sdb1}
@ -3295,7 +3296,7 @@ commands.
@node Supported kernels @node Supported kernels
@chapter Supported boot targets @chapter Supported boot targets
X86 support is summarised in following table. ``Yes'' means that kernel works on the given platform, ``crashes'' means an early kernel crash which we hove will be fixed by concerned kernel developpers. ``no'' means GRUB doesn't load given kernel on a given platform. ``headless'' means that the kernel works but lacks console drivers (you can still use serial or network console). In case of ``no'' and ``crashes'' the reason is given in footnote. X86 support is summarised in the following table. ``Yes'' means that the kernel works on the given platform, ``crashes'' means an early kernel crash which we hope will be fixed by concerned kernel developers. ``no'' means GRUB doesn't load the given kernel on a given platform. ``headless'' means that the kernel works but lacks console drivers (you can still use serial or network console). In case of ``no'' and ``crashes'' the reason is given in footnote.
@multitable @columnfractions .50 .22 .22 @multitable @columnfractions .50 .22 .22
@item @tab BIOS @tab Coreboot @item @tab BIOS @tab Coreboot
@item BIOS chainloading @tab yes @tab no (1) @item BIOS chainloading @tab yes @tab no (1)