gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-03-05 22:04:48 +00:00
Code Issues Packages Projects Releases Wiki Activity

textual changes

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2411 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Gerard Beekmans 2003-01-30 05:06:58 +00:00
parent bdadd380fa
commit 2b114b251e
11 changed files with 42 additions and 44 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
chapter05/binutils-inst.xml
View File

@ -4,10 +4,10 @@
<title>Installation of Binutils</title>
<para>This package is known to behave badly when you have changed its default
optimization flags (including the -march and -mcpu options). Binutils is
best left alone. Therefore, if you have defined any environment variables
that override default optimizations, such as CFLAGS and CXXFLAGS, we
recommend unsetting or modifying them when building binutils.</para>
optimization flags (including the -march and -mcpu options). Therefore, if
you have defined any environment variables that override default
optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting or
modifying them when building binutils.</para>
<para>It is recommended by the Binutils installation documentation to build
Binutils outside of the source directory in a dedicated directory:</para>

8
chapter05/gcc-inst.xml
View File

@ -7,10 +7,10 @@
the gcc-core tarball needs to be unpacked at this time.</para>
<para>This package is known to behave badly when you have changed its
default optimization flags (including the -march and -mcpu options). GCC is
best left alone. Therefore, if you have defined any environment variables
that override default optimizations, such as CFLAGS and CXXFLAGS, we
recommend unsetting or modifying them when building GCC.</para>
default optimization flags (including the -march and -mcpu options).
Therefore, if you have defined any environment variables that override
default optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting
or modifying them when building GCC.</para>
<para>It is recommended by the GCC installation documentation to build
GCC outside of the source directory in a dedicated directory:</para>

8
chapter06/binutils-inst.xml
View File

@ -3,10 +3,10 @@
<sect2><title>Installation of Binutils</title>
<para>This package is known to behave badly when you have changed its
default optimization flags (including the -march and -mcpu options). Binutils
is best left alone. Therefore, if you have defined any environment variables
that override default optimizations, such as CFLAGS and CXXFLAGS, we
recommend unsetting or modifying them when building binutils.</para>
default optimization flags (including the -march and -mcpu options).
Therefore, if you have defined any environment variables that override
default optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting
or modifying them when building binutils.</para>
<para>It is recommended by the Binutils installation documentation to build
Binutils outside of the source directory:</para>

12
chapter06/config-shadowpwd.xml
View File

@ -3,13 +3,13 @@
<sect2><title>Configuring Shadow Password Suite</title>
<para>This package contains utilities to modify users' passwords, add
or delete users and groups, and the like. We're not going to explain
what 'password shadowing' means. A full explanation can be found in the doc/HOWTO
or delete users and groups, and the like. We're not going to explain what
'password shadowing' means. A full explanation can be found in the doc/HOWTO
file within the unpacked shadow password suite's source tree. There's one
thing to keep in mind if you decide to use shadow support: that
programs that need to verify passwords (for example xdm, ftp daemons,
pop3 daemons) need to be 'shadow-compliant', that is they need to
be able to work with shadowed passwords.</para>
thing to keep in mind if you decide to use shadow support: programs that
need to verify passwords (for example xdm, ftp daemons, pop3 daemons) need
to be 'shadow-compliant', that is they need to be able to work with
hadowed passwords.</para>
<para>To enable shadowed passwords, run the following command:</para>

8
chapter06/gcc-inst.xml
View File

@ -4,10 +4,10 @@
<title>Installation of GCC</title>
<para>This package is known to behave badly when you have changed its
default optimization flags (including the -march and -mcpu options). GCC is
best left alone. Therefore, if you have defined any environment variables
that override default optimizations, such as CFLAGS and CXXFLAGS, we
recommend unsetting or modifying them when building GCC.</para>
default optimization flags (including the -march and -mcpu options).
Therefore, if you have defined any environment variables that override
default optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting
or modifying them when building GCC.</para>
<para>We will be building the C and C++ compilers at this time, so you'll
need to unpack both the gcc-core and gcc-g++ tarballs. Other compilers are

8
chapter06/glibc-inst.xml
View File

@ -9,10 +9,10 @@ the glibc-&glibc-version; directory, not in /usr/src as you normally
would do.</para>
<para>This package is known to behave badly when you have changed its
default optimization flags (including the -march and -mcpu options). Glibc
is best left alone. Therefore, if you have defined any environment variables
that override default optimizations, such as CFLAGS and CXXFLAGS, we
recommend unsetting or modifying them when building Glibc.</para>
default optimization flags (including the -march and -mcpu options).
Therefore, if you have defined any environment variables that override
default optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting
or modifying them when building Glibc.</para>
<para>Basically, compiling Glibc in any other way than the book suggests
is putting your system at a very high risk.</para>

16
chapter06/glibc-pass2-inst.xml
View File

@ -19,21 +19,19 @@ LFS. Much like GCC's bootstrap installation method).</para>
<para>We'll also install the linuxthreads man pages here. As you may
recall, during the first installation of Glibc this wasn't possible because
Perl wasn't installed yet. Everything we need to install the Glibc
linuxthread man pages is present now, so we'll take care of this too
now.</para>
Perl wasn't installed yet. Now that everything needed to install the Glibc
linuxthreads man pages is present as well, we will install those too.</para>
<para>Before starting to install glibc, you must cd into the
<para>Before starting to install Glibc, you must cd into the
glibc-&glibc-version; directory and unpack glibc-linuxthreads inside
the glibc-&glibc-version; directory, not in /usr/src as you normally
would do.</para>
<para>This package is known to behave badly when you have changed its
default optimization flags (including the -march and -mcpu options). Glibc
is best left alone. Therefore, if you have defined any environment variables
that override default optimizations, such as CFLAGS and CXXFLAGS, we
recommend unsetting or modifying them when building Glibc. You have
been warned.</para>
default optimization flags (including the -march and -mcpu options).
Therefore, if you have defined any environment variables that override
default optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting
or modifying them when building Glibc. You have been warned.</para>
<para>Basically, compiling Glibc in any other way than the book suggests
is putting your system at very high risk.</para>

2
chapter06/psmisc-inst.xml
View File

@ -3,7 +3,7 @@
<sect2>
<title>Installation of Psmisc</title>
<para>Prepare Psmic to be compiled:</para>
<para>Prepare Psmisc to be compiled:</para>
<para><screen><userinput>./configure --prefix=/usr --exec-prefix=/</userinput></screen></para>

10
chapter06/pwdgroup.xml
View File

@ -34,11 +34,11 @@ audio:x:11:
<userinput>EOF</userinput></screen></para>
<para>The created groups aren't part of any standard -- they are the groups
that the MAKEDEV script in the next section uses.
Besides the group "root", the LSB recommends only a group "bin", with a GID
of 1, be present. All other group names and GIDs can be chosen freely by
the user, as well-written packages don't depend on GID numbers but use the
group's name.</para>
that the MAKEDEV script in the next section uses. Besides the group "root",
the LSB (<ulink url="http://www.linuxbase.org"/>) (recommends only a group
"bin", with a GID of 1, be present. All other group names and GIDs can be
chosen freely by the user, as well-written packages don't depend on GID
numbers but use the group's name.</para>
</sect1>

4
chapter06/utillinux-inst.xml
View File

@ -4,8 +4,8 @@
<title>FHS compliance notes</title>
<para>The FHS recommends that we use /var/lib/hwclock, instead of the
usual /etc, as the location of the adjtime file. To make hwclock, which
is part of the util-linux package, FHS-compliant, run the following:</para>
usual /etc, as the location of the adjtime file. To make hwclock
FHS-compliant, run the following:</para>
<para><screen><userinput>cp hwclock/hwclock.c{,.backup} &amp;&amp;
sed 's%etc/adjtime%var/lib/hwclock/adjtime%' \

2
entities/man.ent
View File

@ -11,7 +11,7 @@
<!ENTITY aa-man-down SYSTEM "../appendixa/man-down.xml">
<!ENTITY man-version "1.5k">
<!ENTITY man-depversion "1.5i2">
<!ENTITY man-depversion "1.5i">
<!ENTITY man-contversion "1.5k">
<!ENTITY man-size "189 KB">