cvs commit: LFS/BOOK/entities man.ent

gerard at linuxfromscratch.org gerard at linuxfromscratch.org
Wed Jan 29 21:06:58 PST 2003


gerard      03/01/30 00:06:58

  Modified:    BOOK/chapter05 binutils-inst.xml gcc-inst.xml
               BOOK/chapter06 binutils-inst.xml config-shadowpwd.xml
                        gcc-inst.xml glibc-inst.xml glibc-pass2-inst.xml
                        psmisc-inst.xml pwdgroup.xml utillinux-inst.xml
               BOOK/entities man.ent
  Log:
  textual changes
  
  Revision  Changes    Path
  1.21      +4 -4      LFS/BOOK/chapter05/binutils-inst.xml
  
  Index: binutils-inst.xml
  ===================================================================
  RCS file: /home/cvsroot/LFS/BOOK/chapter05/binutils-inst.xml,v
  retrieving revision 1.20
  retrieving revision 1.21
  diff -u -r1.20 -r1.21
  --- binutils-inst.xml	27 Jan 2003 21:28:02 -0000	1.20
  +++ binutils-inst.xml	30 Jan 2003 05:06:57 -0000	1.21
  @@ -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>
  
  
  
  1.50      +4 -4      LFS/BOOK/chapter05/gcc-inst.xml
  
  Index: gcc-inst.xml
  ===================================================================
  RCS file: /home/cvsroot/LFS/BOOK/chapter05/gcc-inst.xml,v
  retrieving revision 1.49
  retrieving revision 1.50
  diff -u -r1.49 -r1.50
  --- gcc-inst.xml	27 Jan 2003 21:28:02 -0000	1.49
  +++ gcc-inst.xml	30 Jan 2003 05:06:58 -0000	1.50
  @@ -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>
  
  
  
  1.16      +4 -4      LFS/BOOK/chapter06/binutils-inst.xml
  
  Index: binutils-inst.xml
  ===================================================================
  RCS file: /home/cvsroot/LFS/BOOK/chapter06/binutils-inst.xml,v
  retrieving revision 1.15
  retrieving revision 1.16
  diff -u -r1.15 -r1.16
  --- binutils-inst.xml	27 Jan 2003 22:10:07 -0000	1.15
  +++ binutils-inst.xml	30 Jan 2003 05:06:58 -0000	1.16
  @@ -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>
  
  
  
  1.12      +6 -6      LFS/BOOK/chapter06/config-shadowpwd.xml
  
  Index: config-shadowpwd.xml
  ===================================================================
  RCS file: /home/cvsroot/LFS/BOOK/chapter06/config-shadowpwd.xml,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- config-shadowpwd.xml	28 Jan 2003 01:17:02 -0000	1.11
  +++ config-shadowpwd.xml	30 Jan 2003 05:06:58 -0000	1.12
  @@ -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>
   
  
  
  
  1.42      +4 -4      LFS/BOOK/chapter06/gcc-inst.xml
  
  Index: gcc-inst.xml
  ===================================================================
  RCS file: /home/cvsroot/LFS/BOOK/chapter06/gcc-inst.xml,v
  retrieving revision 1.41
  retrieving revision 1.42
  diff -u -r1.41 -r1.42
  --- gcc-inst.xml	30 Jan 2003 04:33:38 -0000	1.41
  +++ gcc-inst.xml	30 Jan 2003 05:06:58 -0000	1.42
  @@ -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
  
  
  
  1.82      +4 -4      LFS/BOOK/chapter06/glibc-inst.xml
  
  Index: glibc-inst.xml
  ===================================================================
  RCS file: /home/cvsroot/LFS/BOOK/chapter06/glibc-inst.xml,v
  retrieving revision 1.81
  retrieving revision 1.82
  diff -u -r1.81 -r1.82
  --- glibc-inst.xml	27 Jan 2003 22:10:07 -0000	1.81
  +++ glibc-inst.xml	30 Jan 2003 05:06:58 -0000	1.82
  @@ -9,10 +9,10 @@
   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>
  
  
  
  1.5       +7 -9      LFS/BOOK/chapter06/glibc-pass2-inst.xml
  
  Index: glibc-pass2-inst.xml
  ===================================================================
  RCS file: /home/cvsroot/LFS/BOOK/chapter06/glibc-pass2-inst.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- glibc-pass2-inst.xml	17 Jan 2003 20:22:16 -0000	1.4
  +++ glibc-pass2-inst.xml	30 Jan 2003 05:06:58 -0000	1.5
  @@ -19,21 +19,19 @@
   
   <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>
  
  
  
  1.15      +1 -1      LFS/BOOK/chapter06/psmisc-inst.xml
  
  Index: psmisc-inst.xml
  ===================================================================
  RCS file: /home/cvsroot/LFS/BOOK/chapter06/psmisc-inst.xml,v
  retrieving revision 1.14
  retrieving revision 1.15
  diff -u -r1.14 -r1.15
  --- psmisc-inst.xml	17 Jan 2003 03:58:38 -0000	1.14
  +++ psmisc-inst.xml	30 Jan 2003 05:06:58 -0000	1.15
  @@ -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>
   
  
  
  
  1.5       +5 -5      LFS/BOOK/chapter06/pwdgroup.xml
  
  Index: pwdgroup.xml
  ===================================================================
  RCS file: /home/cvsroot/LFS/BOOK/chapter06/pwdgroup.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- pwdgroup.xml	28 Sep 2002 21:08:29 -0000	1.4
  +++ pwdgroup.xml	30 Jan 2003 05:06:58 -0000	1.5
  @@ -34,11 +34,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>
   
  
  
  
  1.28      +2 -2      LFS/BOOK/chapter06/utillinux-inst.xml
  
  Index: utillinux-inst.xml
  ===================================================================
  RCS file: /home/cvsroot/LFS/BOOK/chapter06/utillinux-inst.xml,v
  retrieving revision 1.27
  retrieving revision 1.28
  diff -u -r1.27 -r1.28
  --- utillinux-inst.xml	17 Jan 2003 04:42:53 -0000	1.27
  +++ utillinux-inst.xml	30 Jan 2003 05:06:58 -0000	1.28
  @@ -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} &&
   sed 's%etc/adjtime%var/lib/hwclock/adjtime%' \
  
  
  
  1.12      +1 -1      LFS/BOOK/entities/man.ent
  
  Index: man.ent
  ===================================================================
  RCS file: /home/cvsroot/LFS/BOOK/entities/man.ent,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- man.ent	17 Jan 2003 13:18:27 -0000	1.11
  +++ man.ent	30 Jan 2003 05:06:58 -0000	1.12
  @@ -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">
   
  
  
  
-- 
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe lfs-book' in the subject header of the message



More information about the lfs-book mailing list