source: chapter07/cleanup.xml@ a8f3814a

11.3 11.3-rc1 12.0 12.0-rc1 12.1 12.1-rc1 bdubbs/gcc13 multilib renodr/libudev-from-systemd trunk xry111/arm64 xry111/arm64-12.0 xry111/clfs-ng xry111/loongarch xry111/loongarch-12.0 xry111/loongarch-12.1 xry111/mips64el xry111/pip3 xry111/rust-wip-20221008 xry111/update-glibc
Last change on this file since a8f3814a was 01ecba7, checked in by Bruce Dubbs <bdubbs@…>, 19 months ago

Fix unmounting instruction in 7.13.2. Backup

  • Property mode set to 100644
File size: 6.8 KB
Line 
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
4 <!ENTITY % general-entities SYSTEM "../general.ent">
5 %general-entities;
6]>
7
8<sect1 id="ch-tools-cleanup">
9 <?dbhtml filename="cleanup.html"?>
10
11 <title>Cleaning up and Saving the Temporary System</title>
12
13 <sect2>
14 <title>Cleaning</title>
15
16 <para>First, remove the currently installed documentation to prevent them
17 from ending up in the final system, and to save about 35 MB:</para>
18
19<screen><userinput>rm -rf /usr/share/{info,man,doc}/*</userinput></screen>
20
21 <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>
25
26<screen><userinput>find /usr/{lib,libexec} -name \*.la -delete</userinput></screen>
27
28 <para>
29 The current system size is now about 3 GB, however
30 the /tools directory is no longer needed. It uses about
31 1 GB of disk space. Delete it now:
32 </para>
33
34<screen><userinput>rm -rf /tools</userinput></screen>
35 </sect2>
36
37 <sect2>
38 <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>
50
51 <note><para>
52 All the remaining steps in this section are optional. Nevertheless,
53 as soon as you begin installing packages in <xref
54 linkend="chapter-building-system"/>, the temporary files will be
55 overwritten. So it may be a good idea to do a backup of the current
56 system as described below.
57 </para></note>
58
59 <para>
60 The following steps are performed from outside the chroot
61 environment. That means, you have to leave the chroot environment
62 first before continuing. The reason for that is to
63 get access to file system locations outside of the chroot
64 environment to store/read the backup archive which should
65 not be placed within the
66 <filename class="directory">$LFS</filename> hierarchy for
67 safety reasons.
68 </para>
69
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
76 <important>
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
81 here can modify your host system. Be aware that the
82 environment variable <envar>LFS</envar>
83 is set for user <systemitem class="username">lfs</systemitem> by default
84 but may <emphasis>not</emphasis> be set for
85 <systemitem class="username">root</systemitem>.
86 </para>
87 <para>
88 Whenever commands are to be executed by <systemitem class="username">root</systemitem>,
89 make sure you have set <envar>LFS</envar>.
90 </para>
91 <para>
92 This has been discussed in <xref linkend='ch-partitioning-aboutlfs'/>.
93 </para>
94 </important>
95
96 <para>Before making a backup, unmount the virtual file systems:</para>
97
98<screen role="nodump"><userinput>mountpoint -q $LFS/dev/shm &amp;&amp; umount $LFS/dev/shm
99umount $LFS/dev/pts
100umount $LFS/{sys,proc,run,dev}</userinput></screen>
101
102 <para>
103 Make sure you have at least 1 GB free disk space (the source tarballs
104 will be included in the backup archive) on the filesystem containing
105 directory where you create the backup archive.
106 </para>
107
108 <para>
109 Note that the instructions below specify the home directory of the host
110 system's <systemitem class="username">root</systemitem> user, which is
111 typically found on the root filesystem.
112 </para>
113
114 <para>
115 Replace <envar>$HOME</envar> by a directory of your choice if you
116 do not want to have the backup stored in <systemitem
117 class="username">root</systemitem>'s home directory.
118 </para>
119
120 <para>
121 Create the backup archive by running the following command:
122 </para>
123
124 <note>
125 <para>
126 Because the backup archive is compressed, it takes a relatively
127 long time (over 10 minutes) even on a reasonably fast system.
128 </para>
129 </note>
130
131<screen role="nodump"><userinput>cd $LFS
132tar -cJpf $HOME/lfs-temp-tools-&version;.tar.xz .</userinput></screen>
133
134 <note>
135 <para>
136 If continuing to chapter 8, don't forget to reenter the chroot
137 environment as explained in the <quote>Important</quote> box below.
138 </para>
139 </note>
140
141 </sect2>
142
143 <sect2>
144 <title>Restore</title>
145
146 <para>
147 In case some mistakes have been made and you need to start over, you can
148 use this backup to restore the system and save some recovery time.
149 Since the sources are located under
150 <filename class="directory">$LFS</filename>, they are included in the
151 backup archive as well, so they do not need to be downloaded again. After
152 checking that <envar>$LFS</envar> is set properly,
153 restore the backup by executing the following commands:
154 </para>
155
156<!-- Make the following look different so users don't blindly run the
157 restore when they don't need to. -->
158
159 <warning><para>The following commands are extremely dangerous. If
160 you run <command>rm -rf ./*</command> as the &root; user and you
161 do not change to the $LFS directory or the <envar>LFS</envar>
162 environment variable is not set for the &root; user, it will destroy
163 your entire host system. YOU ARE WARNED.</para></warning>
164
165<screen role="nodump"><computeroutput>cd $LFS
166rm -rf ./*
167tar -xpf $HOME/lfs-temp-tools-&version;.tar.xz</computeroutput></screen>
168
169 <para>
170 Again, double check that the environment has been setup properly
171 and continue building the rest of the system.
172 </para>
173
174 <important>
175 <para>
176 If you left the chroot environment to create a backup or restart
177 building using a restore, remember to check that the virtual
178 filesystems are still mounted (<command>findmnt | grep
179 $LFS</command>). If they are not mounted, remount them now as
180 described in <xref linkend='ch-tools-kernfs'/> and re-enter the chroot
181 environment (see <xref linkend='ch-tools-chroot'/>) before continuing.
182 </para>
183 </important>
184
185 </sect2>
186
187</sect1>
Note: See TracBrowser for help on using the repository browser.