Changeset 8c50f0e for final-system/common

Timestamp:

Feb 21, 2006, 2:28:50 AM (19 years ago)

Author:

Jim Gifford <clfs@…>

Children:

7119f7d0

Parents:

e63113c

Message:

r1169@server (orig r1167): chris | 2006-02-11 19:55:38 -0800
Various text updates

Location:

final-system/common

Files:

• gzip.xml (modified) (1 diff)
• introduction.xml (modified) (1 diff)
• pkgmgt.xml (modified) (4 diffs)
• testsuitesagain.xml (modified) (1 diff)
• udev.xml (modified) (1 diff)
• zlib.xml (modified) (1 diff)

final-system/common/gzip.xml

@@ -67 +67 @@
 <screen os="j"><userinput>mv -v /usr/bin/gzip /bin
 rm -v /usr/bin/{gunzip,zcat}
-ln -sv gzip /bin/gunzip
-ln -sv gzip /bin/zcat
-ln -sv gzip /bin/compress
+ln -sv gzip /bin/{gunzip,zcat,compress}
 ln -sv gunzip /bin/uncompress</userinput></screen>
 

final-system/common/introduction.xml

@@ -58 +58 @@
   the package installs.</para>
 
-  <para os="e">To keep track of which package installs particular files, a package
-  manager can be used. For a general overview of different styles of package
-  managers, please refer to <ulink
-  url="&blfs-root;view/svn/introduction/important.html"/>.
-  For a package management method specifically geared towards LFS, we
-  recommend <ulink url="&hints-root;more_control_and_pkg_man.txt"/>.</para>
-
-<!--  <note os="f">
-    <para>The remainder of this book is to be performed while logged
-    in as user <systemitem class="username">root</systemitem> and no longer
-    as user <systemitem class="username">lfs</systemitem>.</para>
-  </note> -->
+  <para os="e">To keep track of which package installs particular files, a
+  package manager can be used. For a general overview of different styles of
+  package managers, please take a look at the next page.</para>
 
 </sect1>

final-system/common/pkgmgt.xml

@@ -20 +20 @@
   issues that may arise when upgrading packages.</para>
 
-  <para>Some reasons why no package manager is mentioned in LFS or BLFS
-  include:</para>
+  <para>Some reasons why no specific package manager is recommended in LFS or
+  BLFS include:</para>
 
   <itemizedlist>
@@ -31 +31 @@
     <listitem>
       <para>There are multiple solutions for package management, each having
-      its strengths and drawbacks.  Including one that satisfies all audiences
+      its strengths and drawbacks. Including one that satisfies all audiences
       is difficult.</para>
     </listitem>
@@ -39 +39 @@
   the <ulink url="&hints-root;">Hints subproject</ulink> and see if one of them
   fits your need.</para>
-
-  <note>
-    <para>As no particular package management technique is mentioned in LFS,
-    the commands in the remainder of this book must be performed while logged in
-    as user <systemitem class="username">root</systemitem> and no longer as user
-    <systemitem class="username">lfs</systemitem>. Also, double check that
-    <envar>$LFS</envar> is set.</para>
-  </note>
 
   <sect2>
@@ -60 +52 @@
         <para>If one of the toolchain packages (Glibc, GCC or Binutils) needs
         to be upgraded to a newer minor version, it is safer to rebuild LFS.
-        Though you <emphasis>may</emphasis> be able to get by rebuilding all
+        Though, you <emphasis>may</emphasis> be able to get by rebuilding all
         the packages in their dependency order, we do not recommend it. For
         example, if glibc-2.2.x needs to be updated to glibc-2.3.x, it is safer

final-system/common/testsuitesagain.xml

@@ -25 +25 @@
   <systemitem class="filesystem">devpts</systemitem> file system set up
   correctly. This issue is discussed in greater detail at
-  <ulink url="http://www.linuxfromscratch.org/lfs/faq.html#no-ptys"/>.</para>
+  <ulink url="&faq-root;#no-ptys"/>.</para>
 
   <para>Sometimes package test suites will fail, but for reasons which the

final-system/common/udev.xml

@@ -80 +80 @@
 
     <para os="j">Udev's configuration is far from ideal by default, so install
-    the configuration files here:</para>
+    the configuration file here:</para>
 
 <screen os="k"><userinput>cp -v ../&udev-config-file; /etc/udev/rules.d/25-lfs.rules</userinput></screen>

final-system/common/zlib.xml

@@ -50 +50 @@
     <userinput>make check</userinput>.</para>
 
-    <para os="f">Installation:</para>
+    <para os="f">Install the package:</para>
 
 <screen os="g"><userinput>make install</userinput></screen>