Changeset cbc99c8


Ignore:
Timestamp:
07/01/2005 11:36:35 PM (19 years ago)
Author:
Archaic <archaic@…>
Branches:
6.1, 6.1.1
Children:
6169f0c
Parents:
808f5af
Message:

Several minor wording changes in chapter 6. (merged from trunk r6249)

git-svn-id: http://svn.linuxfromscratch.org/LFS/branches/6.1/BOOK@6311 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

Files:
8 edited

Legend:

Unmodified
Added
Removed
  • chapter01/changelog.xml

    r808f5af rcbc99c8  
    8888</listitem>
    8989
     90<listitem><para>July  1st, 2005 [archaic]: Several minor wording changes in
     91chapter 6 (matt).</para></listitem>
     92
    9093<listitem><para>July  1st, 2005 [archaic]: Brought all occurences of
    9194LFS-Bootscripts into conformity.</para></listitem>
  • chapter06/chroot.xml

    r808f5af rcbc99c8  
    3838(<filename class="directory">/</filename>) directory.</para>
    3939
    40 <para>Notice that <filename class="directory">/tools/bin</filename>
    41 comes last in the <envar>PATH</envar>. This means that a
    42 temporary tool will not be used anymore as soon as its final version
    43 is installed. This occurs when the shell does not <quote>remember</quote> the
    44 locations of executed binaries&mdash;for this reason, hashing is switched
    45 off by passing the <parameter>+h</parameter> option to <command>bash</command>.</para>
     40<para>Notice that <filename class="directory">/tools/bin</filename> comes last
     41in the <envar>PATH</envar>. This means that a temporary tool will no longer be
     42used once its final version is installed. This occurs when the shell does not
     43<quote>remember</quote> the locations of executed binaries&mdash;for this
     44reason, hashing is switched off by passing the <parameter>+h</parameter> option
     45to <command>bash</command>.</para>
    4646
    4747<para>It is important that all the commands throughout the remainder
  • chapter06/createfiles.xml

    r808f5af rcbc99c8  
    88<?dbhtml filename="createfiles.html"?>
    99
    10 <para>Some programs use hard-wired paths to programs which do not yet
    11 exist. In order to satisfy these programs, create a number of symbolic
    12 links which will be replaced by real files throughout the course of
    13 this chapter after the software has been installed.</para>
     10<para>Some programs use hard-wired paths to programs which do not exist yet. In
     11order to satisfy these programs, create a number of symbolic links which will be
     12replaced by real files throughout the course of this chapter after the software
     13has been installed.</para>
    1414
    1515<screen><userinput>ln -s /tools/bin/{bash,cat,pwd,stty} /bin
  • chapter06/creatingdirs.xml

    r808f5af rcbc99c8  
    5050<title>FHS Compliance Note</title>
    5151
    52 <para>The directory tree is based on the Filesystem Hierarchy Standard
    53 (FHS) standard (available at <ulink
    54 url="http://www.pathname.com/fhs/"/>). Besides the tree created above,
    55 this standard stipulates the existence of <filename
     52<para>The directory tree is based on the Filesystem Hierarchy Standard (FHS)
     53 (available at <ulink url="http://www.pathname.com/fhs/"/>). In addition
     54to the tree created above, this standard stipulates the existence of <filename
    5655class="directory">/usr/local/games</filename> and <filename
    57 class="directory">/usr/share/games</filename>.  We do not recommend
    58 these for a base system, however, feel free to make the system
    59 FHS-compliant.  The FHS is not precise as to the structure of the
    60 <filename class="directory">/usr/local/share</filename> subdirectory,
    61 so we created only the directories that are needed.</para>
     56class="directory">/usr/share/games</filename>. The FHS is not precise as to the
     57structure of the <filename class="directory">/usr/local/share</filename>
     58subdirectory, so we create only the directories that are needed. However, feel
     59free to create these directories if you prefer to conform more strictly to the
     60FHS standard.</para>
    6261
    6362</sect2>
  • chapter06/glibc.xml

    r808f5af rcbc99c8  
    111111
    112112<listitem><para>If you have mounted the LFS partition with the
    113 <parameter>noatime</parameter> option, the <emphasis>atime</emphasis>
    114 test will fail.  This is not critical.</para></listitem>
     113<parameter>noatime</parameter> option, the <emphasis>atime</emphasis> test will
     114fail. As mentioned in <xref linkend="space-mounting"/>, do not use the
     115<parameter>noatime</parameter> option while building LFS.</para></listitem>
    115116
    116117<listitem><para>When running on older and slower hardware, some tests
     
    194195<indexterm zone="conf-glibc"><primary sortas="e-/etc/localtime">/etc/localtime</primary></indexterm>
    195196
    196 <para>The <filename>/etc/nsswitch.conf</filename> file needs to be
    197 created because, although Glibc provides defaults when this file is
    198 missing or corrupt, the Glibc defaults do not work well with
    199 networking. The time zone also needs to be set up.</para>
     197<para>The <filename>/etc/nsswitch.conf</filename> file needs to be created
     198because, although Glibc provides defaults when this file is missing or corrupt,
     199the Glibc defaults do not work well in a networked environment. The time zone
     200also needs to be configured.</para>
    200201
    201202<para>Create a new file <filename>/etc/nsswitch.conf</filename> by running the
     
    233234    /etc/localtime</userinput></screen>
    234235
    235 <para>Replace <replaceable>[xxx]</replaceable> with the name of the time zone that the
    236 <command>tzselect</command> provided (e.g., Canada/Eastern).</para>
     236<para>Replace <replaceable>[xxx]</replaceable> with the name of the time zone
     237that <command>tzselect</command> provided (e.g., Canada/Eastern).</para>
    237238
    238239<para>The meaning of the cp option:</para>
  • chapter06/kernfs.xml

    r808f5af rcbc99c8  
    88<?dbhtml filename="kernfs.html"?>
    99
    10 <para>Various file systems exported by the kernel do not exist on the
    11 hard drive, but are used to communicate to and from the kernel
    12 itself.</para>
     10<para>Various file systems exported by the kernel are used to communicate to and
     11from the kernel itself. These file systems are virtual in that no disk space is
     12used for them. The contents of the file systems resides in memory.</para>
    1313
    1414<para>Begin by creating directories onto which the file systems will be mounted:</para>
  • chapter06/pwdgroup.xml

    r808f5af rcbc99c8  
    5151EOF</userinput></screen>
    5252
    53 <para>The created groups are not part of any standard&mdash;they are some
    54 of the groups that the Udev configuration will be using in the next
    55 section. The Linux Standard Base (LSB, available at <ulink
    56 url="http://www.linuxbase.org"/>) recommends only that, besides the
    57 group <quote>root</quote> with a Group ID (GID) of 0, a group
    58 <quote>bin</quote> with a GID of 1 be present. All other group names
    59 and GIDs can be chosen freely by the system administrator since
    60 well-written packages do not depend on GID numbers, but rather use the
    61 group's name.</para>
     53<para>The created groups are not part of any standard&mdash;they are some of the
     54groups that the Udev configuration will use in the next section. The Linux
     55Standard Base (LSB, available at <ulink url="http://www.linuxbase.org"/>)
     56recommends only that, besides the group <quote>root</quote> with a Group ID
     57(GID) of 0, a group <quote>bin</quote> with a GID of 1 be present. All other
     58group names and GIDs can be chosen freely by the system administrator since
     59well-written packages do not depend on GID numbers, but rather use the group's
     60name.</para>
    6261
    6362<para>To remove the <quote>I have no name!</quote> prompt, start a new
  • chapter06/readjusting.xml

    r808f5af rcbc99c8  
    88<?dbhtml filename="readjusting.html"?>
    99
    10 <para>Now that the new and final C libraries have been installed, it
    11 is time to adjust the toolchain again. The toolchain will be adjusted
    12 so that it will link any newly compiled program against these new
    13 libraries. This is the same process used in the
    14 <quote>Adjusting</quote> phase in the beginning of <xref
    15 linkend="chapter-temporary-tools"/>, even though it looks to be
    16 reversed. In <xref linkend="chapter-temporary-tools"/>, the chain was
    17 guided from the host's <filename
    18 class="directory">/{,usr/}lib</filename> directories to the new
    19 <filename class="directory">/tools/lib</filename> directory. Now, the
    20 chain will be guided from that same <filename
    21 class="directory">/tools/lib</filename> directory to the LFS
    22 <filename class="directory">/{,usr/}lib</filename> directories.</para>
     10<para>Now that the final C libraries have been installed, it is time to adjust
     11the toolchain again. The toolchain will be adjusted so that it will link any
     12newly compiled program against these new libraries. This is the same process
     13used in the <quote>Adjusting</quote> phase in the beginning of <xref
     14linkend="chapter-temporary-tools"/>, but with the adjustments reversed. In <xref
     15linkend="chapter-temporary-tools"/>, the chain was guided from the host's
     16<filename class="directory">/{,usr/}lib</filename> directories to the new
     17<filename class="directory">/tools/lib</filename> directory. Now, the chain will
     18be guided from that same <filename class="directory">/tools/lib</filename>
     19directory to the LFS <filename class="directory">/{,usr/}lib</filename>
     20directories.</para>
    2321
    24 <para>Start by adjusting the linker. The source and build directories
    25 from the second pass over Binutils were retained for this purpose.
    26 Install the adjusted linker by running the following command from
    27 within the <filename class="directory">binutils-build</filename>
    28 directory:</para>
     22<para>Start by adjusting the linker. The source and build directories from the
     23second pass of Binutils were retained for this purpose. Install the adjusted
     24linker by running the following command from within the <filename
     25class="directory">binutils-build</filename> directory:</para>
    2926
    3027<screen><userinput>make -C ld INSTALL=/tools/bin/install install</userinput></screen>
Note: See TracChangeset for help on using the changeset viewer.