Initial commit - LFS 2.4.4 files

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@14 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

1 files changed, 46 insertions, 0 deletions

diff --git a/chapter06/config-lilo.sgml b/chapter06/config-lilo.sgml
new file mode 100644
index 000000000..1e61cc9f1
--- /dev/null
+++ b/chapter06/config-lilo.sgml
@@ -0,0 +1,46 @@
+<sect2>
+<title>Configuring Lilo</title>
+
+<para>
+We're not going to create lilo's configuration file from scratch, but we'll
+use the file from your normal Linux system. This file is different on every
+machine and thus I can't create it here. Since you would want to have the
+same options regarding lilo as you have when you're using your normal Linux
+system you would create the file exactly as it is on the normal system.
+</para>
+
+<para>
+Copy the Lilo configuration file and kernel images that Lilo uses by
+running the following commands from a shell on your normal Linux system.
+Don't execute these commands from your chroot'ed shell.
+</para>
+
+<blockquote><literallayout>
+
+	<userinput>cp /etc/lilo.conf $LFS/etc</userinput>
+	<userinput>cp /boot/&lt;kernel images&gt; $LFS/boot</userinput>
+
+</literallayout></blockquote>
+
+<para>
+Before you can execute the second command you need to know the names of
+the kernel images. You can't just copy all files from the /boot
+directory. The /etc/lilo.conf file contains the names of the kernel
+images you're using. Open the file and look for lines like this:
+</para>
+
+<blockquote><literallayout>
+
+	image=/boot/vmlinuz
+
+</literallayout></blockquote>
+
+<para>
+Look for all <emphasis>image</emphasis> variables and their values
+represent the name and location of the image files. These files will
+usually be in /boot but they might be in other directories as well,
+depending on your distribution's conventions.
+</para>
+
+</sect2>
+