Ignore:
Timestamp:
07/22/2001 07:45:10 PM (23 years ago)
Author:
Mark Hymers <markh@…>
Branches:
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
Children:
f1da843
Parents:
46f5461
Message:

XML changes

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

File:
1 edited

Legend:

Unmodified
Added
Removed

  • chapter02/install.xml

    r46f5461 rb822811  
    22<title>How to install the software</title>
    33
    4 <para>
    5 Before you can actually start doing something with a package, you need
     4<para>Before you can actually start doing something with a package, you need
    65to unpack it first. Often the package files are tar'ed and
    76gzip'ed or bzip2'ed. I'm not going to write down every time how to
    87unpack an archive. I will explain how to do that once, in this
    9 section.
    10 </para>
     8section.</para>
    119
    12 <para>
    13 To start with, change to the $LFS/usr/src directory by running:
    14 </para>
     10<para>To start with, change to the $LFS/usr/src directory by running:</para>
    1511
    16 <para>
    17 <screen>
    18 <userinput>cd $LFS/usr/src</userinput>
    19 </screen>
    20 </para>
     12<para><screen><userinput>cd $LFS/usr/src</userinput></screen></para>
    2113
    22 <para>
    23 If a file is tar'ed and gzip'ed, it is unpacked by
     14<para>If a file is tar'ed and gzip'ed, it is unpacked by
    2415running either one of the following two commands, depending on the
    25 filename:
    26 </para>
     16filename:</para>
    2717
    28 <para>
    29 <screen>
    30 <userinput>tar xvzf filename.tar.gz</userinput>
    31 <userinput>tar xvzf filename.tgz</userinput>
    32 </screen>
    33 </para>
     18<para><screen><userinput>tar xvzf filename.tar.gz</userinput>
     19<userinput>tar xvzf filename.tgz</userinput></screen></para>
    3420
    3521
    36 <para>
    37 If a file is tar'ed and bzip2'ed, it is unpacked by
    38 running:
    39 </para>
     22<para>If a file is tar'ed and bzip2'ed, it is unpacked by
     23running:</para>
    4024
    41 <para>
    42 <screen>
    43 <userinput>bzcat filename.tar.bz2 | tar xv</userinput>
    44 </screen>
    45 </para>
     25<para><screen><userinput>bzcat filename.tar.bz2 | tar xv</userinput></screen></para>
    4626
    47 <para>
    48 Some tar programs (most of them nowadays but not all of them) are
     27<para>Some tar programs (most of them nowadays but not all of them) are
    4928slightly modified to be able to use bzip2 files directly using either
    5029the I or the y tar parameter, which works the same as the z tar parameter
    5130to handle gzip archives. The above construction works no matter how
    52 your host system decided to patch bzip2.
    53 </para>
     31your host system decided to patch bzip2.</para>
    5432
    55 <para>
    56 If a file is just tar'ed, it is unpacked by running:
    57 </para>
     33<para>If a file is just tar'ed, it is unpacked by running:</para>
    5834
    59 <para>
    60 <screen>
    61 <userinput>tar xvf filename.tar</userinput>
    62 </screen>
    63 </para>
     35<para><screen><userinput>tar xvf filename.tar</userinput></screen></para>
    6436
    65 <para>
    66 When an archive is unpacked, a new directory will be created under the
     37<para>When an archive is unpacked, a new directory will be created under the
    6738current directory (and this book assumes that the archives are unpacked
    6839under the $LFS/usr/src directory). Please enter that new directory
    6940before continuing with the installation instructions. Again, every time
    7041this book is going to install a package, it's up to you to unpack the source
    71 archive and cd into the newly created directory.
    72 </para>
     42archive and cd into the newly created directory.</para>
    7343
    74 <para>
    75 From time to time you will be dealing with single files such as patch
     44<para>From time to time you will be dealing with single files such as patch
    7645files. These files are generally gzip'ed or bzip2'ed. Before such files
    77 can be used they need to be uncompressed first.
    78 </para>
     46can be used they need to be uncompressed first.</para>
    7947
    80 <para>
    81 If a file is gzip'ed, it is unpacked by running:
    82 </para>
     48<para>If a file is gzip'ed, it is unpacked by running:</para>
    8349
    84 <para>
    85 <screen>
    86 <userinput>gunzip filename.gz</userinput>
    87 </screen>
    88 </para>
     50<para><screen><userinput>gunzip filename.gz</userinput></screen></para>
    8951
    90 <para>
    91 If a file is bzip2'ed, it is unpacked by running:
    92 </para>
     52<para>If a file is bzip2'ed, it is unpacked by running:</para>
    9353
    94 <para>
    95 <screen>
    96 <userinput>bunzip2 filename.bz2</userinput>
    97 </screen>
    98 </para>
     54<para><screen><userinput>bunzip2 filename.bz2</userinput></screen></para>
    9955
    100 <para>
    101 After a package has been installed, two things can be done with it:
     56<para>After a package has been installed, two things can be done with it:
    10257either the directory that contains the sources can be deleted,
    10358or it can be kept. If it is kept, that's fine with me, but if the
    … …  
    10762that apply to the host system but which don't always apply to
    10863the LFS system). Doing a simple make clean or make distclean does not
    109 always guarantee a totally clean source tree.
    110 </para>
     64always guarantee a totally clean source tree.</para>
    11165
    112 <para>
    113 So, save yourself a lot of hassle and just remove the source directory
    114 immediately after you have installed it.
    115 </para>
     66<para>So, save yourself a lot of hassle and just remove the source directory
     67immediately after you have installed it.</para>
    11668
    117 <para>
    118 There is one exception; the kernel source tree. Keep it around as you
     69<para>There is one exception; the kernel source tree. Keep it around as you
    11970will need it later in this book when building a kernel. Nothing will use
    120 the kernel tree so it won't be in your way.
    121 </para>
     71the kernel tree so it won't be in your way.</para>
    12272
    12373</sect1>
Note: See TracChangeset for help on using the changeset viewer.