source: chapter07/cleanup.xml@ d4c8dce4

11.1 11.1-rc1 arm multilib trunk xry111/clfs-ng xry111/lfs-next
Last change on this file since d4c8dce4 was d4c8dce4, checked in by Pierre Labastie <pierre.labastie@…>, 8 months ago

Merge branch 'trunk' into plabs/condxml

  • Property mode set to 100644
File size: 6.6 KB
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3 "" [
4 <!ENTITY % general-entities SYSTEM "../general.ent">
5 %general-entities;
8<sect1 id="ch-tools-cleanup">
9 <?dbhtml filename="cleanup.html"?>
11 <title>Cleaning up and Saving the Temporary System</title>
13 <sect2>
14 <title>Cleaning</title>
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>
19<screen><userinput>rm -rf /usr/share/{info,man,doc}/*</userinput></screen>
21 <para>Second, the libtool .la files are only useful when linking with static
22 libraries. They are unneeded and potentially harmful when using dynamic
23 shared libraries, especially when using non-autotools build systems.
24 While still in chroot, remove those files now:</para>
26<screen><userinput>find /usr/{lib,libexec} -name \*.la -delete</userinput></screen>
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>
34<screen><userinput>rm -rf /tools</userinput></screen>
35 </sect2>
37 <sect2>
38 <title>Backup</title>
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>
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>
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>
70 <para>
71 If you have decided to make a backup, leave the chroot environment:
72 </para>
74<screen role="nodump"><userinput>exit</userinput></screen>
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>
96 <para>Before making a backup, unmount the virtual file systems:</para>
98<screen role="nodump"><userinput>umount $LFS/dev/pts
99umount $LFS/{sys,proc,run,dev}</userinput></screen>
101 <para>
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.
105 </para>
107 <para>
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.
111 </para>
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>
119 <para>
120 Create the backup archive by running the following command:
121 </para>
123 <note>
124 <para>
125 Because the backup archive is compressed, it takes a relatively
126 long time (over 10 minutes) even on a resonably fast system.
127 </para>
128 </note>
130<screen role="nodump"><userinput>cd $LFS
131tar -cJpf $HOME/lfs-temp-tools-&version;.tar.xz .</userinput></screen>
133 </sect2>
135 <sect2>
136 <title>Restore</title>
138 <para>
139 In case some mistakes have been made and you need to start over, you can
140 use this backup to restore the system and save some recovery time.
141 Since the sources are located under
142 <filename class="directory">$LFS</filename>, they are included in the
143 backup archive as well, so they do not need to be downloaded again. After
144 checking that <envar>$LFS</envar> is set properly,
145 restore the backup by executing the following commands:
146 </para>
148<!-- Make the following look different so users don't blindly run the
149 restore when they don't need to. -->
151 <warning><para>The following commands are extremly dangerous. If
152 you run <command>rm -rf ./*</command> as the root user and you
153 do not change to the $LFS directory or the <envar>LFS</envar>
154 environment variable is not set for the root user, it will destroy
155 your entire host system. YOU ARE WARNED.</para></warning>
157<screen role="nodump"><computeroutput>cd $LFS
158rm -rf ./*
159tar -xpf $HOME/lfs-temp-tools-&version;.tar.xz</computeroutput></screen>
161 <para>
162 Again, double check that the environment has been setup properly
163 and continue building the rest of the system.
164 </para>
166 <important>
167 <para>
168 If you left the chroot environment to create a backup or restart
169 building using a restore, remember to check that the virtual
170 filesystems are still mounted (<command>findmnt | grep
171 $LFS</command>). If they are not mounted, remount them now as
172 described in <xref linkend='ch-tools-kernfs'/> and re-enter the chroot
173 environment (see <xref linkend='ch-tools-chroot'/>) before continuing.
174 </para>
175 </important>
177 </sect2>
Note: See TracBrowser for help on using the repository browser.