Changeset beb80e2


Ignore:
Timestamp:
09/06/2021 02:32:47 PM (2 years ago)
Author:
Bruce Dubbs <bdubbs@…>
Branches:
11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, arm, bdubbs/gcc13, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/parallelism, xry111/pip3, xry111/rust-wip-20221008
Children:
8e6babe
Parents:
6851fc8
Message:

Update text in Chapter 7 Backup/Restore sections
Patch by Kevin Buckley.
Also made minor clarification to umount commands.

Files:
2 edited

Legend:

Unmodified
Added
Removed

  • chapter01/changelog.xml

    r6851fc8 rbeb80e2  
    4545
    4646    <listitem>
     47      <para>2021-09-06</para>
     48      <itemizedlist>
     49        <listitem>
     50          <para>[bdubbs] - Text clarifications in the backup/restore section
     51          o fChapter 7. Thanks to Kevin Buckley for the patch.</para>
     52        </listitem>
     53      </itemizedlist>
     54    </listitem>
     55
     56    <listitem>
    4757      <para>2021-09-01</para>
    4858      <itemizedlist>

  • chapter07/cleanup.xml

    r6851fc8 rbeb80e2  
    2121    <para>Second, the libtool .la files are only useful when linking with static
    2222    libraries. They are unneeded and potentially harmful when using dynamic
    23     shared libraries, specially when using non-autotools build systems.
     23    shared libraries, especially when using non-autotools build systems.
    2424    While still in chroot, remove those files now:</para>
    2525
    … …  
    3737  <sect2>
    3838    <title>Backup</title>
     39
     40    <para>
     41      At this point the essential programs and libraries have been created
     42      and your current LFS system is in a good state. Your system can now be
     43      backed up for later reuse. In case of fatal failures in the subsequent
     44      chapters, it often turns out that removing everything and starting over
     45      (more carefully) is the best option to recover. Unfortunately, all the
     46      temporary files will be removed, too. To avoid spending extra time to
     47      redo something which has been built successfully, creating a backup of
     48      the current LFS system may prove useful.
     49    </para>
    3950
    4051    <note><para>
    … …  
    5768    </para>
    5869
     70    <para>
     71       If you have decided to make a backup, leave the chroot environment:
     72    </para>
     73
     74<screen role="nodump"><userinput>exit</userinput></screen>
     75
    5976    <important>
    60       <para>All of the following instructions are executed by
    61         <systemitem class="username">root</systemitem>. Take extra
    62         care about the commands you're going to run as mistakes
     77      <para>
     78        All of the following instructions are executed by
     79        <systemitem class="username">root</systemitem> on your host system.
     80        Take extra care about the commands you're going to run as mistakes
    6381        here can modify your host system. Be aware that the
    6482        environment variable <envar>LFS</envar>
    6583        is set for user <systemitem class="username">lfs</systemitem> by default
    6684        but may <emphasis>not</emphasis> be set for
    67         <systemitem class="username">root</systemitem>. Whenever
    68         commands are to be executed by <systemitem class="username">root</systemitem>,
     85        <systemitem class="username">root</systemitem>.
     86     </para>
     87     <para>
     88        Whenever commands are to be executed by <systemitem class="username">root</systemitem>,
    6989        make sure you have set <envar>LFS</envar>.
     90     </para>
     91     <para>
    7092        This has been discussed in <xref linkend='ch-partitioning-aboutlfs'/>.
    7193      </para>
    7294    </important>
    7395
    74     <para>
    75        Now, if you are making a backup, leave the chroot environment:
    76     </para>
     96    <para>Before making a backup, unmount the virtual file systems:</para>
    7797
    78 <screen role="nodump"><userinput>exit</userinput></screen>
     98<screen role="nodump"><userinput>umount $LFS/dev/pts
     99umount $LFS/{sys,proc,run,dev}</userinput></screen>
    79100
    80101    <para>
    81       At this point the essential programs and libraries have been created
    82       and your current system is in a good state. Your system can now be
    83       backed up for later reuse. In case of fatal failures in the subsequent
    84       chapters, it often turns out that removing everything and starting over
    85       (more carefully) is the best option to recover. Unfortunately, all the
    86       temporary files will be removed, too. To avoid spending extra time to
    87       redo something which has been built successfully, prepare a backup.
     102      Make sure you have at least 1 GB free disk space (the source tarballs
     103      will be included in the backup archive) on the filesystem containing
     104      directory where you create the backup archive.
    88105    </para>
    89106
    90107    <para>
    91       Make sure you have at least 1 GB free disk space (the source tarballs
    92       will be included in the backup archive) in the home directory of user
    93       <systemitem class="username">root</systemitem>.
     108      Note that the instructions below specify the home directory of the host
     109      system's <systemitem class="username">root</systemitem> user, which is
     110      typically found on the root filesystem.
    94111    </para>
    95112
    96     <para>Before we make a backup, unmount the virtual file systems:</para>
    97 
    98 <screen role="nodump"><userinput>umount $LFS/dev{/pts,}
    99 umount $LFS/{sys,proc,run}</userinput></screen>
     113    <para>
     114      Replace <envar>$HOME</envar> by a directory of your choice if you
     115      do not want to have the backup stored in <systemitem
     116      class="username">root</systemitem>'s home directory.
     117    </para>
    100118
    101119    <para>
    … …  
    108126          long time (over 10 minutes) even on a resonably fast system.
    109127       </para>
    110        
    111        <para>
    112           Also, ensure the <envar>LFS</envar> environment variable is set
    113           for the root user.
    114        </para>
    115128    </note>
    116129
    … …  
    121134tar -cJpf $HOME/lfs-temp-tools-&versiond;.tar.xz .</userinput></screen>
    122135
    123     <para>
    124       Replace <envar>$HOME</envar> by a directory of your choice if you
    125       do not want to have the backup stored in <systemitem
    126       class="username">root</systemitem>'s home directory.
    127     </para>
    128136  </sect2>
    129137
Note: See TracChangeset for help on using the changeset viewer.