From 4c5274d6b8e52ae76ff5bcd0cc2f6a0f25856fcf Mon Sep 17 00:00:00 2001 From: George Boudreau Date: Sun, 13 Aug 2006 20:57:30 +0000 Subject: [PATCH] README.BLFS: a few spelling mistakes and touch up some grammar --- README.BLFS | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/README.BLFS b/README.BLFS index 7e8ba54..88a192e 100644 --- a/README.BLFS +++ b/README.BLFS @@ -14,7 +14,7 @@ $Id$ general rule you will need to review and edit the scripts while reading the book. - NOTE:: The code is yet under development a may contains several bugs + NOTE:: The code is still under development and may contains several bugs 2. USAGE:: @@ -54,13 +54,14 @@ $Id$ 2.3 PARSING THE BOOK:: Next step is to create a book and build scripts in dependencies build order for a target package. A target package can be any of the ones listed in the - packages file. That is done using the blfs-parser.sh script, but we are triying + packages file. That is done using the blfs-parser.sh script, but we are trying to make a menuconfig based system. The script need three arguments: package name as listed in packages file - dependencies level 1 for required, 2 for required an recommendedand, + dependencies level 1 for required, + 2 for required an recommendedand, 3 for required, recommended, and optional sudo usage y if sudo will be used (you will build as normal user) n if sudo isn't needed (you will build as root) @@ -82,8 +83,8 @@ $Id$ packages (i.e., for non-BLFS packages) can be inserted in an easy way. 2.4 CREATING THE MAKEFILE - When the build scripts will be ready to be run, the Makefile can be - created. Be sure that you are into the "package" directory and run + When the build scripts are ready to be run, the Makefile can be + created. Be sure that you cd into the "package" directory and run ../gen_makefile.sh