1 | <sect1 id="ch02-install">
|
---|
2 | <title>How to install the software</title>
|
---|
3 |
|
---|
4 | <para>
|
---|
5 | Before you can actually start doing something with a package, you need
|
---|
6 | to unpack it first. Often the package files are tar'ed and
|
---|
7 | gzip'ed. (That can be determined by looking at the extension of the file.
|
---|
8 | Tar'ed and gzip'ed archives have a .tar.gz or .tgz extension, for
|
---|
9 | example.) I'm not going to write down every time how to ungzip and how
|
---|
10 | to untar an archive. I will tell how to do that once, in this section.
|
---|
11 | There is also the possibility that a .tar.bz2 file could be downloaded.
|
---|
12 | Such a file would be tar'ed and compressed with the bzip2 program.
|
---|
13 | Bzip2 achieves a better compression than the more commonly used gzip does.
|
---|
14 | In order to use bz2 archives, the bzip2 program needs to be installed.
|
---|
15 | Most if not every distribution comes with this program, so chances are
|
---|
16 | high it is already installed on the host system. If not, it's installed
|
---|
17 | using the distribution's installation tool.
|
---|
18 | </para>
|
---|
19 |
|
---|
20 | <para>
|
---|
21 | To start with, change to the $LFS/usr/src directory by running:
|
---|
22 | </para>
|
---|
23 |
|
---|
24 | <blockquote><literallayout>
|
---|
25 |
|
---|
26 | <userinput>cd $LFS/usr/src</userinput>
|
---|
27 |
|
---|
28 | </literallayout></blockquote>
|
---|
29 |
|
---|
30 | <para>
|
---|
31 | If a file is tar'ed and gzip'ed, it is unpacked by
|
---|
32 | running either one of the following two commands, depending on the
|
---|
33 | filename:
|
---|
34 | </para>
|
---|
35 |
|
---|
36 | <blockquote><literallayout>
|
---|
37 |
|
---|
38 | <userinput>tar xvzf filename.tar.gz</userinput>
|
---|
39 | <userinput>tar xvzf filename.tgz</userinput>
|
---|
40 |
|
---|
41 | </literallayout></blockquote>
|
---|
42 |
|
---|
43 |
|
---|
44 | <para>
|
---|
45 | If a file is tar'ed and bzip2'ed, it is unpacked by
|
---|
46 | running:
|
---|
47 | </para>
|
---|
48 |
|
---|
49 | <blockquote><literallayout>
|
---|
50 |
|
---|
51 | <userinput>bzcat filename.tar.bz2 | tar xv</userinput>
|
---|
52 |
|
---|
53 | </literallayout></blockquote>
|
---|
54 |
|
---|
55 | <para>
|
---|
56 | Some tar programs (most of them nowadays but not all of them) are
|
---|
57 | slightly modified to be able to use bzip2 files directly using either
|
---|
58 | the I or the y tar parameter, which works the same as the z tar parameter
|
---|
59 | to handle gzip archives. The above construction works no matter how
|
---|
60 | your host system decided to patch bzip2.
|
---|
61 | </para>
|
---|
62 |
|
---|
63 | <para>
|
---|
64 | If a file is just tar'ed, it is unpacked by running:
|
---|
65 | </para>
|
---|
66 |
|
---|
67 | <blockquote><literallayout>
|
---|
68 |
|
---|
69 | <userinput>tar xvf filename.tar</userinput>
|
---|
70 |
|
---|
71 | </literallayout></blockquote>
|
---|
72 |
|
---|
73 | <para>
|
---|
74 | When the archive is unpacked, a new directory will be created under the
|
---|
75 | current directory (and this document assumes that the archives are unpacked
|
---|
76 | under the $LFS/usr/src directory). Please enter that new directory
|
---|
77 | before continuing with the installation instructions. Again, every time
|
---|
78 | this book is going to install a package, it's up to you to unpack the source
|
---|
79 | archive and cd into the newly created directory.
|
---|
80 | </para>
|
---|
81 |
|
---|
82 | <para>
|
---|
83 | From time to time you will be dealing with single files such as patch
|
---|
84 | files. These files are generally gzip'ed or bzip2'ed. Before such files
|
---|
85 | can be used they need to be uncompressed first.
|
---|
86 | </para>
|
---|
87 |
|
---|
88 | <para>
|
---|
89 | If a file is gzip'ed, it is unpacked by running:
|
---|
90 | </para>
|
---|
91 |
|
---|
92 | <blockquote><literallayout>
|
---|
93 |
|
---|
94 | <userinput>gunzip filename.gz</userinput>
|
---|
95 |
|
---|
96 | </literallayout></blockquote>
|
---|
97 |
|
---|
98 | <para>
|
---|
99 | If a file is bzip2'ed, it is unpacked by running:
|
---|
100 | </para>
|
---|
101 |
|
---|
102 | <blockquote><literallayout>
|
---|
103 |
|
---|
104 | <userinput>bunzip2 filename.bz2</userinput>
|
---|
105 |
|
---|
106 | </literallayout></blockquote>
|
---|
107 |
|
---|
108 | <para>
|
---|
109 | After a package is installed, two things can be done with it:
|
---|
110 | either the directory that contains the sources can be deleted,
|
---|
111 | either it can be kept. If it is kept, that's fine with me, but if the
|
---|
112 | same package is needed again in a later chapter, the directory
|
---|
113 | needs to be deleted first before using it again. If this is not done,
|
---|
114 | you might end up in trouble because old settings will be used (settings
|
---|
115 | that apply to the normal Linux system but which don't always apply to
|
---|
116 | the LFS system). Doing a simple make clean or make distclean does not
|
---|
117 | always guarantee a totally clean source tree.
|
---|
118 | </para>
|
---|
119 |
|
---|
120 | <para>
|
---|
121 | There is one exception to that rule: don't remove the linux kernel source
|
---|
122 | tree. A lot of programs need the kernel headers, so that's the only
|
---|
123 | directory that should not be removed, unless no software is to be compiled
|
---|
124 | anymore.
|
---|
125 | </para>
|
---|
126 |
|
---|
127 | </sect1>
|
---|
128 |
|
---|