[install-guide: 9/18] Added a few comments about GPT

[Pete Travis]

commit a40c5f39c639b9c13a86f98cd4c938f9616e883e
Author: Pete Travis <immanetize at fedoraproject.org>
Date:   Mon Sep 10 23:32:04 2012 -0600

    Added a few comments about GPT

 en-US/Boot_Init_Shutdown.xml |   19 +++++++++++++------
 1 files changed, 13 insertions(+), 6 deletions(-)
---
diff --git a/en-US/Boot_Init_Shutdown.xml b/en-US/Boot_Init_Shutdown.xml
index feb883f..dc777bf 100644
--- a/en-US/Boot_Init_Shutdown.xml
+++ b/en-US/Boot_Init_Shutdown.xml
@@ -129,13 +129,24 @@
 					<secondary>definition of</secondary>
 					<seealso>boot loaders</seealso>
 				</indexterm>
+				<indexterm>
+				  <primary>GUID Partition Table</primary>
+				  <see>GPT</see>
+				<indexterm significance="normal">
+				  <primary>GPT</primary>
+				  <secondary>definition of</secondary>
+				</indexterm>
 				<para>
 					The <firstterm>Basic Input/Output System</firstterm> (BIOS) is a firmware interface that controls not only the first step of the boot process, but also provides the lowest level interface to peripheral devices. On x86 systems equipped with BIOS, the program is written into read-only, permanent memory and is always available for use. When the system boots, the processor looks at the end of system memory for the BIOS program, and runs it.
 				</para>
 				<para>
-					Once loaded, the BIOS tests the system, looks for and checks peripherals, and then locates a valid device with which to boot the system. Usually, it checks any optical drives or USB storage devices present for bootable media, then, failing that, looks to the system's hard drives. In most cases, the order of the drives searched while booting is controlled with a setting in the BIOS, and it looks on the master IDE on the primary IDE bus or for a SATA device with a boot flag set. The BIOS then loads into memory whatever program is residing in the first sector of this device, called the <firstterm>Master Boot Record</firstterm> (MBR). The MBR is only 512 bytes in size and contains machine code instructions for booting the machine, called a boot loader, along with the partition table. Once the BIOS finds and loads the boot loader program into memory, it yields control of the boot process to it.
+					Once loaded, the BIOS tests the system, looks for and checks peripherals, and then locates a valid device with which to boot the system. Usually, it checks any optical drives or USB storage devices present for bootable media, then, failing that, looks to the system's hard drives. In most cases, the order of the drives searched while booting is controlled with a setting in the BIOS, and it looks for bootable media in the specified order.
 				</para>
 				<para>
+A disk may either have a <firstterm>Master Boot Record</firstterm> (MBR) or a <firstterm>GUID Partition Table</firstterm> (GPT). The <systemitem>MBR</systemitem> is only 512 bytes in size and contains machine code instructions for booting the machine, called a boot loader, along with the partition table. The newer <systemitem>GPT</systemitem> serves the same role and allows for more and larger partitions, but is generally used on newer <systemitem>UEFI</systemitem> systems. Once the BIOS finds and loads the boot loader program into memory, it yields control of the boot process to it.
+				</para>
+
+				<para>
 					This first-stage boot loader is a small machine code binary on the MBR. Its sole job is to locate the second stage boot loader (<application>GRUB</application>) and load the first part of it into memory.
 				</para>
 			</section>
@@ -187,11 +198,7 @@
 				<para>
 					<application>GRUB</application> version 2 has the advantage of being able to read a variety of open filesystems, as well as virtual devices such as <application>mdadm</application> RAID arrays and <application>LVM</application> .
 				</para>
-				<!-- I want to verify this!
-				     <footnote> <para>
-				 GRUB reads ext3 and ext4 file systems as ext2, disregarding the journal file.
-				</para>
-				</footnote>-->
+			
 <para>
  GRUB mounts a designated partition and load its configuration file &mdash; <filename>/boot/grub2/grub.cfg</filename> (for BIOS) or <filename>/boot/efi/EFI/redhat/grub.cfg</filename> (for UEFI) &mdash; at boot time. Refer to <xref linkend="s1-grub-configfile" /> for information on how to edit this file.
 				</para>