Consistency in addressing variables (About $LFS)

elko elko at home.nl
Fri Sep 27 05:57:26 PDT 2002


Hello,

I was reading the section 'About $LFS' and noticed that sometimes
the book talks about 'the $LFS variable' and other times the phrase
'the LFS variable' is used.

The bash man-page is consistent in using the last form 'THIS variable'
instead of '$THIS variable' and 'the variable THAT' instead of using
'the variable $THAT', so I thought it might be a good idea if the
LFS-book also uses the same consistency.

These are the ones that I found:


Index: chapter01/changelog.xml
===================================================================
RCS file: /home/cvsroot/LFS/BOOK/chapter01/changelog.xml,v
retrieving revision 1.382
diff -u -r1.382 changelog.xml
--- chapter01/changelog.xml	24 Sep 2002 04:52:43 -0000	1.382
+++ chapter01/changelog.xml	27 Sep 2002 12:28:35 -0000
@@ -396,7 +396,7 @@
 instead.</para></listitem>
 
 <listitem><para>May 25th, 2002 [markh]: Chapter 06 - Some minor
-corrections dealing with removing the $LFS variable where it isn't
+corrections dealing with removing the LFS variable where it isn't
 wanted.</para></listitem>
 
 <listitem><para>May 23rd, 2002 [gerard]: Implemented the
Index: chapter02/aboutlfs.xml
===================================================================
RCS file: /home/cvsroot/LFS/BOOK/chapter02/aboutlfs.xml,v
retrieving revision 1.17
diff -u -r1.17 aboutlfs.xml
--- chapter02/aboutlfs.xml	22 Sep 2002 03:13:20 -0000	1.17
+++ chapter02/aboutlfs.xml	27 Sep 2002 12:28:35 -0000
@@ -3,7 +3,7 @@
 <?dbhtml filename="aboutlfs.html" dir="chapter02"?>
 
 <para>Please read the following carefully: throughout this book 
-the variable $LFS will be used frequently. $LFS must at all times be
+the variable LFS will be used frequently. $LFS must at all times be
 replaced with the directory where the partition that contains the LFS system 
 is mounted. How to create and where to mount the partition will be
 explained in full detail in Chapter 4. For example, let's assume that 
@@ -28,18 +28,18 @@
 the command line (meaning when you hit enter after having typed the
 command).</para>
 
-<para>If you plan to use $LFS, do not forget to set the $LFS variable at all 
+<para>If you plan to use $LFS, do not forget to set the LFS variable at all 
 times. If the variable is not set and is used in a command, $LFS will 
 be ignored and whatever is left will be executed. A command like
 <userinput>echo "root:x:0:0:root:/root:/bin/bash" > 
-$LFS/etc/passwd</userinput> without the $LFS variable set will
+$LFS/etc/passwd</userinput> without the LFS variable set will
 re-create your host system's /etc/passwd file. Simply put: it will
 destroy your current password database file.</para>
 
-<para>One way to make sure that $LFS is set at all times is adding it to
+<para>One way to make sure that LFS is set at all times is adding it to
 the /root/.bash_profile and /root/.bashrc files so that every time
 you login as user root, or you <userinput>su</userinput> to user root,
-the $LFS variable is set.</para>
+the LFS variable is set.</para>
 
 </sect1>
 
Index: chapter04/mounting.xml
===================================================================
RCS file: /home/cvsroot/LFS/BOOK/chapter04/mounting.xml,v
retrieving revision 1.15
diff -u -r1.15 mounting.xml
--- chapter04/mounting.xml	20 Sep 2002 21:11:27 -0000	1.15
+++ chapter04/mounting.xml	27 Sep 2002 12:28:36 -0000
@@ -19,8 +19,8 @@
 
 <para>Replace <quote>xxx</quote> by the partition's designation (like hda11).</para>
 
-<para>This directory (/mnt/lfs) is the $LFS variable you have read about 
-back in Chapter 2. If you were planning to make use of the $LFS environment 
+<para>This directory (/mnt/lfs) is the LFS variable you have read about 
+back in Chapter 2. If you were planning to make use of the LFS environment 
 variable, <userinput>export LFS=/mnt/lfs</userinput> has to be executed 
 now.</para>
 
Index: chapter05/installasuser.xml
===================================================================
RCS file: /home/cvsroot/LFS/BOOK/chapter05/installasuser.xml,v
retrieving revision 1.15
diff -u -r1.15 installasuser.xml
--- chapter05/installasuser.xml	23 Sep 2002 18:35:06 -0000	1.15
+++ chapter05/installasuser.xml	27 Sep 2002 12:28:36 -0000
@@ -5,7 +5,7 @@
 <para>When you are logged in as root during Chapter 5, it is possible
 that some files of your host system will be overwritten by the ones
 you'll build in Chapter 5. There can be all kinds of reasons for this
-to happen, for example because the $LFS environment variable is not
+to happen, for example because the LFS environment variable is not
 set. Overwriting some files from your host system will most likely
 cause all kinds of problems, so it's a good idea to be logged in as
 an unprivileged user during Chapter 5. To make sure the environment
@@ -39,19 +39,19 @@
 
 <para>This profile makes sure the umask is set to 022 so newly created
 files and directories will have the correct permissions. It is advisable
-to keep this setting throughout your LFS installation. Also, the $LFS,
-$LC_ALL, and $CC environment variables are set. $LFS has been explained
-in previous chapters already. $LC_ALL is a variable that is used for
+to keep this setting throughout your LFS installation. Also, the LFS,
+LC_ALL, and CC environment variables are set. $LFS has been explained
+in previous chapters already. LC_ALL is a variable that is used for
 internationalization.</para>
 
 <para>When your host distribution uses a glibc version older than 2.2.4,
-having $LC_ALL set to something other than "C" or "POSIX" while working
+having LC_ALL set to something other than "C" or "POSIX" while working
 through Chapter 5 may cause trouble when you exit the chroot environment
 of Chapter 6 and try to return to it. By setting this to "POSIX" ("C"
 is an alias for "POSIX") we ensure that everything will work as expected
 in the chroot environment.</para>
 
-<para>$CC is a variable we set in order to prevent debugging symbols from
+<para>CC is a variable we set in order to prevent debugging symbols from
 being compiled into our static packages. By omitting these symbols during
 the linking stage of compilation, we save hard drive space and decrease
 our build time.</para>
Index: chapter06/chroot.xml
===================================================================
RCS file: /home/cvsroot/LFS/BOOK/chapter06/chroot.xml,v
retrieving revision 1.27
diff -u -r1.27 chroot.xml
--- chapter06/chroot.xml	8 Sep 2002 21:54:14 -0000	1.27
+++ chapter06/chroot.xml	27 Sep 2002 12:28:36 -0000
@@ -24,7 +24,7 @@
 like vim and less to operate properly. If you need other variables present,
 such as CFLAGS or CXXFLAGS, this is a good place to set them again.</para>
 
-<para>From this point on there's no need anymore to use the $LFS variable,
+<para>From this point on there's no need anymore to use the LFS variable,
 because everything you do will be restricted to the LFS file system -- since
 what the shell thinks is <filename class="directory">/</filename> is actually
 <filename class="directory">/mnt/lfs</filename>.</para>

-- 
	Elko

-- 
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe lfs-dev' in the subject header of the message



More information about the lfs-dev mailing list