From 908631a62ddf378934c7b83e4f9bab61e4c99a41 Mon Sep 17 00:00:00 2001
From: Gerard Beekmans <gerard@linuxfromscratch.org>
Date: Sat, 14 Apr 2001 22:23:28 +0000
Subject: Don't run lilo inside chroot anymore

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@510 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
---
 chapter08/lilo.xml | 67 +++++++++++++++++++++++++++++++++++++++++++++---------
 1 file changed, 56 insertions(+), 11 deletions(-)

(limited to 'chapter08/lilo.xml')

diff --git a/chapter08/lilo.xml b/chapter08/lilo.xml
index c998387b2..3c1d29157 100644
--- a/chapter08/lilo.xml
+++ b/chapter08/lilo.xml
@@ -1,25 +1,49 @@
 <sect1 id="ch08-lilo">
-<title>Adding an entry to LILO</title>
+<title>Making the LFS system bootable</title>
 
 <para>
-In order to being able to boot from this partition, we need to update our
-/etc/lilo.conf file. The following lines get added to lilo.conf by running:
+In order to being able to boot the LFS system, we need to update our
+bootloader. We're assuming that your host system is using Lilo (since
+that's the most commonly used boot loader at the moment).
+</para>
+
+<para>
+We will not be running the lilo program inside chroot. Running lilo
+inside chroot can have fatal side-effects which render your MBR useles
+and you'd need a boot disk to be able to start any Linux system (either
+the host system or the LFS system).
+</para>
+
+<para>
+First we'll exit chroot and copy the lfskernel file to the host system:
+</para>
+
+<blockquote><literallayout>
+
+	<userinput>logout &amp;&amp;</userinput>
+	<userinput>cp $LFS/boot/lfskernel /boot
+		&amp;&amp;</userinput>
+
+</literallayout></blockquote>
+
+<para>
+The next step is adding an entry to /etc/lilo.conf so that we can
+choose LFS when booting the computer:
 </para>
 
 <literallayout>
 
-<userinput>cat &gt;&gt; /etc/lilo.conf &lt;&lt; "EOF"</userinput>
-image=/boot/lfskernel
-        label=lfs
-        root=&lt;partition&gt;
-        read-only
-<userinput>EOF</userinput>
+	<userinput>cat &gt;&gt; /etc/lilo.conf &lt;&lt; "EOF"</userinput>
+		image=/boot/lfskernel
+		label=lfs
+		root=&lt;partition&gt;
+		read-only
+	<userinput>EOF</userinput>
 
 </literallayout>
 
 <para>
-&lt;partition&gt; must be replaced by the partition's designation (which
-would be /dev/hda5 in my case).
+&lt;partition&gt; must be replaced by the LFS partition's designation.
 </para>
 
 <para>
@@ -32,5 +56,26 @@ Now the boot loader gets updated by running:
 
 </literallayout></blockquote>
 
+<para>
+The last step is syncing the host system lilo config. files with the
+LFS system:
+</para>
+
+<blockquote><literallayout>
+
+	<userinput>cp /etc/lilo.conf $LFS/etc &amp;&amp;</userinput>
+	<userinput>cp &lt;kernel images&gt; $LFS/boot</userinput>
+
+</literallayout></blockquote>
+
+<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 in
+other places than the /boot directory, make sure you update the paths
+in the $LFS/etc/lilo.conf file so that it does look for them in the
+/boot directory.
+</para>
+
 </sect1>
 
-- 
cgit v1.2.3-54-g00ecf