Ignore:
Timestamp:
08/08/2004 02:10:10 AM (20 years ago)
Author:
Gerard Beekmans <gerard@…>
Branches:
6.0
Children:
78349b7
Parents:
9a207c4
Message:

Completed global edits for upcoming 6.0 release

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

File:
1 edited

Legend:

Unmodified
Added
Removed

  • chapter03/introduction.xml

    r9a207c4 r843710f  
    88<?dbhtml filename="introduction.html"?>
    99
    10 <para>Below is a list of packages you need to download for building a basic
    11 Linux system. The listed version numbers correspond to versions of the
    12 software that are <emphasis>known</emphasis> to work, and this book is
    13 based upon them. Unless you are an experienced LFS builder, we highly
    14 recommend not to try out newer versions, as the build commands for one
    15 version may not work with a newer version. Also, there is often a good
    16 reason for not using the latest version due to known problems that haven't
    17 been worked around yet.</para>
     10<para>Below is a list of packages that need to be download for building a
     11basic Linux system. The listed version numbers correspond to versions
     12of the software that are known to work, and this book is based on
     13their use. We highly recommend not using newer versions, as the build
     14commands for one version may not work with a newer version. The newest
     15package versions may also have problems that work-arounds have
     16not been developed for yet.</para>
    1817
    19 <para>All the URLs, when possible, refer to the project's page at
    20 <ulink url="http://www.freshmeat.net/"/>. The Freshmeat
    21 pages will give you easy access to the official download sites as well as
    22 project websites, mailing lists, FAQs, changelogs and more.</para>
     18<para>All the URLs, when possible, refer to the package's information
     19page at <ulink url="http://www.freshmeat.net/"/>. The Freshmeat pages
     20provide easy access to official download sites, as well as project
     21websites, mailing lists, FAQs, changelogs, and more.</para>
    2322
    24 <para>We can't guarantee that these download locations are always available.
    25 In case a download location has changed since this book was published, please
    26 try to google for the package. Should you remain unsuccessful with this,
    27 try one of the alternative means of downloading listed on
    28 <ulink url="&lfs-root;lfs/packages.html"/>.</para>
     23<para>Download locations may not always be accessible. If a download
     24location has changed since this book was published, Google (<ulink
     25url="http://www.google.com"/>) provides a useful search engine for
     26most packages. If this search is unsuccessful, try one of the
     27alternative means of downloading discussed at <ulink
     28url="&lfs-root;lfs/packages.html"/>.</para>
    2929
    30 <para>You'll need to store all the downloaded packages and patches somewhere
    31 that is conveniently available throughout the entire build. You'll also need a
    32 working directory in which to unpack the sources and build them. A scheme that
    33 works well is to use <filename class="directory">$LFS/sources</filename> as the place to store
    34 the tarballs and patches, <emphasis>and</emphasis> as a working directory.
    35 This way everything you need will be located on the LFS partition and available
    36 during all stages of the building process.</para>
     30<para>Downloaded packages and patches will need to be stores somewhere
     31that is conveniently available throughout the entire build. A working
     32directory is also required to unpack the sources and build them.
     33<filename class="directory">$LFS/sources</filename> can be used both
     34as the place to store the tarballs and patches and as a working
     35directory. By using this directory, the required elements will be
     36located on the LFS partition and will be available during all stages
     37of the building process.</para>
    3738
    38 <para>So you may want to execute, as <emphasis>root</emphasis>, the following
    39 command before starting your download session:</para>
     39<para>To create this directory, execute, as user
     40<emphasis>root</emphasis>, the following command before starting the
     41download session:</para>
    4042
    4143<screen><userinput>mkdir $LFS/sources</userinput></screen>
    4244
    43 <para>And make this directory writable (and sticky) for your normal user -- as
    44 you won't do the downloading as <emphasis>root</emphasis>, we guess:</para>
     45<para>Make this directory writable (and sticky -- which basically
     46means that eventhough a user may have write permissions on a
     47directory, the sticky tag prevents users from removing files they do
     48not own as normally write permission on a directory means the owner of
     49the directory can remove all files in it, even if he does not own the
     50file) for your normal user -- as you won't do the downloading as root, we
     51guess:</para>
    4552
    4653<screen><userinput>chmod a+wt $LFS/sources</userinput></screen>
    4754
    48 <!--
    49 <para>For your convenience the top of the list contains a link to a file
    50 you can use with the <ulink url="http://wget.sunsite.dk">wget</ulink>
    51 program. Using this file and the <command>wget</command> program will
    52 make it easy to download all the files at once, rather than downloading each
    53 and every individual file manually.</para>
    54 -->
     55</sect1>
    5556
    56 </sect1>
Note: See TracChangeset for help on using the changeset viewer.