introduction.xml 2.4 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849
  1. <sect1 id="ch05-introduction">
  2. <title>Introduction</title>
  3. <?dbhtml filename="introduction.html" dir="chapter05"?>
  4. <para>In the following chapters we will install all the software that belongs
  5. to a basic Linux system. After you're done with this and the next chapter,
  6. you'll have a fully working Linux system. The remaining chapters deal
  7. with creating the boot scripts, making the LFS system bootable and
  8. setting up basic networking.</para>
  9. <para>The software in this chapter will be linked statically and will be
  10. reinstalled in the next chapter and linked dynamically. The
  11. reason for the static version first is that there is a chance that our
  12. normal Linux system and the LFS system aren't using the same C
  13. Library versions. If the programs in the first part are linked against
  14. an older C library version, those programs might not work well on the
  15. LFS system. Another reason is to resolve circular dependencies. An
  16. example of such a dependency is that you need a compiler to install a
  17. compiler, and you're going to need a shell to install a shell and that
  18. compiler.</para>
  19. <para>All the files from this chapter will be installed under the <filename
  20. class="directory">$LFS/static</filename> directory. By doing it this way,
  21. we keep the installation from this chapter separate from the final
  22. installation in the next chapter. Everything done here is only temporarily
  23. so we don't want it to pollute the to-be LFS system.</para>
  24. <para>The key to learning what makes Linux tick is to know exactly what packages
  25. are used for and why a user or the system needs them. Descriptions
  26. of the package content are provided after the Installation subsection of each
  27. package and in Appendix A as well.</para>
  28. <para>During the installation of various packages, you will more than likely see
  29. all kinds of compiler warnings scrolling by on the screen. These are
  30. normal and can be safely ignored. They are just that, warnings (mostly
  31. about improper use of the C or C++ syntax, but not illegal use. It's just
  32. that, often, C standards changed and packages still use the old standard
  33. which is not a problem).</para>
  34. <para>Before we start, make sure the LFS environment variable is set up
  35. properly if you decided to make use of it. Run the following:</para>
  36. <para><screen><userinput>echo $LFS</userinput></screen></para>
  37. <para>Check to make sure the output contains the correct directory to the LFS
  38. partition's mount point (/mnt/lfs for example).</para>
  39. </sect1>