source: chapter02/install.xml@ bd8f55a

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 bd8f55a was 702997a, checked in by Mark Hymers <markh@…>, 23 years ago

spelling correction

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

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