| 1 | <sect1 id="ch08-lilo">
|
|---|
| 2 | <title>Making the LFS system bootable</title>
|
|---|
| 3 |
|
|---|
| 4 | <para>
|
|---|
| 5 | In order to being able to boot the LFS system, we need to update our
|
|---|
| 6 | bootloader. We're assuming that your host system is using Lilo (since
|
|---|
| 7 | that's the most commonly used boot loader at the moment).
|
|---|
| 8 | </para>
|
|---|
| 9 |
|
|---|
| 10 | <para>
|
|---|
| 11 | We will not be running the lilo program inside chroot. Running lilo
|
|---|
| 12 | inside chroot can have fatal side-effects which render your MBR useles
|
|---|
| 13 | and you'd need a boot disk to be able to start any Linux system (either
|
|---|
| 14 | the host system or the LFS system).
|
|---|
| 15 | </para>
|
|---|
| 16 |
|
|---|
| 17 | <para>
|
|---|
| 18 | First we'll exit chroot and copy the lfskernel file to the host system:
|
|---|
| 19 | </para>
|
|---|
| 20 |
|
|---|
| 21 | <blockquote><literallayout>
|
|---|
| 22 |
|
|---|
| 23 | <userinput>logout &&</userinput>
|
|---|
| 24 | <userinput>cp $LFS/boot/lfskernel /boot
|
|---|
| 25 | &&</userinput>
|
|---|
| 26 |
|
|---|
| 27 | </literallayout></blockquote>
|
|---|
| 28 |
|
|---|
| 29 | <para>
|
|---|
| 30 | The next step is adding an entry to /etc/lilo.conf so that we can
|
|---|
| 31 | choose LFS when booting the computer:
|
|---|
| 32 | </para>
|
|---|
| 33 |
|
|---|
| 34 | <literallayout>
|
|---|
| 35 |
|
|---|
| 36 | <userinput>cat >> /etc/lilo.conf << "EOF"</userinput>
|
|---|
| 37 | image=/boot/lfskernel
|
|---|
| 38 | label=lfs
|
|---|
| 39 | root=<partition>
|
|---|
| 40 | read-only
|
|---|
| 41 | <userinput>EOF</userinput>
|
|---|
| 42 |
|
|---|
| 43 | </literallayout>
|
|---|
| 44 |
|
|---|
| 45 | <para>
|
|---|
| 46 | <partition> must be replaced by the LFS partition's designation.
|
|---|
| 47 | </para>
|
|---|
| 48 |
|
|---|
| 49 | <para>
|
|---|
| 50 | Now the boot loader gets updated by running:
|
|---|
| 51 | </para>
|
|---|
| 52 |
|
|---|
| 53 | <blockquote><literallayout>
|
|---|
| 54 |
|
|---|
| 55 | <userinput>/sbin/lilo</userinput>
|
|---|
| 56 |
|
|---|
| 57 | </literallayout></blockquote>
|
|---|
| 58 |
|
|---|
| 59 | <para>
|
|---|
| 60 | The last step is syncing the host system lilo config. files with the
|
|---|
| 61 | LFS system:
|
|---|
| 62 | </para>
|
|---|
| 63 |
|
|---|
| 64 | <blockquote><literallayout>
|
|---|
| 65 |
|
|---|
| 66 | <userinput>cp /etc/lilo.conf $LFS/etc &&</userinput>
|
|---|
| 67 | <userinput>cp <kernel images> $LFS/boot</userinput>
|
|---|
| 68 |
|
|---|
| 69 | </literallayout></blockquote>
|
|---|
| 70 |
|
|---|
| 71 | <para>
|
|---|
| 72 | To find out which kernel images files are being used, look at the
|
|---|
| 73 | /etc/lilo.conf file and find the lines starting with
|
|---|
| 74 | <emphasis>image=</emphasis>. If your host system has kernel files in
|
|---|
| 75 | other places than the /boot directory, make sure you update the paths
|
|---|
| 76 | in the $LFS/etc/lilo.conf file so that it does look for them in the
|
|---|
| 77 | /boot directory.
|
|---|
| 78 | </para>
|
|---|
| 79 |
|
|---|
| 80 | </sect1>
|
|---|
| 81 |
|
|---|
