Changeset 3df6c70 for BOOK/bootable


Ignore:
Timestamp:
Jul 11, 2006, 10:28:53 AM (14 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:
37efcbc
Parents:
adb2d7f
Message:

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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • BOOK/bootable/x86_64-64/lilo.xml

    radb2d7f r3df6c70  
    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
Note: See TracChangeset for help on using the changeset viewer.