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