Ignore:
Timestamp:
10/01/2022 10:30:12 PM (19 months ago)
Author:
Thomas Trepl (Moody) <thomas@…>
Branches:
multilib
Children:
f3b2f16
Parents:
f29824e (diff), 4349661 (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the (diff) links above to see all the changes relative to each parent.
Message:

Automatic merge of trunk into multilib

File:
1 edited

Legend:

Unmodified
Added
Removed
  • chapter02/aboutlfs.xml

    rf29824e rc093e6b  
    1515  throughout the LFS build process. It should be set to the name of the
    1616  directory where you will be building your LFS system - we will use
    17   <filename class="directory">/mnt/lfs</filename> as an example, but the
    18   directory choice is up to you. If you are building LFS on a separate
     17  <filename class="directory">/mnt/lfs</filename> as an example, but you may
     18  choose any directory name you want. If you are building LFS on a separate
    1919  partition, this directory will be the mount point for the partition.
    2020  Choose a directory location and set the variable with the
     
    2626  <command>mkdir -v $LFS/tools</command> can be typed literally. The shell
    2727  will automatically replace <quote>$LFS</quote> with
    28   <quote>/mnt/lfs</quote> (or whatever the variable was set to) when it
     28  <quote>/mnt/lfs</quote> (or whatever value the variable was set to) when it
    2929  processes the command line.</para>
    3030
     
    5050  enter the export command above.  In addition, the shell specified in the
    5151  <filename>/etc/passwd</filename> file for all users that need the
    52   <envar>LFS</envar> variable needs to be bash to ensure that the
     52  <envar>LFS</envar> variable must be bash to ensure that the
    5353  <filename>/root/.bash_profile</filename> file is incorporated as a part of
    5454  the login process.</para>
     
    6060  the <filename>.bashrc</filename> file for the user and
    6161  <systemitem class="username">root</systemitem>.  In addition,
    62   some distributions have instructions to not run the <filename>.bashrc</filename>
    63   instructions in a non-interactive bash invocation.  Be sure to add the
    64   export command before the test for non-interactive use.</para>
     62  some distributions use an "if" test, and do not run the remaining <filename>.bashrc</filename>
     63  instructions for a non-interactive bash invocation.  Be sure to place the
     64  export command ahead of the test for non-interactive use.</para>
    6565
    6666  </note>
Note: See TracChangeset for help on using the changeset viewer.