| 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354 | <sect1 id="ch08-lilo"><title>Making the LFS system bootable</title><para>In order to being able to boot the LFS system, we need to update ourbootloader. We're assuming that your host system is using Lilo (sincethat's the most commonly used boot loader at the moment).</para><para>We will not be running the lilo program inside chroot. Running liloinside chroot can have fatal side-effects which render your MBR uselessand you'd need a boot disk to be able to start any Linux system (eitherthe host system or the LFS system).</para><para>First we'll exit chroot and copy the lfskernel file to the host system:</para><para><screen><userinput>logout</userinput><userinput>cp $LFS/boot/lfskernel /boot</userinput></screen></para><para>The next step is adding an entry to /etc/lilo.conf so that we canchoose LFS when booting the computer:</para><para><screen><userinput>cat >> /etc/lilo.conf << "EOF"</userinput>image=/boot/lfskernel        label=lfs        root=<partition>        read-only<userinput>EOF</userinput></screen></para><para><partition> must be replaced by the LFS partition's designation.</para><para>Now the boot loader gets updated by running:</para><para><screen><userinput>/sbin/lilo</userinput></screen></para><para>The last step is syncing the host system lilo config. files with theLFS system:</para><para><screen><userinput>cp /etc/lilo.conf $LFS/etc &&</userinput><userinput>cp <kernel images> $LFS/boot</userinput></screen></para><para>To find out which kernel images files are being used, look at the/etc/lilo.conf file and find the lines starting with<emphasis>image=</emphasis>. If your host system has kernel files inother places than the /boot directory, make sure you update the pathsin the $LFS/etc/lilo.conf file so that it does look for them in the/boot directory.</para><para>As soon as we have booted into LFS we can run<userinput>/sbin/lilo</userinput> from the LFS system in order to havethe latest Lilo version in the MBR.</para></sect1>
 |