mountproc.xml 2.7 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455
  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. The proc file system is the process
  7. information pseudo file system through which the kernel provides information
  8. about the status of the system. And the devpts file system is nowadays the most
  9. common way pseudo terminals (PTYs) are implemented. Since kernel version 2.4, a
  10. file system can be mounted as many times and in as many places as you like,
  11. thus it's not a problem that these file systems are already mounted on your
  12. host system, especially so because they are virtual file systems.</para>
  13. <para>First become <emphasis>root</emphasis>, as only <emphasis>root</emphasis>
  14. can mount file systems in unusual places. Then check again that the LFS
  15. environment variable is set correctly by running <userinput>echo
  16. $LFS</userinput> and making sure it shows the path to your LFS partition's
  17. mount point, which is <filename class="directory">/mnt/lfs</filename> if you
  18. followed our example.</para>
  19. <para>Now make the mount points for these filesystems:</para>
  20. <screen><userinput>mkdir -p $LFS/{proc,dev/pts}</userinput></screen>
  21. <para>Mount the <emphasis>proc</emphasis> file system with:</para>
  22. <screen><userinput>mount proc $LFS/proc -t proc</userinput></screen>
  23. <para>And mount the <emphasis>devpts</emphasis> file system with:</para>
  24. <screen><userinput>mount devpts $LFS/dev/pts -t devpts</userinput></screen>
  25. <para>This last command might fail with an error like:</para>
  26. <blockquote><screen>filesystem devpts not supported by kernel</screen></blockquote>
  27. <para>The most likely cause for this is that your host system's kernel was
  28. compiled without support for the devpts file system. You can check which file
  29. systems your kernel supports by peeking into its internals with
  30. <command>cat /proc/filesystems</command>. If a file system type named
  31. <emphasis>devfs</emphasis> is listed there, then we'll be able to work around
  32. the problem by mounting the host's devfs file system on top of the new
  33. <filename>/dev</filename> structure which we'll create later on in the section
  34. on <xref linkend="ch-system-MAKEDEV"/>. If devfs was not listed, do not worry
  35. because there is yet a third way to get PTYs working inside the chroot
  36. environment. We'll cover this shortly in the aforementioned
  37. <xref linkend="ch-system-MAKEDEV"/> section.</para>
  38. <para>Remember that if for any reason you stop working on your LFS, and start
  39. again later, it's important to check that these file systems are mounted again
  40. before entering the chroot environment, otherwise problems could occur.</para>
  41. </sect1>