Changeset 9cb6b64 for final-preps

Timestamp:

Jul 1, 2006, 12:48:39 PM (18 years ago)

Author:

Jim Gifford <clfs@…>

Children:

8018c66

Parents:

2ce8e8a

Message:

r4209@server: jim | 2006-07-01 12:46:18 -0700
Updated variables -

LFS_TARGET is now CLFS_TARGET
LFS_HOST is now CLFS_HOST
LFS_TARGET32 is now CLFS_TARGET32
LFS is now CLFS
/mnt/lfs is now /mnt/clfs

Location:

final-preps

Files:

• aboutlfs.xml (modified) (3 diffs)
• addinguser.xml (modified) (1 diff)
• creatingcrossdir.xml (modified) (3 diffs)
• creatingtoolsdir.xml (modified) (3 diffs)
• settingenviron.xml (modified) (1 diff)

final-preps/aboutlfs.xml

@@ -9 +9 @@
   <?dbhtml filename="aboutlfs.html"?>
 
-  <title>About $LFS</title>
+  <title>About $CLFS</title>
 
   <para>Throughout this book, the environment variable <envar>LFS</envar> will
@@ -16 +16 @@
   Check that the <envar>LFS</envar> variable is set up properly with:</para>
 
-<screen><userinput>echo $LFS</userinput></screen>
+<screen><userinput>echo $CLFS</userinput></screen>
 
   <para>Make sure the output shows the path to the CLFS partition's mount
@@ -26 +26 @@
 
   <para>Having this variable set is beneficial in that commands such as
-  <command>install -dv $LFS/tools</command> can be typed literally. The shell
-  will automatically replace <quote>$LFS</quote> with
+  <command>install -dv $CLFS/tools</command> can be typed literally. The shell
+  will automatically replace <quote>$CLFS</quote> with
   <quote>/mnt/lfs</quote> (or whatever the variable was set to) when it
   processes the command line.</para>
 
-  <para>If you haven't created the <filename class="directory">$LFS</filename>
+  <para>If you haven't created the <filename class="directory">$CLFS</filename>
   directory, do so at this time by issuing the following commands:</para>
 
-<screen><userinput>install -dv $LFS</userinput></screen>
+<screen><userinput>install -dv $CLFS</userinput></screen>
 
-  <para>Do not forget to check that <envar>$LFS</envar> is set whenever
+  <para>Do not forget to check that <envar>$CLFS</envar> is set whenever
   you leave and reenter the current working environment (as when doing a
   <quote>su</quote> to <systemitem class="username">root</systemitem> or

final-preps/addinguser.xml

@@ -79 +79 @@
 
   <para>Grant <systemitem class="username">lfs</systemitem> full access to
-  <filename class="directory">$LFS/cross-tools</filename> and
-  <filename class="directory">$LFS/tools</filename> by making <systemitem
+  <filename class="directory">$CLFS/cross-tools</filename> and
+  <filename class="directory">$CLFS/tools</filename> by making <systemitem
   class="username">lfs</systemitem> the directorys' owner:</para>
 
-<screen><userinput>chown -v lfs $LFS/tools
-chown -v lfs $LFS/cross-tools</userinput></screen>
+<screen><userinput>chown -v lfs $CLFS/tools
+chown -v lfs $CLFS/cross-tools</userinput></screen>
 
   <para>If a separate working directory was created as suggested, 
   give user <systemitem class="username">lfs</systemitem> ownership of this directory:</para>
 
-<screen><userinput>chown -v lfs $LFS/sources</userinput></screen>
+<screen><userinput>chown -v lfs $CLFS/sources</userinput></screen>
 
   <para>Next, login as user <systemitem class="username">lfs</systemitem>.

final-preps/creatingcrossdir.xml

@@ -9 +9 @@
   <?dbhtml filename="creatingcrossdir.html"?>
 
-  <title>Creating the $LFS/cross-tools Directory</title>
+  <title>Creating the $CLFS/cross-tools Directory</title>
 
   <para>The cross-binutils and cross-compiler built in
   <xref linkend="chapter-cross-tools"/> will be installed under
-  <filename class="directory">$LFS/cross-tools</filename> to keep them
+  <filename class="directory">$CLFS/cross-tools</filename> to keep them
   separate from the host programs. The programs compiled here are
   cross-tools and will not be a part of the final CLFS system or the
@@ -22 +22 @@
   <systemitem class="username">root</systemitem>:</para>
 
-<screen><userinput>install -dv $LFS/cross-tools</userinput></screen>
+<screen><userinput>install -dv $CLFS/cross-tools</userinput></screen>
 
   <para>The next step is to create a <filename
@@ -29 +29 @@
   Run this command as  <systemitem class="username">root</systemitem> as well:</para>
 
-<screen><userinput>ln -sv $LFS/cross-tools /</userinput></screen>
+<screen><userinput>ln -sv $CLFS/cross-tools /</userinput></screen>
 
   <para>The symlink isn't technically necessary (though the book's
   instructions do assume its existence), but is there mainly for
-  consistency (because /tools is also symlinked to $LFS/tools) and to
+  consistency (because /tools is also symlinked to $CLFS/tools) and to
   simplify the installation of the cross-compile tools.</para>
 

final-preps/creatingtoolsdir.xml

@@ -9 +9 @@
   <?dbhtml filename="creatingtoolsdir.html"?>
 
-  <title>Creating the $LFS/tools Directory</title>
+  <title>Creating the $CLFS/tools Directory</title>
 
   <para>All programs compiled in <xref linkend="chapter-temp-system"/>
-  will be installed under <filename class="directory">$LFS/tools</filename>
+  will be installed under <filename class="directory">$CLFS/tools</filename>
   to keep them separate from the programs compiled in <xref
   linkend="chapter-building-system"/>. The programs compiled here are
@@ -24 +24 @@
   <systemitem class="username">root</systemitem>:</para>
 
-<screen><userinput>install -dv $LFS/tools</userinput></screen>
+<screen><userinput>install -dv $CLFS/tools</userinput></screen>
 
   <para>The next step is to create a <filename class="symlink">/tools</filename>
@@ -31 +31 @@
   class="username">root</systemitem> as well:</para>
 
-<screen><userinput>ln -sv $LFS/tools /</userinput></screen>
+<screen><userinput>ln -sv $CLFS/tools /</userinput></screen>
 
   <note>

final-preps/settingenviron.xml

@@ -56 +56 @@
   the shell will always search the <envar>PATH</envar> when a program is to
   be run. As such, the shell will find the newly compiled tools in
-  <filename class="directory">$LFS/cross-tools</filename> as soon as they are
+  <filename class="directory">$CLFS/cross-tools</filename> as soon as they are
   available without remembering a previous version of the same program in a
   different location.</para>