source: introduction/important/unpacking.xml@ 75d7f3d7

10.0 10.1 11.0 11.1 6.0 6.1 6.2 6.2.0 6.2.0-rc1 6.2.0-rc2 6.3 6.3-rc1 6.3-rc2 6.3-rc3 7.10 7.4 7.5 7.6 7.6-blfs 7.6-systemd 7.7 7.8 7.9 8.0 8.1 8.2 8.3 8.4 9.0 9.1 basic bdubbs/svn elogind gnome kde5-13430 kde5-14269 kde5-14686 krejzi/svn lazarus nosym perl-modules qt5new systemd-11177 systemd-13485 trunk upgradedb v1_0 v5_0 v5_0-pre1 v5_1 v5_1-pre1 xry111/intltool xry111/test-20220226
Last change on this file since 75d7f3d7 was 75d7f3d7, checked in by Larry Lawrence <larry@…>, 20 years ago

Typos in bootdisk, inputrc and unpacking

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@317 af4574ff-66df-0310-9fd7-8a98e5e911e0

  • Property mode set to 100644
File size: 2.3 KB
Line 
1<sect1 id="intro-important-unpacking">
2<?dbhtml filename="unpacking.html" dir="introduction"?>
3<title>Getting and unpacking the software</title>
4
5<para>Those people who have built a LFS system will be aware of the
6general principles of downloading and unpacking software. We will
7however repeat some of that information here for those new to building
8their own software.</para>
9
10<para>One difference from the LFS book is that we do <emphasis>not</emphasis>
11mirror the packages on the BLFS website.
12Instead, each set of installation instructions contains a URL from which
13you can download the package. We do however keep a selection of patches
14available via http/ftp. These are referenced as needed in the
15installation instructions.</para>
16
17<para>Whilst you can keep the source tarballs anywhere you like, we
18assume that you have unpacked them and unzipped any required patches
19into <filename>/usr/src</filename>.</para>
20
21<para>We can not emphasise strongly enough that you should start from a
22<emphasis>clean source tree</emphasis> each time. This means that if
23you have had an error, it's usually best to delete the source tree and
24re-unpack it <emphasis>before</emphasis> trying again. This obviously
25doesn't apply if you're an advanced user used to hacking Makefiles and C
26code, but if in doubt, start from a clean tree.</para>
27
28<sect2>
29<title>Unpacking the software</title>
30
31<para>If a file is tar'ed and gzip'ed, it is unpacked by running one of
32the following two commands, depending on the filename:</para>
33
34<screen><userinput>tar -xvzf filename.tar.gz
35tar -xvzf filename.tgz
36tar -xvzf filename.tar.Z</userinput></screen>
37
38<para>If a file is tar'ed and bzip2'ed, it can usually be unpacked by
39running:</para>
40
41<screen><userinput>tar -jxvf filename.tar.bz2</userinput></screen>
42
43<para>This applies as long as you patched tar to include the j option
44during your LFS install. If you didn't, you can use a slightly
45different method:</para>
46
47<screen><userinput>bzcat filename.tar.bz2 | tar -xv</userinput></screen>
48
49<para>Finally, you need to be able to unpack patches which are generally
50not tar'd. The best way to do this is to copy the patch file to
51<filename>/usr/src</filename> and then to run one of the following
52commands depending on whether the file is .gz or .bz2:</para>
53
54<screen><userinput>gunzip patchname.gz
55bunzip2 patchname.bz2</userinput></screen>
56
57</sect2>
58
59</sect1>
Note: See TracBrowser for help on using the repository browser.