introduction.xml 2.8 KB

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