r2821 - jhalfs/trunk

manuel at linuxfromscratch.org manuel at linuxfromscratch.org
Thu Jul 13 13:25:46 PDT 2006


Author: manuel
Date: 2006-07-13 14:25:46 -0600 (Thu, 13 Jul 2006)
New Revision: 2821

Modified:
   jhalfs/trunk/README
Log:
Typo fix and trailing spaces clean-up.

Modified: jhalfs/trunk/README
===================================================================
--- jhalfs/trunk/README	2006-07-13 20:25:17 UTC (rev 2820)
+++ jhalfs/trunk/README	2006-07-13 20:25:46 UTC (rev 2821)
@@ -37,10 +37,10 @@
      IMPORTANT:
        If you use the switch -M (automatically run the generated makefile) you
        must be 'root' or you can run the scripts using 'sudo'
-        i.e.  sudo ./lfs -G -M 
-	
+        i.e.  sudo ./lfs -G -M
+
        If you want to run make manually you can only do so if you are 'root' or
-       via 'sudo' 
+       via 'sudo'
         i.e  (from within the jhalfs directory) sudo make
 
      The term <symlink> refers to the 1 of 3 package symlinks, lfs,hlfs,clfs.
@@ -60,41 +60,41 @@
      will give you a context sensitive list of command line switches.
 
    >>>> an expanded example
-   
+
    export SRC_ARCHIVE=/mnt/SourceFiles
-   
+
    ./lfs -D /mnt/partition4 \
          -K ~/jhalfs_configs/linux-2.6.16.19-LFS.config \
 	 -F ~/jhalfs-configs/fstab-sda3 \
-	 -G -T 0 -M  
+	 -G -T 0 -M
 
    explanation:::
-   
+
    export SRC_ARCHIVE=/mnt/SourceFiles
-      # This points to a local archive of existing packages. If the version in 
-        the archive is incorrect jhalfs will access the net and download the 
+      # This points to a local archive of existing packages. If the version in
+        the archive is incorrect jhalfs will access the net and download the
 	necessary version and store it here for later use. DO NOT set this to
 	$BUILDDIR/sources. If you do not set this variable to a valide directory
-	ALL package tarballs will be downloaded from the 'net. 
+	ALL package tarballs will be downloaded from the 'net.
 
-   -D /mnt/partition4 
+   -D /mnt/partition4
       # where everything takes place.  ..NOTE it must already exist and be mounted
-      
+
    -K ~/jhalfs_configs/linux-2.6.16.19-LFS.config
-      # If you want to automatically build a the kernel you MUST supply a valid 
+      # If you want to automatically build a the kernel you MUST supply a valid
         kernel configuration file. The file you supply will be copied and renamed.
 
-   -F ~/jhalfs-configs/fstab-sda3 
-      # If you have a fstab file you wish to use it will be copied and renamed 
-      
-   -G   # Retrieve the package files. You MUST enable this flag at least once if you 
+   -F ~/jhalfs-configs/fstab-sda3
+      # If you have a fstab file you wish to use it will be copied and renamed
+
+   -G   # Retrieve the package files. You MUST enable this flag at least once if you
           wish to do a build or whenever you update the book.
-   
+
    -T 0 # don't run any testsuites
-   
+
    -M   # automatically run make against Makefile once jhalfs finishes its work.
 
-   
+
 5. LAYOUT::
 
         /CLFS/config
@@ -135,12 +135,12 @@
 6. FAQ::
     Q. "It doesn't work!"
     A. Yes it does, try ./lfs --help
-    
+
     Q. "It still doesn't work"
     A. jhalfs was designed to work against the developement versions of the LFS
        series of books. Consequently changes in a book(s) sometimes breaks older
        versions of jhalfs. Before you start pulling out your hair download the
-       latest version of jhalfs is see it that solves your problem.
+       latest version of jhalfs to see if that solves your problem.
 
     Q. "How do I specify the build location?"
     A. The original LFS document worked against the well know location /mnt/lfs.
@@ -183,18 +183,18 @@
        not compatible with the host.  If you choose to build using the chroot
        method a test is performed at the end of the temptools phase. If the test
        succeeds the build continues inside a chroot jail. However if the test fails
-       it means the host and target are not compatible an you should use the 
-       'boot' method to create your target code.        
-       As an extreme example: You can build a sparc target on a x86 platform but 
+       it means the host and target are not compatible an you should use the
+       'boot' method to create your target code.
+       As an extreme example: You can build a sparc target on a x86 platform but
        only the temptools phase. You must run ./clfs using the 'boot' method and
-       not the 'chroot.' You must transfer the toolchain to a sparc platform, reboot 
+       not the 'chroot.' You must transfer the toolchain to a sparc platform, reboot
        the sparc box and continue the build.
-       Of all the LFS series of books the Cross-LFS requires the greatest 
+       Of all the LFS series of books the Cross-LFS requires the greatest
        understanding of host/target hardware combination. Please read the book
        carefully and don't skip the easy parts (there are none..)
-       
 
 
+
 Authors:
   George Boudreau
   Manuel Canales Esparcia




More information about the alfs-log mailing list