gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-06-19 11:49:20 +01:00
Code Issues Packages Projects Releases Wiki Activity

Rewording the section.

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2718 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Alex Gronenwoud 2003-09-02 21:59:18 +00:00
parent a9939e0df5
commit 7fcbee1c5f
1 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
chapter02/aboutlfs.xml
View File

@ -2,16 +2,16 @@
<title>About $LFS</title> <title>About $LFS</title>
<?dbhtml filename="aboutlfs.html" dir="chapter02"?> <?dbhtml filename="aboutlfs.html" dir="chapter02"?>
<para>Please read the following carefully: throughout this book <para>Please read the following paragraphs carefully. Throughout this book the
the variable LFS will be used frequently. $LFS must at all times be variable LFS will be used frequently. $LFS must at all times be replaced with
replaced with the directory where the partition that contains the LFS system the directory where the partition that contains the LFS system is mounted. How
is mounted. How to create and where to mount the partition will be to create and where to mount the partition will be explained in full detail in
explained in full detail in Chapter 4. For example, let's assume that Chapter 4. For the moment let's assume that the LFS partition is mounted on
the LFS partition is mounted on /mnt/lfs.</para> <filename>/mnt/lfs</filename>.</para>
<para>When you are told to run a command like <para>When you are told to run a command like
<userinput>./configure --prefix=$LFS/static</userinput> you actually have to <userinput>./configure --prefix=$LFS/tools</userinput>, you actually have to
execute <userinput>./configure --prefix=/mnt/lfs/static</userinput>.</para> execute <userinput>./configure --prefix=/mnt/lfs/tools</userinput>.</para>
<para>It's important that this is done no matter where it is read; be it in <para>It's important that this is done no matter where it is read; be it in
commands entered in a shell, or in a file edited or created.</para> commands entered in a shell, or in a file edited or created.</para>
@ -23,9 +23,9 @@ This way $LFS can be entered literally instead of replacing it with
<para><screen><userinput>export LFS=/mnt/lfs</userinput></screen></para> <para><screen><userinput>export LFS=/mnt/lfs</userinput></screen></para>
<para>Now, if you are told to run a command such as <para>Now, if you are told to run a command such as
<userinput>./configure --prefix=$LFS/static</userinput>, then you may type <userinput>./configure --prefix=$LFS/tools</userinput>, then you may type it
it literally. Your shell will replace $LFS with /mnt/lfs when it processes literally. Your shell will replace "$LFS" with "/mnt/lfs" when it processes
the command line (meaning when you hit enter after having typed the the command line (that is, when you hit Enter after having typed the
command).</para> command).</para>
</sect1> </sect1>