From 81a47c0302abb616dc4b897ae71e9b0736405a24 Mon Sep 17 00:00:00 2001 From: Thomas Balu Walter Date: Mon, 19 Mar 2001 16:02:50 +0000 Subject: You git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@337 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter06/config-lilo.xml | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) (limited to 'chapter06/config-lilo.xml') diff --git a/chapter06/config-lilo.xml b/chapter06/config-lilo.xml index 1e61cc9f1..c5ceece9c 100644 --- a/chapter06/config-lilo.xml +++ b/chapter06/config-lilo.xml @@ -3,16 +3,16 @@ 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. +use the file from the normal Linux system. This file is different on every +machine and thus I can't create it here. Since a user would want to have the +same options regarding lilo as he has when he is using his normal Linux +system he would create the file exactly as it is on the normal system. 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. +running the following commands from a shell on the normal Linux system. +Don't execute these commands from the chroot'ed shell.
@@ -23,10 +23,10 @@ Don't execute these commands from your chroot'ed shell.
-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 +Before a user can execute the second command he needs to know the names of +the kernel images. He 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: +images he is using. Open the file and look for lines like this:
@@ -39,7 +39,7 @@ images you're using. Open the file and look for lines like this: Look for all image 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. +depending on the distribution's conventions. -- cgit v1.2.3-54-g00ecf