introduction.xml 1.7 KB

12345678910111213141516171819202122232425262728293031323334353637
  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="ch-tools-introduction-chroot">
  8. <?dbhtml filename="introduction.html"?>
  9. <title>Introduction</title>
  10. <para>This chapter shows how to build the last missing bits of the
  11. temporary system: first, the tools needed by the build machinery of
  12. various packages, then three packages needed to run tests.
  13. Now that all circular dependencies have been resolved,
  14. we can use a <quote>chroot</quote> environment, completely isolated
  15. from the computer used for the build, except for the running kernel.</para>
  16. <para>For proper operation of the isolated environment, some communication
  17. with the running kernel must be established. This is done through the
  18. so-called <emphasis>Virtual Kernel File Systems</emphasis>, which must be
  19. mounted when entering the chroot environment. You may want to check
  20. that they are mounted by issuing <command>ls $LFS/dev</command>,
  21. <command>ls $LFS/proc</command>, or <command>ls $LFS/sys</command>.
  22. Note that mounting the virtual kernel file systems must be done
  23. <emphasis>each time you want to enter the chroot
  24. environment</emphasis>.</para>
  25. <para>Until <xref linkend="ch-tools-chroot"/>, the commands must be
  26. run as <systemitem class="username">root</systemitem>, with the
  27. <envar>LFS</envar> variable set. After entering chroot, all commands
  28. are run as root, fortunately without access to the OS of the computer
  29. you build LFS on. Be careful anyway, as it is easy to destroy the whole
  30. LFS system with badly formed commands.</para>
  31. </sect1>