Ignore:
Timestamp:
11/16/2022 11:30:12 PM (20 months ago)
Author:
Thomas Trepl (Moody) <thomas@…>
Branches:
multilib
Children:
8d5322e
Parents:
a03b7d95 (diff), ebecd08 (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

  • chapter07/cleanup.xml

    ra03b7d95 r16a1647  
    1414    <title>Cleaning</title>
    1515
    16     <para>First, remove the currently installed documentation to prevent them
     16    <para>First, remove the currently installed documentation files to prevent them
    1717    from ending up in the final system, and to save about 35 MB:</para>
    1818
    … …  
    2020
    2121    <para>Second, on a modern Linux system, the libtool .la files are only
    22     useful for libltdl.  No libraries in LFS are expected to be loaded by
    23     libltdl, and it's known that some .la files can cause BLFS packages
    24     fail to build.  Remove those files now:</para>
     22    useful for libltdl.  No libraries in LFS are loaded by
     23    libltdl, and it's known that some .la files can cause BLFS package
     24    failures.  Remove those files now:</para>
    2525
    2626<screen><userinput>find /usr/{lib,libexec} -name \*.la -delete</userinput><userinput arch="ml_32">
    … …  
    4646      backed up for later reuse. In case of fatal failures in the subsequent
    4747      chapters, it often turns out that removing everything and starting over
    48       (more carefully) is the best option to recover. Unfortunately, all the
     48      (more carefully) is the best way to recover. Unfortunately, all the
    4949      temporary files will be removed, too. To avoid spending extra time to
    50       redo something which has been built successfully, creating a backup of
     50      redo something which has been done successfully, creating a backup of
    5151      the current LFS system may prove useful.
    5252    </para>
    … …  
    6262    <para>
    6363      The following steps are performed from outside the chroot
    64       environment. That means, you have to leave the chroot environment
     64      environment. That means you have to leave the chroot environment
    6565      first before continuing. The reason for that is to
    6666      get access to file system locations outside of the chroot
    67       environment to store/read the backup archive which should
     67      environment to store/read the backup archive, which ought
    6868      not be placed within the
    69       <filename class="directory">$LFS</filename> hierarchy for
    70       safety reasons.
     69      <filename class="directory">$LFS</filename> hierarchy.
    7170    </para>
    7271
    … …  
    8281        <systemitem class="username">root</systemitem> on your host system.
    8382        Take extra care about the commands you're going to run as mistakes
    84         here can modify your host system. Be aware that the
     83        made here can modify your host system. Be aware that the
    8584        environment variable <envar>LFS</envar>
    8685        is set for user <systemitem class="username">lfs</systemitem> by default
    … …  
    105104    <para>
    106105      Make sure you have at least 1 GB free disk space (the source tarballs
    107       will be included in the backup archive) on the filesystem containing
    108       directory where you create the backup archive.
     106      will be included in the backup archive) on the file system containing
     107      the directory where you create the backup archive.
    109108    </para>
    110109
    … …  
    112111      Note that the instructions below specify the home directory of the host
    113112      system's <systemitem class="username">root</systemitem> user, which is
    114       typically found on the root filesystem.
    115     </para>
    116 
    117     <para>
     113      typically found on the root file system.
    118114      Replace <envar>$HOME</envar> by a directory of your choice if you
    119115      do not want to have the backup stored in <systemitem
    … …  
    153149      <filename class="directory">$LFS</filename>, they are included in the
    154150      backup archive as well, so they do not need to be downloaded again. After
    155       checking that <envar>$LFS</envar> is set properly,
     151      checking that <envar>$LFS</envar> is set properly, you can
    156152      restore the backup by executing the following commands:
    157153    </para>
    … …  
    171167
    172168    <para>
    173        Again, double check that the environment has been setup properly
     169       Again, double check that the environment has been set up properly
    174170       and continue building the rest of the system.
    175171    </para>
    … …  
    179175         If you left the chroot environment to create a backup or restart
    180176         building using a restore, remember to check that the virtual
    181          filesystems are still mounted (<command>findmnt | grep
     177         file systems are still mounted (<command>findmnt | grep
    182178         $LFS</command>).  If they are not mounted, remount them now as
    183179         described in <xref linkend='ch-tools-kernfs'/> and re-enter the chroot
Note: See TracChangeset for help on using the changeset viewer.