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
|
---|
6 | file systems must be available within the chroot environment.
|
---|
7 | As a file system can be mounted as many times and in as many places
|
---|
8 | as you like, it's not a problem that the these file systems are already
|
---|
9 | mounted on your host system -- especially so because they are virtual
|
---|
10 | file systems.</para>
|
---|
11 |
|
---|
12 | <para>The proc file system is mounted under
|
---|
13 | <filename class="directory">/proc</filename> by running the
|
---|
14 | following 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>It means that your host system does not support devpts. You have two
|
---|
29 | options at this point. You can either not worry about it, in which case some
|
---|
30 | of the tests we will run later will fail, or you can use the following command
|
---|
31 | from a terminal not in chroot to put your host's pts system into your new
|
---|
32 | LFS's filesystem:</para>
|
---|
33 |
|
---|
34 | <para><screen><userinput>mount --bind /dev/pts $LFS/dev/pts</userinput></screen>
|
---|
35 | </para>
|
---|
36 |
|
---|
37 | <para>You might get warning messages from the mount command, such as
|
---|
38 | these:</para>
|
---|
39 |
|
---|
40 | <blockquote><screen>warning: can't open /etc/fstab: No such file or directory
|
---|
41 | not enough memory</screen></blockquote>
|
---|
42 |
|
---|
43 | <para>Ignore these, they're just due to the fact that the system
|
---|
44 | isn't installed completely yet and some files are missing. The mount itself
|
---|
45 | will be successful and that's all we care about at this point.</para>
|
---|
46 |
|
---|
47 | <para>The last error (not enough memory) doesn't always show up. It depends
|
---|
48 | on your system configuration (such as the host system's Glibc version that was
|
---|
49 | used to compile the mount program with).</para>
|
---|
50 |
|
---|
51 | <para>Remember, if for any reason you stop working on your LFS, and
|
---|
52 | start again later, it's important to check that these filesystems are still
|
---|
53 | mounted inside the chroot environment. Otherwise, some programs might
|
---|
54 | end up compiled incorrectly.</para>
|
---|
55 |
|
---|
56 | </sect1>
|
---|
57 |
|
---|