r2691 - jhalfs/trunk

jhuntwork at linuxfromscratch.org jhuntwork at linuxfromscratch.org
Sat May 13 20:41:27 PDT 2006

Author: jhuntwork
Date: 2006-05-13 21:41:26 -0600 (Sat, 13 May 2006)
New Revision: 2691

Minor text corrections in the README

Modified: jhalfs/trunk/README
--- jhalfs/trunk/README	2006-05-13 17:16:53 UTC (rev 2690)
+++ jhalfs/trunk/README	2006-05-14 03:41:26 UTC (rev 2691)
@@ -16,7 +16,7 @@
   Lay in a supply of caffeine beverages.
   *.  It is recommended that you temporarily unpack your linux kernel,
-  run <make menuconfig>, configure the kernal as per the book and save
+  run <make menuconfig>, configure the kernel as per the book and save
   the resulting .config file. This suggestion also applies to the
   configuration of the uClibc package when building a HLFS system using
   uClibc rather than glibc.
@@ -94,10 +94,10 @@
 6. FAQ::
-    Q. "It doesn't work"
+    Q. "It doesn't work!"
     A. Yes it does, try ./lfs --help
-    Q. "How do I specify the build location"
+    Q. "How do I specify the build location?"
     A. The original LFS document worked against the well know location /mnt/lfs.
        This script automates the build of all of the LFS series of books and uses
        a generic location $BUILDDIR with a default value a /mnt/build_dir.
@@ -113,7 +113,7 @@
 	    FHS dir structure
-    Q. "What is the function of the SRC_ARCHIVE variable
+    Q. "What is the function of the SRC_ARCHIVE variable?"
     A. When then symlinked master.sh runs it creates a local copy of the
        necessary packages in BUILDDIR/sources by downloading the files. If
        the variable SRC_ARCHIVE is defined the software will first look in
@@ -121,13 +121,13 @@
        If the files are not found in SRC_ARCHIVE _and_ you have write priv to
        the directory any downloaded files will be mirrored there.
-    Q. "How do I set the SRC_ARCHIVE location"
+    Q. "How do I set the SRC_ARCHIVE location?"
     A. The best way to set the value of SRC_ARCHIVE is
        export SRC_ARCHIVE=/wherever/you/store/downloaded/packages
        you can change the setting in .common/config. 
-    Q. "Why have 2 copies of the files."
+    Q. "Why have 2 copies of the files?"
     A. The package files must be visible during the chroot phase and this is a
        simple and reliable method of doing so. This method also handles the CLFS
        build method where the final build may be done on a separate machine.

More information about the alfs-log mailing list