Changeset 883964a for BOOK/boot/x86_64-64/bootloaders.xml

Timestamp:

Jun 2, 2009, 12:34:13 AM (15 years ago)

Author:

Chris Staub <chris@…>

Branches:

clfs-1.2, clfs-2.1, clfs-3.0.0-systemd, clfs-3.0.0-sysvinit, master, systemd, sysvinit

Children:

a0833ff

Parents:

94c04f1

Message:

Indentation consistency

File:

• BOOK/boot/x86_64-64/bootloaders.xml (modified) (1 diff)

BOOK/boot/x86_64-64/bootloaders.xml

@@ -12 +12 @@
 
     <para>On x86 and x86_64 (multilib) architectures, the preferred
-      bootloader is GRUB.  Unfortunately, GRUB doesn't work on x86_64
-      Pure64 - the stage2 files can be correctly built as 32-bit, but the
-      <command>grub</command> shell is a 64-bit program, and tries to
-      execute some of the stage2 routines - this results in a segmentation
-      fault. Therefore, in the final system we use Lilo as the bootloader.
+    bootloader is GRUB. Unfortunately, GRUB doesn't work on x86_64
+    Pure64 - the stage2 files can be correctly built as 32-bit, but the
+    <command>grub</command> shell is a 64-bit program, and tries to
+    execute some of the stage2 routines - this results in a segmentation
+    fault. Therefore, in the final system we use Lilo as the bootloader.
     </para>
 
     <para>If you already have a bootloader, such as GRUB, installed on
-      the system then you should use that to make your new kernel bootable.
-   </para>
+    the system then you should use that to make your new kernel bootable.
+    </para>
 
   <note>
     <para>We will now cross-compile Bin86 and Lilo - these instructions 
-      assume you are using an x86_64 machine (e.g. booted fron a Live CD),
-      either pure64 or multilib. This approach will not work if you are
-      running the machine as i686, because a 32-bit kernel will not be
-      able to execute a 64-bit binary to install the bootloader.  If that
-      is the case, you will need to install an i686 bootloader on the
-      host system. 
+    assume you are using an x86_64 machine (e.g. booted fron a Live CD),
+    either pure64 or multilib. This approach will not work if you are
+    running the machine as i686, because a 32-bit kernel will not be
+    able to execute a 64-bit binary to install the bootloader. If that
+    is the case, you will need to install an i686 bootloader on the
+    host system. 
     </para>
   </note>