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 you will find the package files being tar'ed and
|
---|
7 | gzip'ed (you can determind this 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 you how to do that once, in this paragraph.
|
---|
11 | There is also the possibility that you have the ability of downloading
|
---|
12 | a .tar.bz2 file. Such a file is tar'ed and compressed with the bzip2 program.
|
---|
13 | Bzip2 achieves a better compression than the commonly used gzip does. In
|
---|
14 | order to use bz2 archives you need to have the bzip2 program installed.
|
---|
15 | Most if not every distribution comes with this program so chances are
|
---|
16 | high it is already installed on your system. If not, install it using
|
---|
17 | your 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 | When you have a file that is tar'ed and gzip'ed, you unpack it by
|
---|
32 | running either one of the following two commands, depending on the
|
---|
33 | filename format:
|
---|
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 | When you have a file that is tar'ed and bzip'ed, you unpack it 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.
|
---|
60 | </para>
|
---|
61 |
|
---|
62 | <para>
|
---|
63 | When you have a file that is tar'ed, you unpack it by running:
|
---|
64 | </para>
|
---|
65 |
|
---|
66 | <blockquote><literallayout>
|
---|
67 |
|
---|
68 | <userinput>tar xvf filename.tar</userinput>
|
---|
69 |
|
---|
70 | </literallayout></blockquote>
|
---|
71 |
|
---|
72 | <para>
|
---|
73 | When the archive is unpacked a new directory will be created under the
|
---|
74 | current directory (and this document assumes that you unpack the archives
|
---|
75 | under the $LFS/usr/src directory). You have to enter that new directory
|
---|
76 | before you continue with the installation instructions. So everytime the
|
---|
77 | book is going to install a program, it's up to you to unpack the source
|
---|
78 | archive.
|
---|
79 | </para>
|
---|
80 |
|
---|
81 | <para>
|
---|
82 | After you have installed a package you can do two things with it. You can
|
---|
83 | either delete the directory that contains the sources or you can keep it.
|
---|
84 | If you decide to keep it, that's fine by me. But if you need the same package
|
---|
85 | again in a later chapter you need to delete the directory first before using
|
---|
86 | it again. If you don't do this, you might end up in trouble because old
|
---|
87 | settings will be used (settings that apply to your normal Linux system but
|
---|
88 | which don't always apply to your LFS system). Doing a simple make clean
|
---|
89 | or make distclean does not always guarantee a totally clean source tree.
|
---|
90 | The configure script can also have files lying around in various
|
---|
91 | subdirectories which aren't always removed by a make clean process.
|
---|
92 | </para>
|
---|
93 |
|
---|
94 | <para>
|
---|
95 | There is on exception to that rule: don't remove the linux kernel source
|
---|
96 | tree. A lot of programs need the kernel headers, so that's the only
|
---|
97 | directory you don't want to remove, unless you are not going to
|
---|
98 | compile any software anymore.
|
---|
99 | </para>
|
---|
100 |
|
---|
101 | </sect1>
|
---|
102 |
|
---|