Changeset dc64755 for boot

Timestamp:

Jul 11, 2006, 10:28:53 AM (18 years ago)

Author:

Chris Staub <chris@…>

Children:

e28d682b

Parents:

a9b8538

Message:

Text fixes, mainly in capitalization in the names of Lilo and GRUB

Location:

boot/x86_64-64

Files:

• bin86.xml (modified) (2 diffs)
• bootloaders.xml (modified) (1 diff)
• lilo-build.xml (modified) (1 diff)
• lilo.xml (modified) (3 diffs)

boot/x86_64-64/bin86.xml

@@ -23 +23 @@
     <title>Installation of Bin86</title>
 
-    <para os="a">We are building bin86 so that we can compile lilo.
+    <para os="a">We are building Bin86 so that we can compile Lilo.
       Both <command>as86</command> and <command>ld86</command> need to
       run on the host system to assemble x86_64 code.  We cannot
@@ -45 +45 @@
 
     <para os="e">Install the assembler and linker where they will be on
-      the PATH when we build lilo, using prefixes to show that their
+      the PATH when we build Lilo, using prefixes to show that their
       output is not for a native system.</para>
 

boot/x86_64-64/bootloaders.xml

@@ -12 +12 @@
 
     <para>On x86 and x86_64 (multilib) architectures, the preferred
-      bootloader is Grub.  Unfortunately, Grub doesn&quot;t work on x86_64
+      bootloader is GRUB.  Unfortunately, GRUB doesn't work on x86_64
       Pure64 - the stage2 files can be correctly built as 32-bit, but the
-      grub 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.
+      <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
+    <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>

boot/x86_64-64/lilo-build.xml

@@ -23 +23 @@
     <title>Installation of Lilo</title>
 
-    <para os="a">The following patch forces lilo to use our cross-compiler
+    <para os="a">The following patch forces Lilo to use our cross-compiler
       (except for a couple of utilities which run during the compile),
       and to look for as86 and ld86 under the names by which we installed

boot/x86_64-64/lilo.xml

@@ -18 +18 @@
   <para os="a">You are nearly ready to boot to the new temporary system.
   One of the last things to do is to ensure that the system can be booted.
-  The instructions below apply only to x86_64 machines on which lilo is going
-  to be installed. Information on using a pre-installed Grub on machines
+  The instructions below apply only to x86_64 machines on which Lilo is going
+  to be installed. Information on using a pre-installed GRUB on machines
   currently running as x86 or x86_64 multilib should be available in the
   usual resource-specific locations for those architectures.  If you have
-  installed an x86 version of lilo, these instructions should be modified
+  installed an x86 version of Lilo, these instructions should be modified
   to refer to the <command>lilo</command> and <command>keytab-lilo.pl
   </command> commands you installed on the host system.</para>
@@ -31 +31 @@
 
   <para os="c">If you have multiple systems on your machine using a different
-  bootloader such as grub, you may prefer to use that instead - consult the
+  bootloader such as GRUB, you may prefer to use that instead - consult the
   appropriate documentation.  The rest of this section assumes you are going
-  to use lilo.</para> 
+  to use Lilo.</para> 
 
   <para os="d">Earlier, we compiled and installed the Lilo boot loader software
@@ -42 +42 @@
   dvdrtools) as a test and as a backup.</para>
 
-  <para os="e">Normally, you interact with lilo by using the cursor and enter
+  <para os="e">Normally, you interact with Lilo by using the cursor and enter
   keys to select from the available option(s), but sometimes it is necessary to
   add other boot options, such as e.g. 'init=/bin/bash' to debug boot failures.
   The more your keyboard layout differs from the US qwerty layout, the harder
-  it will be to type boot options unless lilo knows about your keyboard layout.
+  it will be to type boot options unless Lilo knows about your keyboard layout.
   So, we will create a key table for Lilo (.ktl) file - at one point in the
   documentation these are referred to as .klt files, which may be a typo, but