Changeset 342b176 for chapter06/chapter06.xml
- Timestamp:
- 02/09/2004 10:45:54 PM (20 years ago)
- 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:
- 418e6cc
- Parents:
- c76accc
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter06/chapter06.xml
rc76accc r342b176 61 61 </sect1> 62 62 63 &c6-mountproc; 63 64 <sect1 id="ch-system-proc"> 65 <title>Mounting the proc and devpts file systems</title> 66 <?dbhtml filename="proc.html" dir="chapter06"?> 67 68 <para>In order for certain programs to function properly, the 69 <emphasis>proc</emphasis> and <emphasis>devpts</emphasis> file systems must be 70 available within the chroot environment. The proc file system is the process 71 information pseudo file system through which the kernel provides information 72 about the status of the system. And the devpts file system is nowadays the most 73 common way pseudo terminals (PTYs) are implemented. Since kernel version 2.4, a 74 file system can be mounted as many times and in as many places as you like, 75 thus it's not a problem that these file systems are already mounted on your 76 host system, especially so because they are virtual file systems.</para> 77 78 <para>First become <emphasis>root</emphasis>, as only <emphasis>root</emphasis> 79 can mount file systems in unusual places. Then check again that the LFS 80 environment variable is set correctly by running <userinput>echo 81 $LFS</userinput> and making sure it shows the path to your LFS partition's 82 mount point, which is <filename class="directory">/mnt/lfs</filename> if you 83 followed our example.</para> 84 85 <para>Now make the mount points for these filesystems:</para> 86 87 <screen><userinput>mkdir -p $LFS/{proc,dev/pts}</userinput></screen> 88 89 <para>Mount the <emphasis>proc</emphasis> file system with:</para> 90 91 <screen><userinput>mount proc $LFS/proc -t proc</userinput></screen> 92 93 <para>And mount the <emphasis>devpts</emphasis> file system with:</para> 94 95 <screen><userinput>mount devpts $LFS/dev/pts -t devpts</userinput></screen> 96 97 <para>This last command might fail with an error like:</para> 98 99 <blockquote><screen>filesystem devpts not supported by kernel</screen></blockquote> 100 101 <para>The most likely cause for this is that your host system's kernel was 102 compiled without support for the devpts file system. You can check which file 103 systems your kernel supports by peeking into its internals with 104 <command>cat /proc/filesystems</command>. If a file system type named 105 <emphasis>devfs</emphasis> is listed there, then we'll be able to work around 106 the problem by mounting the host's devfs file system on top of the new 107 <filename>/dev</filename> structure which we'll create later on in the section 108 on <xref linkend="ch-system-MAKEDEV"/>. If devfs was not listed, do not worry 109 because there is yet a third way to get PTYs working inside the chroot 110 environment. We'll cover this shortly in the aforementioned 111 <xref linkend="ch-system-MAKEDEV"/> section.</para> 112 113 <para>Remember that if for any reason you stop working on your LFS, and start 114 again later, it's important to check that these file systems are mounted again 115 before entering the chroot environment, otherwise problems could occur.</para> 116 117 </sect1> 118 64 119 65 120 <sect1 id="ch-system-chroot">
Note:
See TracChangeset
for help on using the changeset viewer.