Changeset 5c0b6e7

Timestamp:

09/05/2003 02:06:21 AM (21 years ago)

Author:

Jeremy Utley <jeremy@…>

Branches:

10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v5_0, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc

Children:

c4603f5

Parents:

1a6a5c3

Message:

Added mounting the devpts filesystem into the new LFS partition

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2735 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

Files:

• chapter01/changelog.xml (modified) (1 diff)
• chapter06/mountproc.xml (modified) (3 diffs)

chapter01/changelog.xml

@@ -84 +84 @@
 
 <listitem><para>September 4th, 2003 [jeremy]: Chapter 6 - Mounting Proc:
+Added mounting the devpts filesystem into chroot here.  Closes bug 533.</para>
+</listitem>
+
+<listitem><para>September 4th, 2003 [jeremy]: Chapter 6 - Mounting Proc:
 Added a warning at the end regarding checking that proc is still mounted
 if you stop and restart the lfs process.</para></listitem>

chapter06/mountproc.xml

@@ -1 +1 @@
 <sect1 id="ch06-proc">
-<title>Mounting the proc file system</title>
+<title>Mounting the proc and devpts file systems</title>
 <?dbhtml filename="proc.html" dir="chapter06"?>
 
-<para>In order for certain programs to function properly, the proc file
-system must be available within the chroot environment.
+<para>In order for certain programs to function properly, the proc and devpts
+file systems must be available within the chroot environment.
 As a file system can be mounted as many times and in as many places
-as you like, it's not a problem that the proc file system is already
-mounted on your host system -- especially so because proc is a
-virtual file system.</para>
+as you like, it's not a problem that the these file systems are already
+mounted on your host system -- especially so because they are virtual 
+file systems.</para>
 
 <para>The proc file system is mounted under
@@ -15 +15 @@
 
 <para><screen><userinput>mount proc /proc -t proc</userinput></screen></para>
+
+<para>The devpts file system is mounted to <filename class="directory">/dev/pts
+</filename> by running:</para>
+
+<para><screen><userinput>mount devpts /dev/pts -t devpts</userinput></screen>
+</para>
+
+<para>Should this command fail with an error to the effect of:</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>You might get warning messages from the mount command, such as
@@ -31 +50 @@
 
 <para>Remember, if for any reason you stop working on your LFS, and
-start again later, it's important to check that the proc filesystem is still
+start again later, it's important to check that these filesystems are still
 mounted inside the chroot enviornment. Otherwise, some programs might
 end up compiled incorrectly.</para>