kernfs: Use a separate devpts filesystem for chroot environment

IIRC we switched from separate devpts to bind mount, and matched the UID
of tester with the host UID owning the TTY, to satisify the Bash test
suite.  But now we are always using UID 101 for tester and expect to
spawn a PTY for Bash test suite (so when building LFS in a TTY owned by
the root user of the host tester won't be UID 0).  Thus we can switch
back to a separate devpts mount which is cleaner and safer.

And we are already using a separate devpts mount in Chapter 11.
This commit is contained in:
Xi Ruoyao 2024-02-06 00:15:33 +08:00
parent 1541b7c29f
commit ce11e97f01
No known key found for this signature in database
GPG Key ID: ACAAD20E19E710E3

View File

@ -63,11 +63,14 @@
<para>Now mount the remaining virtual kernel file systems:</para> <para>Now mount the remaining virtual kernel file systems:</para>
<screen><userinput>mount -v --bind /dev/pts $LFS/dev/pts <!-- Do not put any option after $LFS/${mountpoint} or jhalfs cannot
handle it! -->
<screen><userinput>mount -vt devpts devpts -o gid=5,mode=0620 $LFS/dev/pts
mount -vt proc proc $LFS/proc mount -vt proc proc $LFS/proc
mount -vt sysfs sysfs $LFS/sys mount -vt sysfs sysfs $LFS/sys
mount -vt tmpfs tmpfs $LFS/run</userinput></screen> mount -vt tmpfs tmpfs $LFS/run</userinput></screen>
<!--
<variablelist> <variablelist>
<title>The meaning of the mount options for devpts:</title> <title>The meaning of the mount options for devpts:</title>
@ -95,7 +98,7 @@ mount -vt tmpfs tmpfs $LFS/run</userinput></screen>
</varlistentry> </varlistentry>
</variablelist> </variablelist>
-->
<para>In some host systems, <filename>/dev/shm</filename> is a <para>In some host systems, <filename>/dev/shm</filename> is a
symbolic link to a directory, typically symbolic link to a directory, typically
<filename class="directory">/run/shm</filename>. <filename class="directory">/run/shm</filename>.