From fe5b13b40b50e7be2b16cbd477988e7828fcd8ca Mon Sep 17 00:00:00 2001
From: Alex Gronenwoud <alex@linuxfromscratch.org>
Date: Wed, 4 Feb 2004 22:22:49 +0000
Subject: Moving Mounting proc to before Chroot, dropping Util-linux, adding an
 arch script to Perl.

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3220 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
---
 chapter06/mountproc.xml | 26 ++++++++------------------
 1 file changed, 8 insertions(+), 18 deletions(-)

(limited to 'chapter06/mountproc.xml')

diff --git a/chapter06/mountproc.xml b/chapter06/mountproc.xml
index e15c3546e..d1d91d9c1 100644
--- a/chapter06/mountproc.xml
+++ b/chapter06/mountproc.xml
@@ -6,29 +6,19 @@
 <emphasis>proc</emphasis> and <emphasis>devpts</emphasis> file systems must be
 available within the chroot environment. Since kernel version 2.4 a file system
 can be mounted as many times and in as many places as you like, thus it's not a
-problem that these file systems are already mounted on your host system --
+problem that these file systems are already mounted on your host system,
 especially so because they are virtual file systems.</para>
 
+<para>First you need to become <emphasis>root</emphasis>, since probably only
+<emphasis>root</emphasis> can mount these file systems.</para>
+
 <para>The <emphasis>proc</emphasis> file system is the process information
 pseudo file system through which the kernel provides information about the
-status of the system.</para>
-
-<para>The proc file system is mounted on
-<filename class="directory">/proc</filename> by running the following
-command:</para>
+status of the system. Mount it on <filename class="directory">/proc</filename>
+with:</para>
 
 <screen><userinput>mount proc /proc -t proc</userinput></screen>
 
-<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 <emphasis>devpts</emphasis> file system was mentioned earlier and is
 now the most common way for pseudo terminals (PTYs) to be implemented.</para>
 
@@ -54,8 +44,8 @@ environment. We'll cover this shortly in the aforementioned
 <xref linkend="ch-system-MAKEDEV"/> section.</para>
 
 <para>Remember, if for any reason you stop working on your LFS, and start again
-later, it's important to check that these file systems are still mounted inside
-the chroot environment, otherwise problems are likely to occur.</para>
+later, it's important to check that these file systems are mounted again before
+entering the chroot environment, otherwise some problems could occur.</para>
 
 </sect1>
 
-- 
cgit v1.2.3-54-g00ecf