aboutsummaryrefslogtreecommitdiffstats
path: root/chapter06/mountproc.xml
blob: 7194b082e0aefac59222889c09fa91ef3b03095e (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
<sect1 id="ch06-proc">
<title>Mounting the proc file system</title>
<?dbhtml filename="proc.html" dir="chapter06"?>

<para>In order for certain programs to function properly, the proc file
system must be available within the chroot environment.
As a file system can be mounted as many times and in as many places
as you like, it's not a problem that the proc file system is already
mounted on your host system -- especially so because proc is a
virtual file system.</para>

<para>The proc file system is mounted under
<filename class="directory">/proc</filename> by running the
following command:</para>

<para><screen><userinput>mount proc /proc -t proc</userinput></screen></para>

<para>You might get warning messages from the mount command, such as
these:</para>

<blockquote><screen>warning: can't open /etc/fstab: No such file or directory
not enough memory</screen></blockquote>

<para>Ignore these, they're just due to the fact that the system
isn't installed completely yet and some files are missing. The mount itself
will be successful and that's all we care about at this point.</para>

<para>The last error (not enough memory) doesn't always show up. It depends
on your system configuration (such as the host system's Glibc version that was
used to compile the mount program with).</para>

</sect1>