From e1c7e32ae38c9e45821d8df8fac70cecf812db38 Mon Sep 17 00:00:00 2001 From: Alex Gronenwoud Date: Wed, 18 Feb 2004 21:59:19 +0000 Subject: 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 --- chapter06/chapter06.xml | 16 ++++++---------- chapter06/makedev.xml | 29 ++++++++++------------------- 2 files changed, 16 insertions(+), 29 deletions(-) (limited to 'chapter06') diff --git a/chapter06/chapter06.xml b/chapter06/chapter06.xml index eff1c295b..4a168fac6 100644 --- a/chapter06/chapter06.xml +++ b/chapter06/chapter06.xml @@ -99,16 +99,12 @@ followed our example.
filesystem devpts not supported by kernel
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 -cat /proc/filesystems. If a file system type named -devfs 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 -/dev structure which we'll create later on in the section -on . 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 - section. +compiled without support for the devpts file system (you can check which file +systems your kernel supports with cat /proc/filesystems, +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 section. Remember that if for any reason you stop working on your LFS, and start again later, it's important to check that these file systems are mounted again diff --git a/chapter06/makedev.xml b/chapter06/makedev.xml index 271ebef80..a83f07885 100644 --- a/chapter06/makedev.xml +++ b/chapter06/makedev.xml @@ -65,25 +65,16 @@ you are satisfied, run the script to create the device files: If you had success with mounting the devpts file system earlier in , 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: - -mount -t devfs devfs /dev - -This will mount the devfs file system over the top of the new static -/dev structure. This poses no problems, as the device -nodes created are still present, they are just hidden by the new devfs file -system. - -If that didn't work either, the only option left is to create a few ptyXX -and ttyXX device nodes. To do this, open make_devices 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 ./make_devices from -inside /dev to have it create the new devices. +unable to mount devpts, you will have to create a few static ptyXX and ttyXX +device nodes instead. To do this, open make_devices 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 +./make_devices from inside /dev to +have it create the new devices. -- cgit v1.2.3-54-g00ecf