Ignore:
Timestamp:
02/04/2005 07:30:54 AM (19 years ago)
Author:
Bruce Dubbs <bdubbs@…>
Branches:
10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.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, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
Children:
843cc38c
Parents:
fb31251
Message:

Minor wording changes in chapters 1 and 2

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

File:
1 edited

Legend:

Unmodified
Added
Removed

  • introduction/important/unpacking.xml

    rfb31251 r20828163  
    1212</sect1info>
    1313<?dbhtml filename="unpacking.html"?>
    14 <title>Notes on downloading, unpacking and compiling software</title>
     14<title>Notes on building software</title>
    1515
    16 <para>Those people who have built a <acronym>LFS</acronym> system will be aware
     16<para>Those people who have built an <acronym>LFS</acronym> system will be aware
    1717of the general principles of downloading and unpacking software.  We will
    1818however repeat some of that information here for those new to building
    … …  
    2424installation instructions.</para>
    2525
    26 <para>While you can keep the source <acronym>TAR</acronym> balls anywhere you like, we
     26<para>While you can keep the source files anywhere you like, we
    2727assume that you have unpacked them and unzipped any required patches
    2828into <filename>/usr/src</filename>.</para>
    … …  
    3939
    4040<para>If a file is tar'ed and gzip'ed, it is unpacked by running one of
    41 the following two commands, depending on the filename:</para>
     41the following commands, depending on the filename:</para>
    4242
    4343<screen><command>tar -xvzf filename.tar.gz
    … …  
    5454<screen><command>bzcat filename.tar.bz2 | tar -xv</command></screen>
    5555
    56 <para>Finally, you need to be able to unpack patches which are generally
    57 not tar'ed.  The best way to do this is to copy the patch file to
    58 <filename>/usr/src</filename> and then to run one of the following
    59 commands depending on whether the file is .gz or .bz2:</para>
     56<para>Finally, you sometimes need to be able to unpack patches which are
     57generally not tar'ed.  The best way to do this is to copy the patch file to
     58<filename>/usr/src</filename> and then to run one of the following commands
     59depending on whether the file is .gz or .bz2:</para>
    6060
    6161<screen><command>gunzip patchname.gz
Note: See TracChangeset for help on using the changeset viewer.