Changeset bbdb0ff4

Timestamp:

05/30/2005 08:49:04 PM (18 years ago)

Author:

Randy McMurchy <randy@…>

Branches:

10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 6.1, 6.2, 6.2.0, 6.2.0-rc1, 6.2.0-rc2, 6.3, 6.3-rc1, 6.3-rc2, 6.3-rc3, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, ken/inkscape-core-mods, krejzi/svn, lazarus, nosym, perl-modules, plabs/python-mods, qt5new, systemd-11177, systemd-13485, trunk, upgradedb, xry111/intltool, xry111/soup3, xry111/test-20220226

Children:

b2782389

Parents:

4ff86b9

Message:

Removed excess multiple spaces from the ends of lines

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@4493 af4574ff-66df-0310-9fd7-8a98e5e911e0

Files:

• basicnet/netprogs/ncftp.xml (modified) (1 diff)
• basicnet/netprogs/portmap.xml (modified) (1 diff)
• basicnet/textweb/textweb.xml (modified) (1 diff)
• book/preface.xml (modified) (1 diff)
• connect/dhcp/dhcp-client.xml (modified) (1 diff)
• connect/other/other.xml (modified) (1 diff)
• general/genutils/imagemagick.xml (modified) (1 diff)
• general/prog/jdk.xml (modified) (1 diff)
• introduction/welcome/contact.xml (modified) (1 diff)
• multimedia/audioutils/freetts.xml (modified) (2 diffs)
• postlfs/config/inputrc.xml (modified) (1 diff)
• postlfs/config/logon.xml (modified) (2 diffs)
• postlfs/config/vimrc.xml (modified) (1 diff)
• postlfs/security/firewalling.xml (modified) (4 diffs)

basicnet/netprogs/ncftp.xml

@@ -63 +63 @@
     <title>Installation of NcFTP</title>
 
-    <para>There are two ways to build <application>NcFTP</application>.  
+    <para>There are two ways to build <application>NcFTP</application>.
     The first (and optimal) way builds most of the functionality as a shared library 
     and then builds and installs the program linked against this library.  The 
     second method simply links all of the functionality into the binary statically. 
-    This doesn't make the dynamic library available for linking by other applications.  
+    This doesn't make the dynamic library available for linking by other applications.
     You need to choose which method best suits you.  Note that the second method 
     does <emphasis>not</emphasis> create an entirely statically linked binary; 

basicnet/netprogs/portmap.xml

@@ -31 +31 @@
 
     <para>The <application>portmap</application> package is a more secure 
-    replacement for the original SUN <application>portmap</application> package.  
+    replacement for the original SUN <application>portmap</application> package.
     <application>Portmap</application> is used to forward RPC requests to RPC 
     daemons such as NFS and NIS.</para>

basicnet/textweb/textweb.xml

@@ -14 +14 @@
   earth would I want a text-mode browser?  I'm going to compile 
   <application>X</application> and use
-  <application>Konqueror</application>/<application>Mozilla</application>/Whatever!".  
+  <application>Konqueror</application>/<application>Mozilla</application>/Whatever!".
   Those who have been around systems for a while
   know that when (not if) you manage to mess up your graphical browser install

book/preface.xml

@@ -233 +233 @@
     <bridgehead renderas="sect2">Part XI - X Software</bridgehead>
 
-    <para>Office programs and graphical web browsers are important to most people.  
+    <para>Office programs and graphical web browsers are important to most people.
     They, along with some generic <application>X</application> software can be 
     found in this part of the book.</para>

connect/dhcp/dhcp-client.xml

@@ -23 +23 @@
   both a client (<command>dhclient</command>) and a server program for 
   using DHCP.  If you want to install this package, 
-  the instructions can be found at <xref linkend="dhcp"/>.  
+  the instructions can be found at <xref linkend="dhcp"/>.
   Note that if you only want to use the client, you 
   do <emphasis>not</emphasis> need to run the server and so do not need 

connect/other/other.xml

@@ -12 +12 @@
 
   <para>Other methods to connect to large networks are through ISDN
-  and PPPoE interfaces, among others. PPPoE is discussed here.  
+  and PPPoE interfaces, among others. PPPoE is discussed here.
   Pages written for ISDN (or others as the need arises) are always welcome 
   and will be included in future books, if available.</para>

general/genutils/imagemagick.xml

@@ -142 +142 @@
     <application>Libtool</application> library in 
     <filename class='directory'>/usr/lib</filename>. This command forces the 
-    package to link to the installed version of  
+    package to link to the installed version of
     <filename class='libraryfile'>libltdl</filename>, and not replace it.</para>
 

general/prog/jdk.xml

@@ -54 +54 @@
     will still need to download the binary version to bootstrap the 
     <application>JDK</application> build.  You will need to download a total of four 
-    files to complete the source build:  
+    files to complete the source build:
     <filename>jdk-1_5_0_02-linux-i586.bin</filename>; 
     <filename>jdk-1_5_0-src-jrl.zip</filename>; 

introduction/welcome/contact.xml

@@ -20 +20 @@
   the available mailing lists.</para>
 
-  <para>The current BLFS maintainer is &maintainer-fullname;.  
+  <para>The current BLFS maintainer is &maintainer-fullname;.
   If you need to reach &maintainer-firstname;, send an email to
   <ulink url="mailto:&maintainer-address;">&maintainer-address;</ulink>.</para>

multimedia/audioutils/freetts.xml

@@ -192 +192 @@
     <para>Test the installation using the following command:</para>
 
-<screen><userinput>java -jar /opt/freetts/lib/freetts.jar \     
+<screen><userinput>java -jar /opt/freetts/lib/freetts.jar \
     -text "This is a test of the FreeTTS speech synthesis system"</userinput></screen>
 
@@ -199 +199 @@
     as shown below:</para>
 
-<screen><userinput>java -jar /opt/freetts/lib/freetts.jar -streaming \           
+<screen><userinput>java -jar /opt/freetts/lib/freetts.jar -streaming \
     -text "This is a test of the FreeTTS speech synthesis system"</userinput></screen>
 

postlfs/config/inputrc.xml

@@ -39 +39 @@
   file.  A later page sets up <application>Bash</application> to use
   <filename>/etc/inputrc</filename> if there is no <filename>.inputrc</filename>
-  for a user when   <filename>/etc/profile</filename> is read (usually at login).  
+  for a user when   <filename>/etc/profile</filename> is read (usually at login).
   If you   want your system to use both, or don't want <emphasis>global</emphasis>
   keyboard handling, it is a good idea to place a default

postlfs/config/logon.xml

@@ -29 +29 @@
   which will also accept certain Escape sequences (see below) in order to
   insert information about the system.  There is also the file
-  <filename>issue.net</filename> which can be used when logging on remotely.  
+  <filename>issue.net</filename> which can be used when logging on remotely.
   <command>ssh</command> however, will only use it if you set the option in the 
   configuration file and will also <emphasis>not</emphasis> interpret the 
@@ -37 +37 @@
   the screen at each logon.  The easiest way of doing that is to put a "clear" 
   escape-sequence into <filename>/etc/issue</filename>.  A simple way of 
-  doing this is to do <command>clear &gt; /etc/issue</command>.  
+  doing this is to do <command>clear &gt; /etc/issue</command>.
   This will insert the relevant escape code into the start of the
   <filename>/etc/issue</filename> file.  Note that if you do this, when you 

postlfs/config/vimrc.xml

@@ -37 +37 @@
   <filename>/etc/vimrc</filename> and <filename>~/.vimrc</filename> (i.e., the 
   global <filename>vimrc</filename> and the user-specific one.).  Note that this is
-  only true if you compiled <application>vim</application> using LFS-3.1 onwards.  
+  only true if you compiled <application>vim</application> using LFS-3.1 onwards.
   Prior to this, the global <filename>vimrc</filename> was 
   <filename>/usr/share/vim/vimrc</filename>.</para>

postlfs/security/firewalling.xml

@@ -71 +71 @@
       <title><xref linkend="fw-masqRouter"/></title>
 
-      <para>This is a system placed between the Internet and an intranet.  
+      <para>This is a system placed between the Internet and an intranet.
       To minimize the risk of compromising the firewall itself, it should 
-      generally have only one role&mdash;that of protecting the intranet.  
-      Although not completely risk free, the tasks of doing the routing and  
+      generally have only one role&mdash;that of protecting the intranet.
+      Although not completely risk free, the tasks of doing the routing and
       IP masquerading (rewriting IP headers of the packets it routes from 
       clients with private IP addresses onto the Internet so that they seem 
@@ -159 +159 @@
 
     <note>
-      <para>You should always run your firewall rules from a script.  
+      <para>You should always run your firewall rules from a script.
       This ensures consistency and a record of what was done. It also 
       allows retention of comments that are essential for understanding 
@@ -419 +419 @@
 
       <para>If you want to add services such as internal samba or 
-      name servers that do not need to access the Internet themselves,  
+      name servers that do not need to access the Internet themselves,
       the additional statements are quite simple and should still be 
       acceptable from a security standpoint. Just add the following lines
@@ -506 +506 @@
           <para>There are other addresses that you may also want to 
           drop: 0.0.0.0/8, 127.0.0.0/8, 224.0.0.0/3 (multicast and 
-          experimental), 169.254.0.0/16 (Link Local Networks), and  
+          experimental), 169.254.0.0/16 (Link Local Networks), and
           192.0.2.0/24 (IANA defined test network).</para>
         </listitem>