gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-03-06 06:14:47 +00:00
Code Issues Packages Projects Releases Wiki Activity

Oops. Forgot to change the actual mount commands.

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3227 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Alex Gronenwoud 2004-02-05 22:16:21 +00:00
parent dcff0464e8
commit 91e8861fd1
2 changed files with 22 additions and 24 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
chapter06/chapter06.xml
View File

@ -67,15 +67,9 @@ with a series of short descriptions of these.</para>
<?dbhtml filename="chroot.html" dir="chapter06"?>
<para>It is time to enter the chroot environment in order to begin building
and installing your final LFS system.</para>
<para>First check, just like earlier, that the LFS environment variable is set
up properly by running <userinput>echo $LFS</userinput> and making sure it
shows the path to your LFS partition's mount point, which is
<filename class="directory">/mnt/lfs</filename> if you followed our example.</para>
<para>As <emphasis>root</emphasis>, run the following command to enter the
chroot environment:</para>
and installing your final LFS system. Still as <emphasis>root</emphasis> run
the following command to enter the small world that is, at the moment,
populated with only the temporary tools:</para>
<screen><userinput>chroot $LFS /tools/bin/env -i \
&nbsp;&nbsp;&nbsp;&nbsp;HOME=/root TERM=$TERM PS1='\u:\w\$ ' \

34
chapter06/mountproc.xml
View File

@ -9,31 +9,35 @@ 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,
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>First make the mount points for these filesystems:</para>
<screen><userinput>mkdir -p $LFS/{proc,dev/pts}</userinput></screen>
<para>Now become <emphasis>root</emphasis>, since only
<emphasis>root</emphasis> can mount file systems in unusual places. Then
check again that the LFS environment variable is set correctly by running
<userinput>echo $LFS</userinput> and making sure it shows the path to your LFS
partition's mount point, which is <filename
class="directory">/mnt/lfs</filename> if you followed our example.</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. Mount it on <filename class="directory">/proc</filename>
with:</para>
status of the system. Mount it with:</para>
<screen><userinput>mount proc /proc -t proc</userinput></screen>
<screen><userinput>mount proc $LFS/proc -t proc</userinput></screen>
<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>
<para>The <emphasis>devpts</emphasis> file system is now the most common way
for pseudo terminals (PTYs) to be implemented. Mount it with:</para>
<para>The devpts file system is mounted on
<filename class="directory">/dev/pts</filename> by running:</para>
<screen><userinput>mount devpts $LFS/dev/pts -t devpts</userinput></screen>
<screen><userinput>mount devpts /dev/pts -t devpts</userinput></screen>
<para>Should this command fail with an error to the effect of:</para>
<para>This last command might fail with an error to the effect of:</para>
<blockquote><screen>filesystem devpts not supported by kernel</screen></blockquote>
<para>The most likely cause is that your host system's kernel was compiled
without support for the devpts file system. You can check which file systems
your kernel supports by peeking into its internals with a command such as
<para>The most likely cause for this is that your host system's kernel was
compiled without support for the devpts file system. You can check which file
systems your kernel supports by peeking into its internals with
<command>cat /proc/filesystems</command>. If a file system type named
<emphasis>devfs</emphasis> is listed there, then we'll be able to work around
the problem by mounting the host's devfs file system on top of the new