source: chapter02/install.xml@ bea68d8

10.0 10.0-rc1 10.1 10.1-rc1 11.0 11.0-rc1 11.0-rc2 11.0-rc3 11.1 11.1-rc1 11.2 11.2-rc1 11.3 11.3-rc1 12.0 12.0-rc1 12.1 12.1-rc1 6.0 6.1 6.1.1 6.3 6.4 6.5 6.6 6.7 6.8 7.0 7.1 7.2 7.3 7.4 7.5 7.5-systemd 7.6 7.6-systemd 7.7 7.7-systemd 7.8 7.8-systemd 7.9 7.9-systemd 8.0 8.1 8.2 8.3 8.4 9.0 9.1 arm bdubbs/gcc13 ml-11.0 multilib renodr/libudev-from-systemd s6-init trunk v3_0 v3_1 v3_2 v3_3 v4_0 v4_1 v5_0 v5_1 v5_1_1 xry111/arm64 xry111/arm64-12.0 xry111/clfs-ng xry111/lfs-next 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 bea68d8 was bea68d8, checked in by Gerard Beekmans <gerard@…>, 23 years ago

Noted that you can keep the kernel tree if you want to, since you need
it later in the book anyways

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@796 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

  • Property mode set to 100644
File size: 3.2 KB
Line 
1<sect1 id="ch02-install">
2<title>How to install the software</title>
3
4<para>
5Before you can actually start doing something with a package, you need
6to unpack it first. Often the package files are tar'ed and
7gzip'ed or bzip2'ed. I'm not going to write down every time how to
8unpack an archive. I will explain how to do that once, in this
9section.
10</para>
11
12<para>
13To start with, change to the $LFS/usr/src directory by running:
14</para>
15
16<para>
17<screen>
18<userinput>cd $LFS/usr/src</userinput>
19</screen>
20</para>
21
22<para>
23If a file is tar'ed and gzip'ed, it is unpacked by
24running either one of the following two commands, depending on the
25filename:
26</para>
27
28<para>
29<screen>
30<userinput>tar xvzf filename.tar.gz</userinput>
31<userinput>tar xvzf filename.tgz</userinput>
32</screen>
33</para>
34
35
36<para>
37If a file is tar'ed and bzip2'ed, it is unpacked by
38running:
39</para>
40
41<para>
42<screen>
43<userinput>bzcat filename.tar.bz2 | tar xv</userinput>
44</screen>
45</para>
46
47<para>
48Some tar programs (most of them nowadays but not all of them) are
49slightly modified to be able to use bzip2 files directly using either
50the I or the y tar parameter, which works the same as the z tar parameter
51to handle gzip archives. The above construction works no matter how
52your host system decided to patch bzip2.
53</para>
54
55<para>
56If a file is just tar'ed, it is unpacked by running:
57</para>
58
59<para>
60<screen>
61<userinput>tar xvf filename.tar</userinput>
62</screen>
63</para>
64
65<para>
66When an archive is unpacked, a new directory will be created under the
67current directory (and this book assumes that the archives are unpacked
68under the $LFS/usr/src directory). Please enter that new directory
69before continuing with the installation instructions. Again, every time
70this book is going to install a package, it's up to you to unpack the source
71archive and cd into the newly created directory.
72</para>
73
74<para>
75From time to time you will be dealing with single files such as patch
76files. These files are generally gzip'ed or bzip2'ed. Before such files
77can be used they need to be uncompressed first.
78</para>
79
80<para>
81If a file is gzip'ed, it is unpacked by running:
82</para>
83
84<para>
85<screen>
86<userinput>gunzip filename.gz</userinput>
87</screen>
88</para>
89
90<para>
91If a file is bzip2'ed, it is unpacked by running:
92</para>
93
94<para>
95<screen>
96<userinput>bunzip2 filename.bz2</userinput>
97</screen>
98</para>
99
100<para>
101After a package has been installed, two things can be done with it:
102either the directory that contains the sources can be deleted,
103or it can be kept. If it is kept, that's fine with me, but if the
104same package is needed again in a later chapter, the directory
105needs to be deleted first before using it again. If this is not done,
106you might end up in trouble because old settings will be used (settings
107that apply to the host system but which don't always apply to
108the LFS system). Doing a simple make clean or make distclean does not
109always guarantee a totally clean source tree.
110</para>
111
112<para>
113So, save yourself a lot of hassle and just remove the source directory
114immediately after you have installed it.
115</para>
116
117<para>
118There is one exception; the kernel source tree. Keep it around as you
119will need it later in this book when building a kernel. Nothing will use
120the kernel tree so it won't be in your way.
121</para>
122
123</sect1>
124
Note: See TracBrowser for help on using the repository browser.