Changeset dc64755


Ignore:
Timestamp:
Jul 11, 2006, 10:28:53 AM (13 years ago)
Author:
Chris Staub <chris@…>
Children:
e28d682b
Parents:
a9b8538
Message:

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

Files:
7 edited

Legend:

Unmodified
Added
Removed
  • boot/x86_64-64/bin86.xml

    ra9b8538 rdc64755  
    2323    <title>Installation of Bin86</title>
    2424
    25     <para os="a">We are building bin86 so that we can compile lilo.
     25    <para os="a">We are building Bin86 so that we can compile Lilo.
    2626      Both <command>as86</command> and <command>ld86</command> need to
    2727      run on the host system to assemble x86_64 code.  We cannot
     
    4545
    4646    <para os="e">Install the assembler and linker where they will be on
    47       the PATH when we build lilo, using prefixes to show that their
     47      the PATH when we build Lilo, using prefixes to show that their
    4848      output is not for a native system.</para>
    4949
  • boot/x86_64-64/bootloaders.xml

    ra9b8538 rdc64755  
    1212
    1313    <para>On x86 and x86_64 (multilib) architectures, the preferred
    14       bootloader is Grub.  Unfortunately, Grub doesn&quot;t work on x86_64
     14      bootloader is GRUB.  Unfortunately, GRUB doesn't work on x86_64
    1515      Pure64 - the stage2 files can be correctly built as 32-bit, but the
    16       grub shell is a 64-bit program, and tries to execute some of the
    17       stage2 routines - this results in a segmentation fault. Therefore,
    18       in the final system we use Lilo as the bootloader.
     16      <command>grub</command> shell is a 64-bit program, and tries to
     17      execute some of the stage2 routines - this results in a segmentation
     18      fault. Therefore, in the final system we use Lilo as the bootloader.
    1919    </para>
    2020
    21     <para>If you already have a bootloader, such as Grub, installed on
     21    <para>If you already have a bootloader, such as GRUB, installed on
    2222      the system then you should use that to make your new kernel bootable.
    2323   </para>
  • boot/x86_64-64/lilo-build.xml

    ra9b8538 rdc64755  
    2323    <title>Installation of Lilo</title>
    2424
    25     <para os="a">The following patch forces lilo to use our cross-compiler
     25    <para os="a">The following patch forces Lilo to use our cross-compiler
    2626      (except for a couple of utilities which run during the compile),
    2727      and to look for as86 and ld86 under the names by which we installed
  • boot/x86_64-64/lilo.xml

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

    ra9b8538 rdc64755  
    1818    <para os="a">Your shiny new CLFS system is almost complete. One of the
    1919      last things to do is to ensure that the system can be properly
    20       booted. The instructions below apply only to computers using lilo,
     20      booted. The instructions below apply only to computers using Lilo,
    2121      which in the context of this book means x86_64 Pure64 systems.
    2222      Information on <quote>boot loading</quote> for other architectures
     
    2929
    3030    <para os="c">If you have multiple systems on your machine using a
    31       different bootloader such as Grub, you may prefer to use that
     31      different bootloader such as GRUB, you may prefer to use that
    3232      instead - consult the appropriate documentation.  The rest of
    3333      this section assumes you are going to use Lilo.</para>
     
    4040      loopback block device support in the kernel).</para>
    4141
    42     <para os="e">Normally, you interact with lilo by using the cursor
     42    <para os="e">Normally, you interact with Lilo by using the cursor
    4343      and <literal>enter</literal> keys to select from the available
    4444      option(s), but sometimes it is necessary to add other boot
    4545      options, such as e.g. 'init=/bin/bash' to debug boot failures.
    4646      The more your keyboard layout differs from the US qwerty layout,
    47       the harder it becomes to type boot options unless lilo knows
     47      the harder it becomes to type boot options unless Lilo knows
    4848      about your keyboard layout. So, we will create a key table for
    4949      Lilo (.ktl) file - at one point in the documentation these are
     
    117117  <note os='o'>
    118118    <para>People who have been used to GRUB need to be aware that
    119       lilo works differently - in particular, you cannot edit the
    120       available choices as you can in the grub shell, and lilo records
    121       the block addresses of the kernels into the boot blocks each time
    122       /sbin/lilo is run. This means that when you compile a new kernel,
    123       you have to add it to /etc/lilo.conf and rerun /sbin/lilo.  It
    124       also means that if you recompile an existing kernel and save it
    125       to the same name you still have to rerun /sbin/lilo in case it now
    126       occupies different blocks on the filesystem.</para>
     119      Lilo works differently - in particular, you cannot edit the
     120      available choices as you can in the <command>grub</command> shell,
     121      and Lilo records the block addresses of the kernels into the boot
     122      blocks each time /sbin/lilo is run. This means that when you
     123      compile a new kernel, you have to add it to /etc/lilo.conf and
     124      rerun /sbin/lilo.  It also means that if you recompile an existing
     125      kernel and save it to the same name you still have to rerun /sbin/lilo
     126      in case it now occupies different blocks on the filesystem.</para>
    127127  </note>
    128128
    129129    <para os="p">If you are running multiple systems on this box and
    130     using lilo, it is a good idea to ensure that each system is running
    131     the same version of lilo, otherwise an old version may not be able
     130    using Lilo, it is a good idea to ensure that each system is running
     131    the same version of Lilo, otherwise an old version may not be able
    132132    to overwrite the bootloader from a newer version.  You will also
    133133    need to ensure that the copies of /etc/lilo.conf on each system are
  • final-system/x86_64-64/bin86.xml

    ra9b8538 rdc64755  
    2626    <title>Installation of Bin86</title>
    2727
    28     <para os="a">We are building bin86 because it is required to
    29       compile lilo, and at the moment no other bootloader builds and runs
     28    <para os="a">We are building Bin86 because it is required to
     29      compile Lilo, and at the moment no other bootloader builds and runs
    3030      on a pure64 system. If your machine has multiple systems (i.e. x86
    3131      or multilib) you may prefer to use the bootloader from those
    32       systems, such as grub.</para>
     32      systems, such as GRUB.</para>
    3333
    34     <para os="p1">This patch updates bin86 to compile on x86_64:</para>
     34    <para os="p1">This patch updates Bin86 to compile on x86_64:</para>
    3535
    3636<screen os="p2"><userinput>patch -Np1 -i ../&bin86-x86_64-patch;</userinput></screen>
  • final-system/x86_64-64/lilo.xml

    ra9b8538 rdc64755  
    1919    <para os="a">The Lilo package contains the Linux Loader, a bootloader.</para>
    2020
    21     <para os="b">We have chosen to use lilo because at the moment no other
     21    <para os="b">We have chosen to use Lilo because at the moment no other
    2222      bootloader builds and runs on a pure64 system. If your machine has
    2323      multiple systems (i.e. x86 or multilib) you may prefer to use the
    24       bootloader from the other system, such as grub.</para>
     24      bootloader from the other system, such as GRUB.</para>
    2525
    2626  </sect2>
     
    4040    <para>At the end of the installation the make install process will
    4141      print a message stating that /sbin/lilo has to be executed to
    42       complete the update. Don&quot;t do this as it has no use. The
    43       /etc/lilo.conf isn&quot;t present yet. We will complete the
    44       installation of lilo in chapter 12.</para>
     42      complete the update. Don't do this as it has no use. The
     43      /etc/lilo.conf isn't present yet. We will complete the
     44      installation of Lilo in chapter 12.</para>
    4545
    4646  </sect2>
Note: See TracChangeset for help on using the changeset viewer.