source: chapter06/mountproc.xml@ d725552

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
Last change on this file since d725552 was d725552, checked in by Jeremy Utley <jeremy@…>, 21 years ago

Added a new solution to the devpts problem - mounting host's devfs system on top of our static /dev

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

  • Property mode set to 100644
File size: 2.2 KB
Line 
1<sect1 id="ch06-proc">
2<title>Mounting the proc and devpts file systems</title>
3<?dbhtml filename="proc.html" dir="chapter06"?>
4
5<para>In order for certain programs to function properly, the proc and devpts
6file systems must be available within the chroot environment.
7As a file system can be mounted as many times and in as many places
8as you like, it's not a problem that the these file systems are already
9mounted on your host system -- especially so because they are virtual
10file systems.</para>
11
12<para>The proc file system is mounted under
13<filename class="directory">/proc</filename> by running the
14following command:</para>
15
16<para><screen><userinput>mount proc /proc -t proc</userinput></screen></para>
17
18<para>The devpts file system is mounted to <filename class="directory">/dev/pts
19</filename> by running:</para>
20
21<para><screen><userinput>mount devpts /dev/pts -t devpts</userinput></screen>
22</para>
23
24<para>Should this command fail with an error to the effect of:</para>
25
26<blockquote><screen>filesystem devpts not supported by kernel</screen></blockquote>
27
28<para>This most likely means that your host system uses devfs, and does not
29have the necessary support for devpts in the kernel. To work around this
30problem, we will place the host's devfs system on top of the new /dev
31structure later, in the section where we run the MAKEDEV script.</para>
32
33<para>You might get warning messages from the mount command, such as
34these:</para>
35
36<blockquote><screen>warning: can't open /etc/fstab: No such file or directory
37not enough memory</screen></blockquote>
38
39<para>Ignore these, they're just due to the fact that the system
40isn't installed completely yet and some files are missing. The mount itself
41will be successful and that's all we care about at this point.</para>
42
43<para>The last error (not enough memory) doesn't always show up. It depends
44on your system configuration (such as the host system's Glibc version that was
45used to compile the mount program with).</para>
46
47<para>Remember, if for any reason you stop working on your LFS, and
48start again later, it's important to check that these filesystems are still
49mounted inside the chroot environment. Otherwise, some programs might
50end up compiled incorrectly.</para>
51
52</sect1>
53
Note: See TracBrowser for help on using the repository browser.