mountproc.xml 2.8 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061
  1. <sect1 id="ch-system-proc">
  2. <title>Mounting the proc and devpts file systems</title>
  3. <?dbhtml filename="proc.html" dir="chapter06"?>
  4. <para>In order for certain programs to function properly, the
  5. <emphasis>proc</emphasis> and <emphasis>devpts</emphasis> file systems must be
  6. available within the chroot environment. A file system can be mounted as many
  7. times and in as many places as you like, thus it's not a problem that these
  8. file systems are already mounted on your host system -- especially so because
  9. they are virtual file systems.</para>
  10. <para>The <emphasis>proc</emphasis> file system is the process information
  11. pseudo file system through which the kernel provides information about the
  12. status of the system.</para>
  13. <para>The proc file system is mounted on
  14. <filename class="directory">/proc</filename> by running the following
  15. command:</para>
  16. <screen><userinput>mount proc /proc -t proc</userinput></screen>
  17. <para>You might get warning messages from the mount command, such as
  18. these:</para>
  19. <blockquote><screen>warning: can't open /etc/fstab: No such file or directory
  20. not enough memory</screen></blockquote>
  21. <para>Ignore these, they're just due to the fact that the system
  22. isn't installed completely yet and some files are missing. The mount itself
  23. will be successful and that's all we care about at this point.</para>
  24. <para>The <emphasis>devpts</emphasis> file system was mentioned earlier and is
  25. now the most common way for pseudo terminals (PTYs) to be implemented.</para>
  26. <para>The devpts file system is mounted on
  27. <filename class="directory">/dev/pts</filename> by running:</para>
  28. <screen><userinput>mount devpts /dev/pts -t devpts</userinput></screen>
  29. <para>Should this command fail with an error to the effect of:</para>
  30. <blockquote><screen>filesystem devpts not supported by kernel</screen></blockquote>
  31. <para>The most likely cause is that your host system's kernel was compiled
  32. without support for the devpts file system. You can check which file systems
  33. your kernel supports by peeking into its internals with a command such as
  34. <userinput>cat /proc/filesystems</userinput>. If a file system type named
  35. <emphasis>devfs</emphasis> is listed there, then we'll be able to work around
  36. the problem by mounting the host's devfs file system on top of the new
  37. <filename>/dev</filename> structure which we'll create later on in the section
  38. on <xref linkend="ch-system-MAKEDEV"/>. If devfs was not listed, do not worry
  39. because there is yet a third way to get PTYs working inside the chroot
  40. environment. We'll cover this shortly in the aforementioned
  41. <xref linkend="ch-system-MAKEDEV"/> section.</para>
  42. <para>Remember, if for any reason you stop working on your LFS, and start again
  43. later, it's important to check that these file systems are still mounted inside
  44. the chroot environment, otherwise problems are likely to occur.</para>
  45. </sect1>