Ignore:
Timestamp:
02/07/2004 10:48:13 AM (21 years ago)
Author:
Alex Gronenwoud <alex@…>
Branches:
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, 12.2, 12.2-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, 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/loongarch-12.2, xry111/mips64el, xry111/multilib, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
Children:
c21999c6
Parents:
74798ca
Message:

Fixing several small things.

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

File:
1 edited

Legend:

Unmodified
Added
Removed

  • chapter06/mountproc.xml

    r74798ca r5b0dd3a  
    55<para>In order for certain programs to function properly, the
    66<emphasis>proc</emphasis> and <emphasis>devpts</emphasis> file systems must be
    7 available within the chroot environment. Since kernel version 2.4 a file system
    8 can be mounted as many times and in as many places as you like, thus it's not a
    9 problem that these file systems are already mounted on your host system,
    10 especially so because they are virtual file systems.</para>
     7available within the chroot environment. The proc file system is the process
     8information pseudo file system through which the kernel provides information
     9about the status of the system. And the devpts file system is nowadays the most
     10common way pseudo terminals (PTYs) are implemented. Since kernel version 2.4, a
     11file system can be mounted as many times and in as many places as you like,
     12thus it's not a problem that these file systems are already mounted on your
     13host system, especially so because they are virtual file systems.</para>
    1114
    12 <para>First make the mount points for these filesystems:</para>
     15<para>First become <emphasis>root</emphasis>, as only <emphasis>root</emphasis>
     16can mount file systems in unusual places. Then check again that the LFS
     17environment variable is set correctly by running <userinput>echo
     18$LFS</userinput> and making sure it shows the path to your LFS partition's
     19mount point, which is <filename class="directory">/mnt/lfs</filename> if you
     20followed our example.</para>
     21
     22<para>Now make the mount points for these filesystems:</para>
    1323
    1424<screen><userinput>mkdir -p $LFS/{proc,dev/pts}</userinput></screen>
    1525
    16 <para>Now become <emphasis>root</emphasis>, since only
    17 <emphasis>root</emphasis> can mount file systems in unusual places. Then
    18 check again that the LFS environment variable is set correctly by running
    19 <userinput>echo $LFS</userinput> and making sure it shows the path to your LFS
    20 partition's mount point, which is <filename
    21 class="directory">/mnt/lfs</filename> if you followed our example.</para>
    22 
    23 <para>The <emphasis>proc</emphasis> file system is the process information
    24 pseudo file system through which the kernel provides information about the
    25 status of the system. Mount it with:</para>
     26<para>Mount the <emphasis>proc</emphasis> file system with:</para>
    2627
    2728<screen><userinput>mount proc $LFS/proc -t proc</userinput></screen>
    2829
    29 <para>The <emphasis>devpts</emphasis> file system is now the most common way
    30 for pseudo terminals (PTYs) to be implemented. Mount it with:</para>
     30<para>And mount the <emphasis>devpts</emphasis> file system with:</para>
    3131
    3232<screen><userinput>mount devpts $LFS/dev/pts -t devpts</userinput></screen>
    3333
    34 <para>This last command might fail with an error to the effect of:</para>
     34<para>This last command might fail with an error like:</para>
    3535
    3636<blockquote><screen>filesystem devpts not supported by kernel</screen></blockquote>
    … …  
    4848<xref linkend="ch-system-MAKEDEV"/> section.</para>
    4949
    50 <para>Remember, if for any reason you stop working on your LFS, and start again
    51 later, it's important to check that these file systems are mounted again before
    52 entering the chroot environment, otherwise some problems could occur.</para>
     50<para>Remember that if for any reason you stop working on your LFS, and start
     51again later, it's important to check that these file systems are mounted again
     52before entering the chroot environment, otherwise problems could occur.</para>
    5353
    5454</sect1>
Note: See TracChangeset for help on using the changeset viewer.