introduction.xml 2.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354
  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. <para>This chapter includes a list of packages that need to be
  10. downloaded for building a basic Linux system. The listed version numbers
  11. correspond to versions of the software that are known to work, and
  12. this book is based on their use. We highly recommend not using newer
  13. versions because the build commands for one version may not work with
  14. a newer version. The newest package versions may also have problems
  15. that work-arounds have not been developed for yet.</para>
  16. <para>All the URLs, when possible, refer to the package's information
  17. page at <ulink url="http://www.freshmeat.net/"/>. The Freshmeat pages
  18. provide easy access to official download sites, as well as project
  19. websites, mailing lists, FAQ, changelogs, and more.</para>
  20. <para>Download locations may not always be accessible. If a download
  21. location has changed since this book was published, Google (<ulink
  22. url="http://www.google.com"/>) provides a useful search engine for
  23. most packages. If this search is unsuccessful, try one of the
  24. alternate means of downloading discussed at <ulink
  25. url="&lfs-root;lfs/packages.html"/>.</para>
  26. <para>Downloaded packages and patches will need to be stored somewhere
  27. that is conveniently available throughout the entire build. A working
  28. directory is also required to unpack the sources and build them.
  29. <filename class="directory">$LFS/sources</filename> can be used both
  30. as the place to store the tarballs and patches and as a working
  31. directory. By using this directory, the required elements will be
  32. located on the LFS partition and will be available during all stages
  33. of the building process.</para>
  34. <para>To create this directory, execute, as user
  35. <emphasis>root</emphasis>, the following command before starting the
  36. download session:</para>
  37. <screen><userinput>mkdir $LFS/sources</userinput></screen>
  38. <para>Make this directory writable and sticky. <quote>Sticky</quote>
  39. means that even if multiple users have write permission on a
  40. directory, only the owner of a file can delete the file within a
  41. sticky directory. The following command will enable the write and
  42. sticky modes:</para>
  43. <screen><userinput>chmod a+wt $LFS/sources</userinput></screen>
  44. </sect1>