Changeset 91e8861


Ignore:
Timestamp:
02/05/2004 10:16:21 PM (20 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, 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/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
Children:
2309b72
Parents:
dcff046
Message:

Oops. Forgot to change the actual mount commands.

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

Location:
chapter06
Files:
2 edited

Legend:

Unmodified
Added
Removed

  • chapter06/chapter06.xml

    rdcff046 r91e8861  
    6868
    6969<para>It is time to enter the chroot environment in order to begin building
    70 and installing your final LFS system.</para>
    71 
    72 <para>First check, just like earlier, that the LFS environment variable is set
    73 up properly by running <userinput>echo $LFS</userinput> and making sure it
    74 shows the path to your LFS partition's mount point, which is
    75 <filename class="directory">/mnt/lfs</filename> if you followed our example.</para>
    76 
    77 <para>As <emphasis>root</emphasis>, run the following command to enter the
    78 chroot environment:</para>
     70and installing your final LFS system. Still as <emphasis>root</emphasis> run
     71the following command to enter the small world that is, at the moment,
     72populated with only the temporary tools:</para>
    7973
    8074<screen><userinput>chroot $LFS /tools/bin/env -i \

  • chapter06/mountproc.xml

    rdcff046 r91e8861  
    1010especially so because they are virtual file systems.</para>
    1111
    12 <para>First you need to become <emphasis>root</emphasis>, since probably only
    13 <emphasis>root</emphasis> can mount these file systems.</para>
     12<para>First make the mount points for these filesystems:</para>
     13
     14<screen><userinput>mkdir -p $LFS/{proc,dev/pts}</userinput></screen>
     15
     16<para>Now become <emphasis>root</emphasis>, since only
     17<emphasis>root</emphasis> can mount file systems in unusual places. Then
     18check 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
     20partition's mount point, which is <filename
     21class="directory">/mnt/lfs</filename> if you followed our example.</para>
    1422
    1523<para>The <emphasis>proc</emphasis> file system is the process information
    1624pseudo file system through which the kernel provides information about the
    17 status of the system. Mount it on <filename class="directory">/proc</filename>
    18 with:</para>
     25status of the system. Mount it with:</para>
    1926
    20 <screen><userinput>mount proc /proc -t proc</userinput></screen>
     27<screen><userinput>mount proc $LFS/proc -t proc</userinput></screen>
    2128
    22 <para>The <emphasis>devpts</emphasis> file system was mentioned earlier and is
    23 now the most common way for pseudo terminals (PTYs) to be implemented.</para>
     29<para>The <emphasis>devpts</emphasis> file system is now the most common way
     30for pseudo terminals (PTYs) to be implemented. Mount it with:</para>
    2431
    25 <para>The devpts file system is mounted on
    26 <filename class="directory">/dev/pts</filename> by running:</para>
     32<screen><userinput>mount devpts $LFS/dev/pts -t devpts</userinput></screen>
    2733
    28 <screen><userinput>mount devpts /dev/pts -t devpts</userinput></screen>
    29 
    30 <para>Should this command fail with an error to the effect of:</para>
     34<para>This last command might fail with an error to the effect of:</para>
    3135
    3236<blockquote><screen>filesystem devpts not supported by kernel</screen></blockquote>
    3337
    34 <para>The most likely cause is that your host system's kernel was compiled
    35 without support for the devpts file system. You can check which file systems
    36 your kernel supports by peeking into its internals with a command such as
     38<para>The most likely cause for this is that your host system's kernel was
     39compiled without support for the devpts file system. You can check which file
     40systems your kernel supports by peeking into its internals with
    3741<command>cat /proc/filesystems</command>. If a file system type named
    3842<emphasis>devfs</emphasis> is listed there, then we'll be able to work around
Note: See TracChangeset for help on using the changeset viewer.