Changes in / [82e98d0:38311c3]


Ignore:
Files:
4 edited

Legend:

Unmodified
Added
Removed

  • chapter04/creatingminlayout.xml

    r82e98d0 r38311c3  
    99  <?dbhtml filename="creatingminlayout.html"?>
    1010
    11   <title>Creating a limited directory layout in LFS filesystem</title>
     11  <title>Creating a Limited Directory Layout in the LFS Filesystem</title>
    1212
    1313  <para>In this section, we begin populating the LFS filesystem with the
    … …  
    4040<screen><userinput>mkdir -pv $LFS/tools</userinput></screen>
    4141
     42  <note>
     43    <para>
     44      The LFS editors have deliberately decided not to use a
     45      <filename class="directory">/usr/lib64</filename> directory.  Several
     46      steps are taken to be sure the toolchain will not use it. If for any
     47      reason this directory appears (either because you made an error in
     48      following the instructions, or because you installed a binary package that
     49      created it after finishing LFS), it may break your system.
     50      You should always be sure this directory does not exist.
     51    </para>
     52  </note>
     53
    4254</sect1>

  • chapter07/creatingdirs.xml

    r82e98d0 r38311c3  
    6969    directories, if you wish.  </para>
    7070
     71  <warning>
     72    <para>
     73      The FHS does not mandate the existence of the directory
     74      <filename class="directory">/usr/lib64</filename>, and the LFS editors
     75      have decided not to use it. For the instructions in LFS and BLFS to work correctly,
     76      it is imperative that this directory be non-existent. From time to time you should
     77      verify that it does not exist, because it is easy to create it
     78      inadvertently, and this will probably break your system.
     79    </para>
     80  </warning>
     81
    7182  </sect2>
    7283

  • chapter08/gcc.xml

    r82e98d0 r38311c3  
    8181             --with-system-zlib</userinput></screen>
    8282
    83     <para>Note that for other programming languages there are some prerequisites that
    84     are not yet available. See the
     83    <para>GCC supports seven different computer languages, but the
     84    prerequisites for most of them have not yet been installed. See the
    8585    <ulink url="&blfs-book;general/gcc.html">BLFS Book GCC page</ulink>
    8686    for instructions on how to build all of GCC's supported languages.</para>
    … …  
    9292        <term><parameter>LD=ld</parameter></term>
    9393        <listitem>
    94           <para>This parameter makes the configure script use the ld installed
    95           by the binutils built earlier in this chapter, rather than
     94          <para>This parameter makes the configure script use the ld program installed
     95          by the Binutils package built earlier in this chapter, rather than
    9696          the cross-built version which would otherwise be used.</para>
    9797        </listitem>
    … …  
    102102        <listitem>
    103103          <para>This switch tells GCC to link to the system installed copy of
    104           the zlib library, rather than its own internal copy.</para>
     104          the Zlib library, rather than its own internal copy.</para>
    105105        </listitem>
    106106      </varlistentry>
    … …  
    110110      <anchor id="pie-ssp-info" xreflabel="note on PIE and SSP"/>
    111111      <para>
    112         PIE (position-independent executable) is a technique to produce
     112        PIE (position-independent executables) are
    113113        binary programs that can be loaded anywhere in memory.  Without PIE,
    114114        the security feature named ASLR (Address Space Layout Randomization)
    115         can be applied for the shared libraries, but not the executable
    116         itself.  Enabling PIE allows ASLR for the executables in addition to
     115        can be applied for the shared libraries, but not for the executables
     116        themselves.  Enabling PIE allows ASLR for the executables in addition to
    117117        the shared libraries, and mitigates some attacks based on fixed
    118118        addresses of sensitive code or data in the executables.
    … …  
    120120      <para>
    121121        SSP (Stack Smashing Protection) is a technique to ensure
    122         that the parameter stack is not corrupted. Stack corruption can
    123         for example alter the return address of a subroutine,
    124         which would allow transferring control to some dangerous code
     122        that the parameter stack is not corrupted. Stack corruption can,
     123        for example, alter the return address of a subroutine,
     124        thus transferring control to some dangerous code
    125125        (existing in the program or shared libraries, or injected by the
    126         attacker somehow) instead of the original one.
     126        attacker somehow).
    127127      </para>
    128128    </note>
    … …  
    134134    <important>
    135135      <para>In this section, the test suite for GCC is considered
    136       important, but it takes a long time. First time builders are
    137       encouraged to not skip it.  The time to run the tests can be
    138       reduced significantly by adding -jx to the make command below
    139       where x is the number of cores on your system.</para>
     136      important, but it takes a long time. First-time builders are
     137      encouraged to run the test suite.  The time to run the tests can be
     138      reduced significantly by adding -jx to the <command>make -k check</command> command below,
     139      where x is the number of CPU cores on your system.</para>
    140140    </important>
    141141
    … …  
    150150su tester -c "PATH=$PATH make -k check"</userinput></screen>
    151151
    152     <para>To receive a summary of the test suite results, run:</para>
     152    <para>To extract a summary of the test suite results, run:</para>
    153153
    154154<screen><userinput remap="test">../contrib/test_summary</userinput></screen>
    155155
    156     <para>For only the summaries, pipe the output through
     156    <para>To filter out only the summaries, pipe the output through
    157157    <userinput>grep -A7 Summ</userinput>.</para>
    158158
    … …  
    161161    <ulink url="https://gcc.gnu.org/ml/gcc-testresults/"/>.</para>
    162162
    163     <para>In gcc, eleven tests, in the i386 test suite are known to FAIL.
     163    <para>Eleven tests in the i386 test suite for the gcc compiler are known to FAIL.
    164164    It's because the test files do not account for the
    165165    <parameter>--enable-default-pie</parameter> option.</para>
    166166
    167     <para>In g++, four tests related to PR100400 are known to be reported
    168     as both XPASS and FAIL.  It's because the test file for this known issue
     167    <para>Four tests related to PR100400 may be reported
     168    as both XPASS and FAIL when testing the g++ compiler; the test file
    169169    is not well written.</para>
    170170
    … …  
    188188
    189189    <para>The GCC build directory is owned by <systemitem class="username">
    190     tester</systemitem> now and the ownership of the installed header
    191     directory (and its content) will be incorrect.  Change the ownership to
     190    tester</systemitem> now, and the ownership of the installed header
     191    directory (and its content) is incorrect.  Change the ownership to the
    192192    <systemitem class="username">root</systemitem> user and group:</para>
    193193
    … …  
    226226<screen><computeroutput>[Requesting program interpreter: /lib64/ld-linux-x86-64.so.2]</computeroutput></screen>
    227227
    228   <para>Now make sure that we're setup to use the correct start files:</para>
     228  <para>Now make sure that we're set up to use the correct start files:</para>
    229229
    230230<screen><userinput>grep -E -o '/usr/lib.*/S?crt[1in].*succeeded' dummy.log</userinput></screen>
    … …  
    275275SEARCH_DIR("/usr/lib");</computeroutput></screen>
    276276
    277    <para>A 32-bit system may see a few different directories. For example, here
     277   <para>A 32-bit system may use a few other directories. For example, here
    278278   is the output from an i686 machine:</para>
    279279
    … …  
    308308  steps to find out where the problem is and correct it. <!--The most likely
    309309  reason is that something went wrong with the specs file adjustment.--> Any
    310   issues will need to be resolved before continuing with the process.</para>
     310  issues should be resolved before continuing with the process.</para>
    311311
    312312  <para>Once everything is working correctly, clean up the test files:</para>
    … …  
    375375        <listitem>
    376376          <para>The C preprocessor; it is used by the compiler to expand the
    377           #include, #define, and similar statements in the source files</para>
     377          #include, #define, and similar directives in the source files</para>
    378378          <indexterm zone="ch-system-gcc cpp">
    379379            <primary sortas="b-cpp">cpp</primary>
    … …  
    408408          plugin to the command line. This program is only used
    409409          to add "link time optimization" and is not useful with the
    410           default build options</para>
     410          default build options.</para>
    411411          <indexterm zone="ch-system-gcc gcc-ar">
    412412            <primary sortas="b-gcc-ar">gc-ar</primary>
    … …  
    421421          plugin to the command line. This program is only used
    422422          to add "link time optimization" and is not useful with the
    423           default build options</para>
     423          default build options.</para>
    424424          <indexterm zone="ch-system-gcc gcc-nm">
    425425            <primary sortas="b-gcc-nm">gc-nm</primary>
    … …  
    434434          plugin to the command line. This program is only used
    435435          to add "link time optimization" and is not useful with the
    436           default build options</para>
     436          default build options.</para>
    437437          <indexterm zone="ch-system-gcc gcc-ranlib">
    438438            <primary sortas="b-gcc-ranlib">gc-ranlib</primary>
    … …  
    445445        <listitem>
    446446          <para>A coverage testing tool; it is used to analyze programs to
    447           determine where optimizations will have the most effect</para>
     447          determine where optimizations will have the greatest effect</para>
    448448          <indexterm zone="ch-system-gcc gcov">
    449449            <primary sortas="b-gcov">gcov</primary>
    … …  
    526526        <term><filename class="libraryfile">libgcov</filename></term>
    527527        <listitem>
    528           <para>This library is linked in to a program when GCC is instructed
     528          <para>This library is linked into a program when GCC is instructed
    529529          to enable profiling</para>
    530530          <indexterm zone="ch-system-gcc libgcov">
    … …  
    568568        <term><filename class="libraryfile">liblto_plugin</filename></term>
    569569        <listitem>
    570           <para>GCC's LTO plugin allows binutils to process object files
     570          <para>GCC's LTO plugin allows Binutils to process object files
    571571          produced by GCC with LTO enabled</para>
    572572          <indexterm zone="ch-system-gcc liblto_plugin">
    … …  
    590590        <listitem>
    591591          <para>Contains routines supporting GCC's stack-smashing protection
    592           functionality.  Normally it's unused because glibc also provides
    593           those routines</para>
     592          functionality.  Normally it is not used, because Glibc also provides
     593          those routines.</para>
    594594          <indexterm zone="ch-system-gcc libssp">
    595595            <primary sortas="c-libssp">libssp</primary>

  • chapter08/shadow.xml

    r82e98d0 r38311c3  
    6363    <emphasis>crypt</emphasis> method, use the more secure
    6464    <emphasis>SHA-512</emphasis> method of password encryption, which also
    65     allows passwords longer than 8 characters. It is also necessary to change
     65    allows passwords longer than 8 characters. In addition, set the number of
     66    rounds to 500,000 instead of the default 5000, which is much too low to
     67    prevent brute force password attacks. It is also necessary to change
    6668    the obsolete <filename class="directory">/var/spool/mail</filename> location
    6769    for user mailboxes that Shadow uses by default to the <filename
    … …  
    8183
    8284<screen><userinput remap="pre">sed -e 's:#ENCRYPT_METHOD DES:ENCRYPT_METHOD SHA512:' \
     85    -e 's@#\(SHA_CRYPT_..._ROUNDS 5000\)@\100@'       \
    8386    -e 's:/var/spool/mail:/var/mail:'                 \
    8487    -e '/PATH=/{s@/sbin:@@;s@/bin:@@}'                \
    … …  
    204207          an ID equal to this number on your system, then the first time you use
    205208          <command>useradd</command> without the <parameter>-g</parameter>
    206           parameter, an error message will be generated &mdash; <computeroutput>useradd:
     209          parameter, an error message will be generated&mdash;<computeroutput>useradd:
    207210          unknown GID 999</computeroutput>,
    208211          even though the account has been created correctly. That is why we
Note: See TracChangeset for help on using the changeset viewer.