introduction.xml 3.1 KB

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