- Timestamp:
- Jul 11, 2006, 10:28:53 AM (18 years ago)
- Children:
- e28d682b
- Parents:
- a9b8538
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
bootable/x86_64-64/lilo.xml
ra9b8538 rdc64755 18 18 <para os="a">Your shiny new CLFS system is almost complete. One of the 19 19 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, 21 21 which in the context of this book means x86_64 Pure64 systems. 22 22 Information on <quote>boot loading</quote> for other architectures … … 29 29 30 30 <para os="c">If you have multiple systems on your machine using a 31 different bootloader such as G rub, you may prefer to use that31 different bootloader such as GRUB, you may prefer to use that 32 32 instead - consult the appropriate documentation. The rest of 33 33 this section assumes you are going to use Lilo.</para> … … 40 40 loopback block device support in the kernel).</para> 41 41 42 <para os="e">Normally, you interact with lilo by using the cursor42 <para os="e">Normally, you interact with Lilo by using the cursor 43 43 and <literal>enter</literal> keys to select from the available 44 44 option(s), but sometimes it is necessary to add other boot 45 45 options, such as e.g. 'init=/bin/bash' to debug boot failures. 46 46 The more your keyboard layout differs from the US qwerty layout, 47 the harder it becomes to type boot options unless lilo knows47 the harder it becomes to type boot options unless Lilo knows 48 48 about your keyboard layout. So, we will create a key table for 49 49 Lilo (.ktl) file - at one point in the documentation these are … … 117 117 <note os='o'> 118 118 <para>People who have been used to GRUB need to be aware that 119 lilo works differently - in particular, you cannot edit the120 available choices as you can in the grub shell, and lilo records121 the block addresses of the kernels into the boot blocks each time122 /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. It124 also means that if you recompile an existing kernel and save it125 to the same name you still have to rerun /sbin/lilo in case it now126 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> 127 127 </note> 128 128 129 129 <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 running131 the same version of lilo, otherwise an old version may not be able130 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 132 132 to overwrite the bootloader from a newer version. You will also 133 133 need to ensure that the copies of /etc/lilo.conf on each system are
Note:
See TracChangeset
for help on using the changeset viewer.