Changeset bbdb0ff4 for postlfs


Ignore:
Timestamp:
05/30/2005 08:49:04 PM (19 years ago)
Author:
Randy McMurchy <randy@…>
Branches:
10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 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, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
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

Location:
postlfs
Files:
4 edited

Legend:

Unmodified
Added
Removed
  • postlfs/config/inputrc.xml

    r4ff86b9 rbbdb0ff4  
    3939  file.  A later page sets up <application>Bash</application> to use
    4040  <filename>/etc/inputrc</filename> if there is no <filename>.inputrc</filename>
    41   for a user when   <filename>/etc/profile</filename> is read (usually at login). 
     41  for a user when   <filename>/etc/profile</filename> is read (usually at login).
    4242  If you   want your system to use both, or don't want <emphasis>global</emphasis>
    4343  keyboard handling, it is a good idea to place a default
  • postlfs/config/logon.xml

    r4ff86b9 rbbdb0ff4  
    2929  which will also accept certain Escape sequences (see below) in order to
    3030  insert information about the system.  There is also the file
    31   <filename>issue.net</filename> which can be used when logging on remotely. 
     31  <filename>issue.net</filename> which can be used when logging on remotely.
    3232  <command>ssh</command> however, will only use it if you set the option in the
    3333  configuration file and will also <emphasis>not</emphasis> interpret the
     
    3737  the screen at each logon.  The easiest way of doing that is to put a "clear"
    3838  escape-sequence into <filename>/etc/issue</filename>.  A simple way of
    39   doing this is to do <command>clear &gt; /etc/issue</command>. 
     39  doing this is to do <command>clear &gt; /etc/issue</command>.
    4040  This will insert the relevant escape code into the start of the
    4141  <filename>/etc/issue</filename> file.  Note that if you do this, when you
  • postlfs/config/vimrc.xml

    r4ff86b9 rbbdb0ff4  
    3737  <filename>/etc/vimrc</filename> and <filename>~/.vimrc</filename> (i.e., the
    3838  global <filename>vimrc</filename> and the user-specific one.).  Note that this is
    39   only true if you compiled <application>vim</application> using LFS-3.1 onwards. 
     39  only true if you compiled <application>vim</application> using LFS-3.1 onwards.
    4040  Prior to this, the global <filename>vimrc</filename> was
    4141  <filename>/usr/share/vim/vimrc</filename>.</para>
  • postlfs/security/firewalling.xml

    r4ff86b9 rbbdb0ff4  
    7171      <title><xref linkend="fw-masqRouter"/></title>
    7272
    73       <para>This is a system placed between the Internet and an intranet. 
     73      <para>This is a system placed between the Internet and an intranet.
    7474      To minimize the risk of compromising the firewall itself, it should
    75       generally have only one role&mdash;that of protecting the intranet. 
    76       Although not completely risk free, the tasks of doing the routing and 
     75      generally have only one role&mdash;that of protecting the intranet.
     76      Although not completely risk free, the tasks of doing the routing and
    7777      IP masquerading (rewriting IP headers of the packets it routes from
    7878      clients with private IP addresses onto the Internet so that they seem
     
    159159
    160160    <note>
    161       <para>You should always run your firewall rules from a script. 
     161      <para>You should always run your firewall rules from a script.
    162162      This ensures consistency and a record of what was done. It also
    163163      allows retention of comments that are essential for understanding
     
    419419
    420420      <para>If you want to add services such as internal samba or
    421       name servers that do not need to access the Internet themselves, 
     421      name servers that do not need to access the Internet themselves,
    422422      the additional statements are quite simple and should still be
    423423      acceptable from a security standpoint. Just add the following lines
     
    506506          <para>There are other addresses that you may also want to
    507507          drop: 0.0.0.0/8, 127.0.0.0/8, 224.0.0.0/3 (multicast and
    508           experimental), 169.254.0.0/16 (Link Local Networks), and 
     508          experimental), 169.254.0.0/16 (Link Local Networks), and
    509509          192.0.2.0/24 (IANA defined test network).</para>
    510510        </listitem>
Note: See TracChangeset for help on using the changeset viewer.