10.0
10.0-rc1
10.1
10.1-rc1
11.0
11.0-rc1
11.0-rc2
11.0-rc3
11.1
11.1-rc1
11.2
11.2-rc1
11.3
11.3-rc1
12.0
12.0-rc1
12.1
12.1-rc1
6.0
6.1
6.1.1
6.3
6.4
6.5
6.6
6.7
6.8
7.0
7.1
7.2
7.3
7.4
7.5
7.5-systemd
7.6
7.6-systemd
7.7
7.7-systemd
7.8
7.8-systemd
7.9
7.9-systemd
8.0
8.1
8.2
8.3
8.4
9.0
9.1
arm
bdubbs/gcc13
ml-11.0
multilib
renodr/libudev-from-systemd
s6-init
trunk
v3_0
v3_1
v3_2
v3_3
v4_0
v4_1
v5_0
v5_1
v5_1_1
xry111/arm64
xry111/arm64-12.0
xry111/clfs-ng
xry111/lfs-next
xry111/loongarch
xry111/loongarch-12.0
xry111/loongarch-12.1
xry111/mips64el
xry111/pip3
xry111/rust-wip-20221008
xry111/update-glibc
| Line | |
|---|
| 1 | <sect2>
|
|---|
| 2 | <title>Configuring Lilo</title>
|
|---|
| 3 |
|
|---|
| 4 | <para>
|
|---|
| 5 | We're not going to create lilo's configuration file from scratch, but we'll
|
|---|
| 6 | use the file from the normal Linux system. This file is different on every
|
|---|
| 7 | machine and thus I can't create it here. Since a user would want to have the
|
|---|
| 8 | same options regarding lilo as he has when he is using his normal Linux
|
|---|
| 9 | system he would create the file exactly as it is on the normal system.
|
|---|
| 10 | </para>
|
|---|
| 11 |
|
|---|
| 12 | <para>
|
|---|
| 13 | Copy the Lilo configuration file and kernel images that Lilo uses by
|
|---|
| 14 | running the following commands from a shell on the normal Linux system.
|
|---|
| 15 | Don't execute these commands from the chroot'ed shell.
|
|---|
| 16 | </para>
|
|---|
| 17 |
|
|---|
| 18 | <blockquote><literallayout>
|
|---|
| 19 |
|
|---|
| 20 | <userinput>cp /etc/lilo.conf $LFS/etc</userinput>
|
|---|
| 21 | <userinput>cp /boot/<kernel images> $LFS/boot</userinput>
|
|---|
| 22 |
|
|---|
| 23 | </literallayout></blockquote>
|
|---|
| 24 |
|
|---|
| 25 | <para>
|
|---|
| 26 | Before a user can execute the second command he needs to know the names of
|
|---|
| 27 | the kernel images. He can't just copy all files from the /boot
|
|---|
| 28 | directory. The /etc/lilo.conf file contains the names of the kernel
|
|---|
| 29 | images he is using. Open the file and look for lines like this:
|
|---|
| 30 | </para>
|
|---|
| 31 |
|
|---|
| 32 | <blockquote><literallayout>
|
|---|
| 33 |
|
|---|
| 34 | image=/boot/vmlinuz
|
|---|
| 35 |
|
|---|
| 36 | </literallayout></blockquote>
|
|---|
| 37 |
|
|---|
| 38 | <para>
|
|---|
| 39 | Look for all <emphasis>image</emphasis> variables and their values
|
|---|
| 40 | represent the name and location of the image files. These files will
|
|---|
| 41 | usually be in /boot but they might be in other directories as well,
|
|---|
| 42 | depending on the distribution's conventions.
|
|---|
| 43 | </para>
|
|---|
| 44 |
|
|---|
| 45 | </sect2>
|
|---|
| 46 |
|
|---|
Note:
See
TracBrowser
for help on using the repository browser.
