1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
---|
2 | <!DOCTYPE section [
|
---|
3 | <!ENTITY % general-entities SYSTEM "../general.ent">
|
---|
4 | %general-entities;
|
---|
5 | ]>
|
---|
6 | <section xmlns="http://docbook.org/docbook-ng"
|
---|
7 | xmlns:xlink="http://www.w3.org/1999/xlink"
|
---|
8 | xml:id="materials-introduction">
|
---|
9 | <info><title>Introduction</title></info>
|
---|
10 | <?dbhtml filename="introduction.html"?>
|
---|
11 |
|
---|
12 | <para>Below is a list of packages you need to download for building a basic
|
---|
13 | Linux system. The listed version numbers correspond to versions of the
|
---|
14 | software that are <emphasis>known</emphasis> to work, and this book is
|
---|
15 | based upon them. Unless you are an experienced LFS builder, we highly
|
---|
16 | recommend not to try out newer versions, as the build commands for one
|
---|
17 | version may not work with a newer version. Also, there is often a good
|
---|
18 | reason for not using the latest version due to known problems that haven't
|
---|
19 | been worked around yet.</para>
|
---|
20 |
|
---|
21 | <para>All the URLs, when possible, refer to the project's page at
|
---|
22 | <uri xlink:href="http://www.freshmeat.net/">http://www.freshmeat.net/</uri>.
|
---|
23 | The Freshmeat pages will give you easy access to the official download sites as
|
---|
24 | well as project websites, mailing lists, FAQs, changelogs and more.</para>
|
---|
25 |
|
---|
26 | <para>We can't guarantee that these download locations are always available.
|
---|
27 | In case a download location has changed since this book was published, please
|
---|
28 | try to google for the package. Should you remain unsuccessful with this,
|
---|
29 | try one of the alternative means of downloading listed on
|
---|
30 | <uri xlink:href="&lfs-root;lfs/packages.html">&lfs-root;lfs/packages.html</uri>.</para>
|
---|
31 |
|
---|
32 | <para>You'll need to store all the downloaded packages and patches somewhere
|
---|
33 | that is conveniently available throughout the entire build. You'll also need a
|
---|
34 | working directory in which to unpack the sources and build them. A scheme that
|
---|
35 | works well is to use <filename class="directory">$LFS/sources</filename> as the place to store
|
---|
36 | the tarballs and patches, <emphasis>and</emphasis> as a working directory.
|
---|
37 | This way everything you need will be located on the LFS partition and available
|
---|
38 | during all stages of the building process.</para>
|
---|
39 |
|
---|
40 | <para>So you may want to execute, as <emphasis>root</emphasis>, the following
|
---|
41 | command before starting your download session:</para>
|
---|
42 |
|
---|
43 | <screen><userinput>mkdir $LFS/sources</userinput></screen>
|
---|
44 |
|
---|
45 | <para>And make this directory writable (and sticky) for your normal user -- as
|
---|
46 | you won't do the downloading as <emphasis>root</emphasis>, we guess:</para>
|
---|
47 |
|
---|
48 | <screen><userinput>chmod a+wt $LFS/sources</userinput></screen>
|
---|
49 |
|
---|
50 | <!--
|
---|
51 | <para>For your convenience the top of the list contains a link to a file
|
---|
52 | you can use with the <ulink url="http://wget.sunsite.dk">wget</ulink>
|
---|
53 | program. Using this file and the <command>wget</command> program will
|
---|
54 | make it easy to download all the files at once, rather than downloading each
|
---|
55 | and every individual file manually.</para>
|
---|
56 | -->
|
---|
57 |
|
---|
58 | </section>
|
---|