|
@@ -44,14 +44,13 @@ now the most common way for pseudo terminals (PTYs) to be implemented.</para>
|
|
|
<para>The most likely cause is that your host system's kernel was compiled
|
|
|
without support for the devpts file system. You can check which file systems
|
|
|
your kernel supports by peeking into its internals with a command such as
|
|
|
-<userinput>cat /proc/filesystems</userinput>. If for some reason devpts is
|
|
|
-listed there but the mount still doesn't work, check instead for a different
|
|
|
-file system variety called <emphasis>devfs</emphasis>. If devfs is listed then
|
|
|
-we'll be able to work around the problem by mounting the host's devfs file
|
|
|
-system on top of the new <filename>/dev</filename> structure which we'll create
|
|
|
-later on in the "Creating devices (Makedev)" section. If devfs was not listed,
|
|
|
-do not worry because there is yet a third way to get PTYs working inside the
|
|
|
-chroot environment. We'll cover this shortly in the aforementioned Makedev
|
|
|
+<userinput>cat /proc/filesystems</userinput>. If a file system type named
|
|
|
+<emphasis>devfs</emphasis> is listed there, then we'll be able to work around
|
|
|
+the problem by mounting the host's devfs file system on top of the new
|
|
|
+<filename>/dev</filename> structure which we'll create later on in the
|
|
|
+"Creating devices (Makedev)" section. If devfs was not listed, do not worry
|
|
|
+because there is yet a third way to get PTYs working inside the chroot
|
|
|
+environment. We'll cover this shortly in the aforementioned Makedev
|
|
|
section.</para>
|
|
|
|
|
|
<para>Remember, if for any reason you stop working on your LFS, and start again
|