Changeset 2b114b25 for chapter06


Ignore:
Timestamp:
01/30/2003 05:06:58 AM (21 years ago)
Author:
Gerard Beekmans <gerard@…>
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, v4_1, v5_0, 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:
6f531d7
Parents:
bdadd38
Message:

textual changes

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

Location:
chapter06
Files:
8 edited

Legend:

Unmodified
Added
Removed

  • chapter06/binutils-inst.xml

    rbdadd38 r2b114b25  
    44
    55<para>This package is known to behave badly when you have changed its
    6 default optimization flags (including the -march and -mcpu options). Binutils
    7 is best left alone. Therefore, if you have defined any environment variables
    8 that override default optimizations, such as CFLAGS and CXXFLAGS, we
    9 recommend unsetting or modifying them when building binutils.</para>
     6default optimization flags (including the -march and -mcpu options).
     7Therefore, if you have defined any environment variables that override
     8default optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting
     9or modifying them when building binutils.</para>
    1010
    1111<para>It is recommended by the Binutils installation documentation to build

  • chapter06/config-shadowpwd.xml

    rbdadd38 r2b114b25  
    44
    55<para>This package contains utilities to modify users' passwords, add
    6 or delete users and groups, and the like. We're not going to explain
    7 what 'password shadowing' means. A full explanation can be found in the doc/HOWTO
     6or delete users and groups, and the like. We're not going to explain what
     7'password shadowing' means. A full explanation can be found in the doc/HOWTO
    88file within the unpacked shadow password suite's source tree. There's one
    9 thing to keep in mind if you decide to use shadow support: that
    10 programs that need to verify passwords (for example xdm, ftp daemons,
    11 pop3 daemons) need to be 'shadow-compliant', that is they need to
    12 be able to work with shadowed passwords.</para>
     9thing to keep in mind if you decide to use shadow support: programs that
     10need to verify passwords (for example xdm, ftp daemons, pop3 daemons) need
     11to be 'shadow-compliant', that is they need to be able to work with
     12hadowed passwords.</para>
    1313
    1414<para>To enable shadowed passwords, run the following command:</para>

  • chapter06/gcc-inst.xml

    rbdadd38 r2b114b25  
    55
    66<para>This package is known to behave badly when you have changed its
    7 default optimization flags (including the -march and -mcpu options). GCC is
    8 best left alone. Therefore, if you have defined any environment variables
    9 that override default optimizations, such as CFLAGS and CXXFLAGS, we
    10 recommend unsetting or modifying them when building GCC.</para>
     7default optimization flags (including the -march and -mcpu options).
     8Therefore, if you have defined any environment variables that override
     9default optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting
     10or modifying them when building GCC.</para>
    1111
    1212<para>We will be building the C and C++ compilers at this time, so you'll

  • chapter06/glibc-inst.xml

    rbdadd38 r2b114b25  
    1010
    1111<para>This package is known to behave badly when you have changed its
    12 default optimization flags (including the -march and -mcpu options). Glibc
    13 is best left alone. Therefore, if you have defined any environment variables
    14 that override default optimizations, such as CFLAGS and CXXFLAGS, we
    15 recommend unsetting or modifying them when building Glibc.</para>
     12default optimization flags (including the -march and -mcpu options).
     13Therefore, if you have defined any environment variables that override
     14default optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting
     15or modifying them when building Glibc.</para>
    1616
    1717<para>Basically, compiling Glibc in any other way than the book suggests

  • chapter06/glibc-pass2-inst.xml

    rbdadd38 r2b114b25  
    2020<para>We'll also install the linuxthreads man pages here. As you may
    2121recall, during the first installation of Glibc this wasn't possible because
    22 Perl wasn't installed yet. Everything we need to install the Glibc
    23 linuxthread man pages is present now, so we'll take care of this too
    24 now.</para>
     22Perl wasn't installed yet. Now that everything needed to install the Glibc
     23linuxthreads man pages is present as well, we will install those too.</para>
    2524
    26 <para>Before starting to install glibc, you must cd into the
     25<para>Before starting to install Glibc, you must cd into the
    2726glibc-&glibc-version; directory and unpack glibc-linuxthreads inside
    2827the glibc-&glibc-version; directory, not in /usr/src as you normally
    … …  
    3029
    3130<para>This package is known to behave badly when you have changed its
    32 default optimization flags (including the -march and -mcpu options). Glibc
    33 is best left alone. Therefore, if you have defined any environment variables
    34 that override default optimizations, such as CFLAGS and CXXFLAGS, we
    35 recommend unsetting or modifying them when building Glibc. You have
    36 been warned.</para>
     31default optimization flags (including the -march and -mcpu options).
     32Therefore, if you have defined any environment variables that override
     33default optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting
     34or modifying them when building Glibc. You have been warned.</para>
    3735
    3836<para>Basically, compiling Glibc in any other way than the book suggests

  • chapter06/psmisc-inst.xml

    rbdadd38 r2b114b25  
    44<title>Installation of Psmisc</title>
    55
    6 <para>Prepare Psmic to be compiled:</para>
     6<para>Prepare Psmisc to be compiled:</para>
    77
    88<para><screen><userinput>./configure --prefix=/usr --exec-prefix=/</userinput></screen></para>

  • chapter06/pwdgroup.xml

    rbdadd38 r2b114b25  
    3535
    3636<para>The created groups aren't part of any standard -- they are the groups
    37 that the MAKEDEV script in the next section uses.
    38 Besides the group "root", the LSB recommends only a group "bin", with a GID
    39 of 1, be present. All other group names and GIDs can be chosen freely by
    40 the user, as well-written packages don't depend on GID numbers but use the
    41 group's name.</para>
     37that the MAKEDEV script in the next section uses. Besides the group "root",
     38the LSB (<ulink url="http://www.linuxbase.org"/>) (recommends only a group
     39"bin", with a GID of 1, be present. All other group names and GIDs can be
     40chosen freely by the user, as well-written packages don't depend on GID
     41numbers but use the group's name.</para>
    4242
    4343</sect1>

  • chapter06/utillinux-inst.xml

    rbdadd38 r2b114b25  
    55
    66<para>The FHS recommends that we use /var/lib/hwclock, instead of the
    7 usual /etc, as the location of the adjtime file. To make hwclock, which
    8 is part of the util-linux package, FHS-compliant, run the following:</para>
     7usual /etc, as the location of the adjtime file. To make hwclock
     8FHS-compliant, run the following:</para>
    99
    1010<para><screen><userinput>cp hwclock/hwclock.c{,.backup} &amp;&amp;
Note: See TracChangeset for help on using the changeset viewer.