Changeset fe5b13b


Ignore:
Timestamp:
02/04/2004 10:22:49 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:
dcff046
Parents:
4248b0e
Message:

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

Files:
6 edited

Legend:

Unmodified
Added
Removed

  • chapter01/changelog.xml

    r4248b0e rfe5b13b  
    6363</listitem>
    6464
     65<listitem><para>February 4th, 2004 [alex]: Chapters 5 + 6 - Moved the Mounting
     66of proc and devpts to before Chrooting, dropped Util-linux from the tools, and
     67added a little arch script for Perl.</para></listitem>
     68
    6569<listitem><para>February 1st, 2004 [gerard]: LFS-5.1-PRE1
    6670release.</para></listitem>

  • chapter05/chapter05.xml

    r4248b0e rfe5b13b  
    569569&c5-texinfo;
    570570&c5-bash;
    571 &c5-utillinux;
    572571&c5-perl;
    573572

  • chapter05/gcc-pass2.xml

    r4248b0e rfe5b13b  
    129129a summary of the test suite results, run this:</para>
    130130 
    131 <screen><userinput>../&gcc-dir;/contrib/test_summary | more</userinput></screen>
     131<screen><userinput>../&gcc-dir;/contrib/test_summary | grep -A7 Summ</userinput></screen>
    132132
    133133<para>You can compare your results to those posted to the gcc-testresults

  • chapter05/perl.xml

    r4248b0e rfe5b13b  
    1818<screen><userinput>patch -Np1 -i ../&perl-libc-patch;</userinput></screen>
    1919
    20 <para>Now prepare Perl for compilation (make sure to get the 'IO Fcntl'
     20<para>Perl insists on using the <command>arch</command> program to find out
     21the machine type. Create a little script to mimick this command:</para>
     22
     23<screen><userinput>echo "uname -m" &gt; /tools/bin/arch
     24chmod 755 /tools/bin/arch</userinput></screen>
     25
     26<para>Now prepare Perl for compilation (make sure you get the 'IO Fcntl'
    2127right, they are all letters):</para>
    2228

  • chapter06/chapter06.xml

    r4248b0e rfe5b13b  
    6161</sect1>
    6262
     63&c6-mountproc;
    6364
    6465<sect1 id="ch-system-chroot">
    … …  
    6667<?dbhtml filename="chroot.html" dir="chapter06"?>
    6768
    68 <para>It is time to enter the chroot environment in order to begin installing
    69 the packages we need. Before you can chroot, however, you need to become
    70 <emphasis>root</emphasis>, since only <emphasis>root</emphasis>
    71 can execute the <command>chroot</command> command.</para>
    72 
    73 <para>Just like earlier, ensure the LFS environment variable is set up properly
    74 by running <userinput>echo $LFS</userinput> and ensuring it shows the path to
    75 your LFS partition's mount point, which is
     69<para>It is time to enter the chroot environment in order to begin building
     70and installing your final LFS system.</para>
     71
     72<para>First check, just like earlier, that the LFS environment variable is set
     73up properly by running <userinput>echo $LFS</userinput> and making sure it
     74shows the path to your LFS partition's mount point, which is
    7675<filename class="directory">/mnt/lfs</filename> if you followed our example.</para>
    7776
    78 <para>Become <emphasis>root</emphasis> and run the following command
    79 to enter the chroot environment:</para>
     77<para>As <emphasis>root</emphasis>, run the following command to enter the
     78chroot environment:</para>
    8079
    8180<screen><userinput>chroot $LFS /tools/bin/env -i \
    … …  
    109108in the following chapters are run from within the chroot environment.
    110109If you ever leave this environment for any reason (rebooting for example),
    111 you must remember to again enter chroot and mount the proc and devpts
    112 file systems (discussed later) before continuing with the installations.</para>
    113 
    114 <para>Note that the bash prompt will say "I have no name!" This is
    115 normal, as the <filename>/etc/passwd</filename> file has not been
    116 created yet.</para>
     110you must remember to first mount the proc and devpts file systems (discussed
     111in the previous section) <emphasis>and</emphasis> enter chroot again before
     112continuing with the installations.</para>
     113
     114<para>Note that the bash prompt will say "I have no name!" This is normal, as
     115the <filename>/etc/passwd</filename> file has not been created yet.</para>
    117116
    118117</sect1>
    … …  
    208207
    209208</sect1>
    210 
    211 
    212 &c6-mountproc;
    213209
    214210

  • chapter06/mountproc.xml

    r4248b0e rfe5b13b  
    77available within the chroot environment. Since kernel version 2.4 a file system
    88can 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 --
     9problem that these file systems are already mounted on your host system,
    1010especially so because they are virtual file systems.</para>
     11
     12<para>First you need to become <emphasis>root</emphasis>, since probably only
     13<emphasis>root</emphasis> can mount these file systems.</para>
    1114
    1215<para>The <emphasis>proc</emphasis> file system is the process information
    1316pseudo file system through which the kernel provides information about the
    14 status of the system.</para>
    15 
    16 <para>The proc file system is mounted on
    17 <filename class="directory">/proc</filename> by running the following
    18 command:</para>
     17status of the system. Mount it on <filename class="directory">/proc</filename>
     18with:</para>
    1919
    2020<screen><userinput>mount proc /proc -t proc</userinput></screen>
    21 
    22 <para>You might get warning messages from the mount command, such as
    23 these:</para>
    24 
    25 <blockquote><screen>warning: can't open /etc/fstab: No such file or directory
    26 not enough memory</screen></blockquote>
    27 
    28 <para>Ignore these, they're just due to the fact that the system
    29 isn't installed completely yet and some files are missing. The mount itself
    30 will be successful and that's all we care about at this point.</para>
    3121
    3222<para>The <emphasis>devpts</emphasis> file system was mentioned earlier and is
    … …  
    5545
    5646<para>Remember, if for any reason you stop working on your LFS, and start again
    57 later, it's important to check that these file systems are still mounted inside
    58 the chroot environment, otherwise problems are likely to occur.</para>
     47later, it's important to check that these file systems are mounted again before
     48entering the chroot environment, otherwise some problems could occur.</para>
    5949
    6050</sect1>
Note: See TracChangeset for help on using the changeset viewer.