Changeset e1c7e32

Timestamp:

02/18/2004 09:59:19 PM (20 years ago)

Author:

Alex Gronenwoud <alex@…>

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_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:

9da62ab

Parents:

b42c2fb

Message:

Cleaning up the PTY business for the test suites.

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

Files:

• chapter06/chapter06.xml (modified) (1 diff)
• chapter06/makedev.xml (modified) (1 diff)
• chapter07/introduction.xml (deleted)

chapter06/chapter06.xml

@@ -100 +100 @@
 
 <para>The most likely cause for this 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
-<command>cat /proc/filesystems</command>. 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 section
-on <xref linkend="ch-system-MAKEDEV"/>. 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
-<xref linkend="ch-system-MAKEDEV"/> section.</para>
+compiled without support for the devpts file system (you can check which file
+systems your kernel supports with <command>cat /proc/filesystems</command>,
+for example). A few PTYs are needed to be able to run the suites for Binutils
+and GCC later on. If your kernel does not support devpts, do not worry, there
+is another way to get them working inside the chroot environment. We'll cover
+this shortly in the <xref linkend="ch-system-MAKEDEV"/> section.</para>
 
 <para>Remember that if for any reason you stop working on your LFS, and start

chapter06/makedev.xml

@@ -66 +66 @@
 <para>If you had success with mounting the devpts file system earlier in <xref
 linkend="ch-system-proc"/>, you can continue with the next section. If you were
-unable to mount devpts, now is the time to try the alternatives. If your kernel
-supports the devfs file system, run the following command to mount
-devfs:</para>
-
-<screen><userinput>mount -t devfs devfs /dev</userinput></screen>
-
-<para>This will mount the devfs file system over the top of the new static
-<filename>/dev</filename> structure. This poses no problems, as the device
-nodes created are still present, they are just hidden by the new devfs file
-system.</para>
-
-<para>If that didn't work either, the only option left is to create a few ptyXX
-and ttyXX device nodes. To do this, open <filename>make_devices</filename> in
-your editor, go to the section "Pseudo-TTY masters" and enable as many ptyXX
-devices as you think you will need (every xterm, ssh connection, telnet
-connection, and the like, uses one of these pseudo terminals). In the
-immediately following section "Pseudo-TTY slaves", enable the corresponding
-ttyXX devices. When you are done, rerun <command>./make_devices</command> from
-inside <filename>/dev</filename> to have it create the new devices.</para>
+unable to mount devpts, you will have to create a few static ptyXX and ttyXX
+device nodes instead. To do this, open <filename>make_devices</filename> in
+your editor, go to the section "Pseudo-TTY masters" and enable a few ptyXX
+devices -- a handful are enough to enable the test suites to run, but if you
+plan to run a kernel without devpts support you will probably need many more
+(every xterm, ssh connection, telnet connection, and the like, uses one of
+these pseudo terminals). In the immediately following section "Pseudo-TTY
+slaves", enable the corresponding ttyXX devices. When you are done, rerun
+<command>./make_devices</command> from inside <filename>/dev</filename> to
+have it create the new devices.</para>
 
 </sect2>