source: chapter06/mountproc.xml@ 470939a7

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 v4_1 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 470939a7 was 2c094d6, checked in by Timothy Bauscher <timothy@…>, 22 years ago

Applied Bill Maltby's grammar patch. Changed $LFS to LFS where appropriate. Internal XML cleanup: removed double spacing where appropriate.

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

  • Property mode set to 100644
File size: 1.1 KB
Line 
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
6system 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 proc file system is already
9mounted on your host system -- especially so because proc is a
10virtual file system.</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>You will most likely get some warning messages from the mount
19command, such as these:</para>
20
21<blockquote><screen>warning: can't open /etc/fstab: No such file or directory
22not enough memory</screen></blockquote>
23
24<para>Ignore these, they're just due to the fact that the system
25isn't installed completely yet and some files are missing. The mount itself
26will be successful and that's all we care about at this point.</para>
27
28</sect1>
29
Note: See TracBrowser for help on using the repository browser.