Clarify verbiage in chapter 2.6 (Setting the $LFS Variable).

This commit is contained in:
David Bryant 2022-09-23 14:08:34 -05:00
parent 10d7c7a820
commit 50e70dbc1f

View File

@ -14,8 +14,8 @@
be used several times. You should ensure that this variable is always defined
throughout the LFS build process. It should be set to the name of the
directory where you will be building your LFS system - we will use
<filename class="directory">/mnt/lfs</filename> as an example, but the
directory choice is up to you. If you are building LFS on a separate
<filename class="directory">/mnt/lfs</filename> as an example, but you may
choose any directory name you want. If you are building LFS on a separate
partition, this directory will be the mount point for the partition.
Choose a directory location and set the variable with the
following command:</para>
@ -25,7 +25,7 @@
<para>Having this variable set is beneficial in that commands such as
<command>mkdir -v $LFS/tools</command> can be typed literally. The shell
will automatically replace <quote>$LFS</quote> with
<quote>/mnt/lfs</quote> (or whatever the variable was set to) when it
<quote>/mnt/lfs</quote> (or whatever value the variable was set to) when it
processes the command line.</para>
<caution>
@ -49,7 +49,7 @@
personal home directory and in <filename>/root/.bash_profile</filename> and
enter the export command above. In addition, the shell specified in the
<filename>/etc/passwd</filename> file for all users that need the
<envar>LFS</envar> variable needs to be bash to ensure that the
<envar>LFS</envar> variable must be bash to ensure that the
<filename>/root/.bash_profile</filename> file is incorporated as a part of
the login process.</para>
@ -59,9 +59,9 @@
a virtual terminal is started. In this case, add the export command to
the <filename>.bashrc</filename> file for the user and
<systemitem class="username">root</systemitem>. In addition,
some distributions have instructions to not run the <filename>.bashrc</filename>
instructions in a non-interactive bash invocation. Be sure to add the
export command before the test for non-interactive use.</para>
some distributions use an "if" test, and do not run the remaining <filename>.bashrc</filename>
instructions for a non-interactive bash invocation. Be sure to place the
export command ahead of the test for non-interactive use.</para>
</note>