1 | <sect1 id="ch06-proc">
|
---|
2 | <title>Mounting the proc file system</title>
|
---|
3 | <?dbhtml filename="proc.html" dir="chapter06"?>
|
---|
4 |
|
---|
5 | <para>In order for certain programs to function properly, the proc file
|
---|
6 | system 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 proc file system is already
|
---|
9 | mounted on your host system -- especially so because proc is a
|
---|
10 | virtual file system.</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>You might get warning messages from the mount command, such as
|
---|
19 | these:</para>
|
---|
20 |
|
---|
21 | <blockquote><screen>warning: can't open /etc/fstab: No such file or directory
|
---|
22 | not enough memory</screen></blockquote>
|
---|
23 |
|
---|
24 | <para>Ignore these, they're just due to the fact that the system
|
---|
25 | isn't installed completely yet and some files are missing. The mount itself
|
---|
26 | will be successful and that's all we care about at this point.</para>
|
---|
27 |
|
---|
28 | <para>The last error (not enough memory) doesn't always show up. It depends
|
---|
29 | on your system configuration (such as the host system's Glibc version that was
|
---|
30 | used to compile the mount program with).</para>
|
---|
31 |
|
---|
32 | <para>Remember, if for any reason you stop working on your LFS, and
|
---|
33 | start again later, it's important to check that the proc filesystem is still
|
---|
34 | mounted inside the chroot enviornment. Otherwise, some programs might
|
---|
35 | end up compiled incorrectly.</para>
|
---|
36 |
|
---|
37 | </sect1>
|
---|
38 |
|
---|