source: chapter06/mountproc.xml@ 74798ca

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 12.2 12.2-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/loongarch-12.2 xry111/mips64el xry111/multilib xry111/pip3 xry111/rust-wip-20221008 xry111/update-glibc
Last change on this file since 74798ca was 91e8861, checked in by Alex Gronenwoud <alex@…>, 21 years ago

Oops. Forgot to change the actual mount commands.

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

  • Property mode set to 100644
File size: 2.7 KB
Line 
1<sect1 id="ch-system-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
6<emphasis>proc</emphasis> and <emphasis>devpts</emphasis> file systems must be
7available within the chroot environment. Since kernel version 2.4 a file system
8can be mounted as many times and in as many places as you like, thus it's not a
9problem that these file systems are already mounted on your host system,
10especially so because they are virtual file systems.</para>
11
12<para>First make the mount points for these filesystems:</para>
13
14<screen><userinput>mkdir -p $LFS/{proc,dev/pts}</userinput></screen>
15
16<para>Now become <emphasis>root</emphasis>, since only
17<emphasis>root</emphasis> can mount file systems in unusual places. Then
18check again that the LFS environment variable is set correctly by running
19<userinput>echo $LFS</userinput> and making sure it shows the path to your LFS
20partition's mount point, which is <filename
21class="directory">/mnt/lfs</filename> if you followed our example.</para>
22
23<para>The <emphasis>proc</emphasis> file system is the process information
24pseudo file system through which the kernel provides information about the
25status of the system. Mount it with:</para>
26
27<screen><userinput>mount proc $LFS/proc -t proc</userinput></screen>
28
29<para>The <emphasis>devpts</emphasis> file system is now the most common way
30for pseudo terminals (PTYs) to be implemented. Mount it with:</para>
31
32<screen><userinput>mount devpts $LFS/dev/pts -t devpts</userinput></screen>
33
34<para>This last command might fail with an error to the effect of:</para>
35
36<blockquote><screen>filesystem devpts not supported by kernel</screen></blockquote>
37
38<para>The most likely cause for this is that your host system's kernel was
39compiled without support for the devpts file system. You can check which file
40systems your kernel supports by peeking into its internals with
41<command>cat /proc/filesystems</command>. If a file system type named
42<emphasis>devfs</emphasis> is listed there, then we'll be able to work around
43the problem by mounting the host's devfs file system on top of the new
44<filename>/dev</filename> structure which we'll create later on in the section
45on <xref linkend="ch-system-MAKEDEV"/>. If devfs was not listed, do not worry
46because there is yet a third way to get PTYs working inside the chroot
47environment. We'll cover this shortly in the aforementioned
48<xref linkend="ch-system-MAKEDEV"/> section.</para>
49
50<para>Remember, if for any reason you stop working on your LFS, and start again
51later, it's important to check that these file systems are mounted again before
52entering the chroot environment, otherwise some problems could occur.</para>
53
54</sect1>
55
Note: See TracBrowser for help on using the repository browser.