| 1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
|---|
| 2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
|
|---|
| 3 | <!ENTITY % general-entities SYSTEM "../general.ent">
|
|---|
| 4 | %general-entities;
|
|---|
| 5 | ]>
|
|---|
| 6 | <sect1 id="materials-introduction">
|
|---|
| 7 | <title>Introduction</title>
|
|---|
| 8 | <?dbhtml filename="introduction.html"?>
|
|---|
| 9 |
|
|---|
| 10 | <para>This chapter includes a list of packages that need to be
|
|---|
| 11 | downloaded for building a basic Linux system. The listed version numbers
|
|---|
| 12 | correspond to versions of the software that are known to work, and
|
|---|
| 13 | this book is based on their use. We highly recommend not using newer
|
|---|
| 14 | versions because the build commands for one version may not work with
|
|---|
| 15 | a newer version. The newest package versions may also have problems
|
|---|
| 16 | that work-arounds have not been developed for yet.</para>
|
|---|
| 17 |
|
|---|
| 18 | <para>All the URLs, when possible, refer to the package's information
|
|---|
| 19 | page at <ulink url="http://www.freshmeat.net/"/>. The Freshmeat pages
|
|---|
| 20 | provide easy access to official download sites, as well as project
|
|---|
| 21 | websites, mailing lists, FAQ, changelogs, and more.</para>
|
|---|
| 22 |
|
|---|
| 23 | <para>Download locations may not always be accessible. If a download
|
|---|
| 24 | location has changed since this book was published, Google (<ulink
|
|---|
| 25 | url="http://www.google.com"/>) provides a useful search engine for
|
|---|
| 26 | most packages. If this search is unsuccessful, try one of the
|
|---|
| 27 | alternate means of downloading discussed at <ulink
|
|---|
| 28 | url="&lfs-root;lfs/packages.html"><phrase condition ="pdf">&lfs-root;
|
|---|
| 29 | lfs/packages.html</phrase></ulink>.</para>
|
|---|
| 30 |
|
|---|
| 31 | <para>Downloaded packages and patches will need to be stored somewhere
|
|---|
| 32 | that is conveniently available throughout the entire build. A working
|
|---|
| 33 | directory is also required to unpack the sources and build them.
|
|---|
| 34 | <filename class="directory">$LFS/sources</filename> can be used both
|
|---|
| 35 | as the place to store the tarballs and patches and as a working
|
|---|
| 36 | directory. By using this directory, the required elements will be
|
|---|
| 37 | located on the LFS partition and will be available during all stages
|
|---|
| 38 | of the building process.</para>
|
|---|
| 39 |
|
|---|
| 40 | <para>To create this directory, execute, as user
|
|---|
| 41 | <emphasis>root</emphasis>, the following command before starting the
|
|---|
| 42 | download session:</para>
|
|---|
| 43 |
|
|---|
| 44 | <screen><userinput>mkdir $LFS/sources</userinput></screen>
|
|---|
| 45 |
|
|---|
| 46 | <para>Make this directory writable and sticky. <quote>Sticky</quote>
|
|---|
| 47 | means that even if multiple users have write permission on a
|
|---|
| 48 | directory, only the owner of a file can delete the file within a
|
|---|
| 49 | sticky directory. The following command will enable the write and
|
|---|
| 50 | sticky modes:</para>
|
|---|
| 51 |
|
|---|
| 52 | <screen><userinput>chmod a+wt $LFS/sources</userinput></screen>
|
|---|
| 53 |
|
|---|
| 54 | </sect1>
|
|---|
| 55 |
|
|---|
