Added a new solution to the devpts problem - mounting host's devfs system on top of our static /dev

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2886 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Jeremy Utley 2003-09-26 05:58:52 +00:00
parent 0bb2989ee0
commit d725552ce5
2 changed files with 13 additions and 8 deletions

View File

@ -35,5 +35,14 @@ create devices via the <emphasis>mknod</emphasis> program. Please refer to
the man and info pages of <emphasis>mknod</emphasis> if you need more
information.</para>
<para>Also, if earlier in Chapter 6 you were unable to mount the devpts
filesystem because your host uses devfs, we will now mount that devfs
system over top of this new static /dev structure. This poses no problems,
as the device nodes created are still present, they are just hidden by the
new devfs filesystem. Run the following command to mount devfs, if necessary:
</para>
<para><screen><userinput>mount -t devfs devfs /dev</userinput></screen></para>
</sect2>

View File

@ -25,14 +25,10 @@ following command:</para>
<blockquote><screen>filesystem devpts not supported by kernel</screen></blockquote>
<para>It means that your host system does not support devpts. You have two
options at this point. You can either not worry about it, in which case some
of the tests we will run later will fail, or you can use the following command
from a terminal not in chroot to put your host's pts system into your new
LFS's filesystem:</para>
<para><screen><userinput>mount --bind /dev/pts $LFS/dev/pts</userinput></screen>
</para>
<para>This most likely means that your host system uses devfs, and does not
have the necessary support for devpts in the kernel. To work around this
problem, we will place the host's devfs system on top of the new /dev
structure later, in the section where we run the MAKEDEV script.</para>
<para>You might get warning messages from the mount command, such as
these:</para>