Changeset e0d33ef


Ignore:
Timestamp:
05/30/2005 09:56:30 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:
3aa07d1
Parents:
f009801
Message:

Removed excess spaces from the ends of lines in the source files

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

Location:
postlfs/config
Files:
10 edited

Legend:

Unmodified
Added
Removed

  • postlfs/config/autofs.xml

    rf009801 re0d33ef  
    3232    <para>The <application>autofs</application> package contains userspace
    3333    tools that work with the kernel to mount and un-mount removable file
    34     systems. This is useful for allowing users to mount floppies, cdroms and 
     34    systems. This is useful for allowing users to mount floppies, cdroms and
    3535    other removable storage devices without requiring the system
    36     administrator to mount the devices.  This may not be ideal for all 
     36    administrator to mount the devices.  This may not be ideal for all
    3737    installations, so be aware of the risks before implementing this feature.</para>
    3838
    … …  
    121121    <title>Installation of Autofs</title>
    122122
    123     <para>Install <application>autofs</application> by running the following 
     123    <para>Install <application>autofs</application> by running the following
    124124    commands:</para>
    125125
    … …  
    202202      </note>
    203203
    204       <para>While this package could be used to mount NFS shares and SMB 
    205       shares, that feature is not configured in these instructions. NFS shares 
     204      <para>While this package could be used to mount NFS shares and SMB
     205      shares, that feature is not configured in these instructions. NFS shares
    206206      are covered on the next page.</para>
    207207
    … …  
    209209      working hardware. The loaded configuration file should load your cdrom
    210210      if <filename>/dev/cdrom</filename> is active or it can be edited to
    211       match your device setup and examples for floppies are available in the file 
     211      match your device setup and examples for floppies are available in the file
    212212      and easily activated. Documentation for this file is available using the
    213213      <command>man 5 autofs</command> command.</para>
    … …  
    219219
    220220
    221       <para>Install the <filename>/etc/rc.d/init.d/autofs</filename> mount script 
    222       and <filename>/etc/sysconfig/autofs.conf</filename> support file included 
     221      <para>Install the <filename>/etc/rc.d/init.d/autofs</filename> mount script
     222      and <filename>/etc/sysconfig/autofs.conf</filename> support file included
    223223      with the <xref linkend="intro-important-bootscripts"/> package.</para>
    224224
    … …  
    232232      <filename>/etc/sysconfig/autofs.conf</filename>. The installed file sets
    233233      a default of 60 seconds of inactivity before unmounting the device.  A
    234       much shorter time may be necessary to protect buffer writing to a floppy 
     234      much shorter time may be necessary to protect buffer writing to a floppy
    235235      if users tend to remove the media prior to the timeout setting.</para>
    236236
    … …  
    262262        <term><command>automount</command></term>
    263263        <listitem>
    264           <para>is the daemon that performs the mounting when a request is 
     264          <para>is the daemon that performs the mounting when a request is
    265265          made for the device.</para>
    266266          <indexterm zone="autofs automount">

  • postlfs/config/compressdoc.xml

    rf009801 re0d33ef  
    2323  bzip2'ed pages, a feature you can use to free some disk space while keeping
    2424  your documentation available. However, things are not that simple; man
    25   directories tend to contain links&mdash;hard and symbolic&mdash;which defeat 
    26   simple ideas like recursively calling <command>gzip</command> on them. A 
     25  directories tend to contain links&mdash;hard and symbolic&mdash;which defeat
     26  simple ideas like recursively calling <command>gzip</command> on them. A
    2727  better way to go is to use the script below.</para>
    2828
    … …  
    4343# to allow for a backup, to allow to keep the newest version of a page.
    4444#
    45 # Modified 20040330 by Tushar Teredesai to replace $0 by the name of the 
     45# Modified 20040330 by Tushar Teredesai to replace $0 by the name of the
    4646# script.
    4747#   (Note: It is assumed that the script is in the user's PATH)
    … …  
    5353#     - choose a default compress method to be based on the available
    5454#       tool : gzip or bzip2;
    55 #     - offer an option to automagically choose the best compression 
    56 #       methed on a per page basis (eg. check which of 
     55#     - offer an option to automagically choose the best compression
     56#       methed on a per page basis (eg. check which of
    5757#       gzip/bzip2/whatever is the most effective, page per page);
    5858#     - when a MANPATH env var exists, use this instead of /etc/man.conf
    … …  
    7878
    7979  --backup      Specify a .tar backup shall be done for all directories.
    80                 In case a backup already exists, it is saved as .tar.old 
    81                 prior to making the new backup. If a .tar.old backup 
     80                In case a backup already exists, it is saved as .tar.old
     81                prior to making the new backup. If a .tar.old backup
    8282                exists, it is removed prior to saving the backup.
    8383                In backup mode, no other action is performed.
    … …  
    8585And where options are :
    8686  -1 to -9, --fast, --best
    87                 The compression level, as accepted by gzip and bzip2. 
    88                 When not specified, uses the default compression level 
    89                 for the given method (-6 for gzip, and -9 for bzip2). 
     87                The compression level, as accepted by gzip and bzip2.
     88                When not specified, uses the default compression level
     89                for the given method (-6 for gzip, and -9 for bzip2).
    9090                Not used when in backup or decompress modes.
    9191
    92   --force, -F   Force (re-)compression, even if the previous one was 
    93                 the same method. Useful when changing the compression 
    94                 ratio. By default, a page will not be re-compressed if 
    95                 it ends with the same suffix as the method adds 
     92  --force, -F   Force (re-)compression, even if the previous one was
     93                the same method. Useful when changing the compression
     94                ratio. By default, a page will not be re-compressed if
     95                it ends with the same suffix as the method adds
    9696                (.bz2 for bzip2, .gz for gzip).
    9797
    98   --soft, -S    Change hard-links into soft-links. Use with _caution_ 
    99                 as the first encountered file will be used as a 
     98  --soft, -S    Change hard-links into soft-links. Use with _caution_
     99                as the first encountered file will be used as a
    100100                reference. Not used when in backup mode.
    101101
    102   --hard, -H    Change soft-links into hard-links. Not used when in 
     102  --hard, -H    Change soft-links into hard-links. Not used when in
    103103                backup mode.
    104104
    … …  
    106106                Specify the location of man.conf. Defaults to /etc.
    107107
    108   --verbose, -v Verbose mode, print the name of the directory being 
    109                 processed. Double the flag to turn it even more verbose, 
     108  --verbose, -v Verbose mode, print the name of the directory being
     109                processed. Double the flag to turn it even more verbose,
    110110                and to print the name of the file being processed.
    111111
    112112  --fake, -f    Fakes it. Print the actual parameters compman will use.
    113113
    114   dirs          A list of space-separated _absolute_ pathnames to the 
    115                 man directories. When empty, and only then, parse 
     114  dirs          A list of space-separated _absolute_ pathnames to the
     115                man directories. When empty, and only then, parse
    116116                ${MAN_CONF}/man.conf for all occurrences of MANPATH.
    117117
    … …  
    120120  both gzip and bzip2 on man pages, taking into account the hosting fs,
    121121  the architecture, etc... On the overall, the conclusion was that gzip
    122   was much more efficient on 'small' files, and bzip2 on 'big' files, 
     122  was much more efficient on 'small' files, and bzip2 on 'big' files,
    123123  small and big being very dependent on the content of the files.
    124124
    125   See the original post from Mickael A. Peters, titled 
     125  See the original post from Mickael A. Peters, titled
    126126  "Bootable Utility CD", dated 20030409.1816(+0200), and subsequent posts:
    127127  http://linuxfromscratch.org/pipermail/blfs-support/2003-April/038817.html
    128128
    129   On my system (x86, ext3), man pages were 35564KB before compression. 
    130   gzip -9 compressed them down to 20372KB (57.28%), bzip2 -9 got down to 
     129  On my system (x86, ext3), man pages were 35564KB before compression.
     130  gzip -9 compressed them down to 20372KB (57.28%), bzip2 -9 got down to
    131131  19812KB (55.71%). That is a 1.57% gain in space. YMMV.
    132132
    133   What was not taken into consideration was the decompression speed. But 
    134   does it make sense to? You gain fast access with uncompressed man 
    135   pages, or you gain space at the expense of a slight overhead in time. 
     133  What was not taken into consideration was the decompression speed. But
     134  does it make sense to? You gain fast access with uncompressed man
     135  pages, or you gain space at the expense of a slight overhead in time.
    136136  Well, my P4-2.5GHz does not even let me notice this... :-)
    137137
    … …  
    140140}
    141141
    142 # This function checks that the man page is unique amongst bzip2'd, 
     142# This function checks that the man page is unique amongst bzip2'd,
    143143# gzip'd and uncompressed versions.
    144144#  $1 the directory in which the file resides
    145145#  $2 the file name for the man page
    146 # Returns 0 (true) if the file is the latest and must be taken care of, 
    147 # and 1 (false) if the file is not the latest (and has therefore been 
     146# Returns 0 (true) if the file is the latest and must be taken care of,
     147# and 1 (false) if the file is not the latest (and has therefore been
    148148# deleted).
    149149function check_unique ()
    … …  
    177177MY_NAME=`basename $0`
    178178
    179 # OK, parse the command-line for arguments, and initialize to some 
    180 # sensible state, that is: don't change links state, parse 
    181 # /etc/man.conf, be most silent, search man.conf in /etc, and don't 
     179# OK, parse the command-line for arguments, and initialize to some
     180# sensible state, that is: don't change links state, parse
     181# /etc/man.conf, be most silent, search man.conf in /etc, and don't
    182182# force (re-)compression.
    183183COMP_METHOD=
    … …  
    258258      ;;
    259259    *)
    260       echo "\"$1\" is not an absolute path name" 
     260      echo "\"$1\" is not an absolute path name"
    261261      exit 1
    262262      ;;
    … …  
    286286esac
    287287
    288 # Note: on my machine, 'man --path' gives /usr/share/man twice, once 
     288# Note: on my machine, 'man --path' gives /usr/share/man twice, once
    289289# with a trailing '/', once without.
    290290if [ -z "$MAN_DIR" ]; then
    … …  
    319319  echo "man.conf is.......: ${MAN_CONF}/man.conf"
    320320  echo -n "Hard-links........: "
    321   [ "foo$LN_OPT" = "foo-S" ] &amp;&amp; 
     321  [ "foo$LN_OPT" = "foo-S" ] &amp;&amp;
    322322  echo "convert to soft-links" || echo "leave as is"
    323323  echo -n "Soft-links........: "
    324   [ "foo$LN_OPT" = "foo-H" ] &amp;&amp; 
     324  [ "foo$LN_OPT" = "foo-H" ] &amp;&amp;
    325325  echo "convert to hard-links" || echo "leave as is"
    326326  echo "Backup............: $BACKUP"
    … …  
    344344    echo "Backing up $DIR..." &gt; $DEST_FD0
    345345    [ -f "${DIR_NAME}.tar.old" ] &amp;&amp; rm -f "${DIR_NAME}.tar.old"
    346     [ -f "${DIR_NAME}.tar" ] &amp;&amp; 
     346    [ -f "${DIR_NAME}.tar" ] &amp;&amp;
    347347    mv "${DIR_NAME}.tar" "${DIR_NAME}.tar.old"
    348348    tar -cfv "${DIR_NAME}.tar" "${DIR_NAME}" &gt; $DEST_FD1
    … …  
    361361
    362362    # Fixes the case when hard-links see their compression scheme change
    363     # (from not compressed to compressed, or from bz2 to gz, or from gz 
     363    # (from not compressed to compressed, or from bz2 to gz, or from gz
    364364    # to bz2)
    365     # Also fixes the case when multiple version of the page are present, 
     365    # Also fixes the case when multiple version of the page are present,
    366366    # which are either compressed or not.
    367367    if [ ! -L "$FILE" -a ! -e "$FILE" ]; then continue; fi
    … …  
    371371
    372372    if [ -d "$FILE" ]; then
    373       cd "${MEM_DIR}"  # Go back to where we ran "$0", 
     373      cd "${MEM_DIR}"  # Go back to where we ran "$0",
    374374                       # in case "$0"=="./compressdoc" ...
    375375      # We are going recursive to that directory
    … …  
    426426        # Take care of hard-links: build the list of files hard-linked
    427427        # to the one we are {de,}compressing.
    428         # NB. This is not optimum has the file will eventually be 
    429         # compressed as many times it has hard-links. But for now, 
     428        # NB. This is not optimum has the file will eventually be
     429        # compressed as many times it has hard-links. But for now,
    430430        # that's the safe way.
    431431        inode=`ls -li "$FILE" | awk '{print $1}'`
    … …  
    483483
    484484      else
    485         # There is a problem when we get neither a symlink nor a plain 
     485        # There is a problem when we get neither a symlink nor a plain
    486486        # file. Obviously, we shall never ever come here... :-(
    487487        echo -n "Whaooo... \"${DIR}/${FILE}\" is neither a symlink "
    … …  
    497497chmod 755 /usr/sbin/compressdoc</userinput></screen>
    498498
    499   <para>Now, as <systemitem class="username">root</systemitem>, you can issue a 
    500   <command>compressdoc --bz2</command> to compress all your system man 
    501   pages. You can also run <command>compressdoc --help</command> to get 
     499  <para>Now, as <systemitem class="username">root</systemitem>, you can issue a
     500  <command>compressdoc --bz2</command> to compress all your system man
     501  pages. You can also run <command>compressdoc --help</command> to get
    502502  comprehensive help about what the script is able to do.</para>
    503503
    504   <para> Don't forget that a few programs, like the <application>X Window 
    505   System</application>  and <application>XEmacs</application> also 
    506   install their documentation in non standard places (such as 
    507   <filename class="directory">/usr/X11R6/man</filename>, etc...). Be sure 
    508   to add these locations to the file <filename>/etc/man.conf</filename>, as a 
     504  <para> Don't forget that a few programs, like the <application>X Window
     505  System</application>  and <application>XEmacs</application> also
     506  install their documentation in non standard places (such as
     507  <filename class="directory">/usr/X11R6/man</filename>, etc...). Be sure
     508  to add these locations to the file <filename>/etc/man.conf</filename>, as a
    509509  <envar>MANPATH</envar>=<replaceable>[/path]</replaceable> section.</para>
    510510
    … …  
    518518    ...</literal></screen>
    519519
    520   <para>Generally, package installation systems do not compress man/info pages, 
    521   which means you will need to run the script again if you want to keep the size 
     520  <para>Generally, package installation systems do not compress man/info pages,
     521  which means you will need to run the script again if you want to keep the size
    522522  of your documentation as small as possible. Also, note that running the script
    523   after upgrading a package is safe; when you have several versions of a page 
     523  after upgrading a package is safe; when you have several versions of a page
    524524  (for example, one compressed and one uncompressed), the most recent one is kept
    525525  and the others deleted.</para>

  • postlfs/config/config.xml

    rf009801 re0d33ef  
    1111  <title>After LFS Configuration Issues</title>
    1212
    13   <para>The intention of LFS is to provide a basic system which you can 
    14   build upon.  There are several things, about tidying up the system, which 
     13  <para>The intention of LFS is to provide a basic system which you can
     14  build upon.  There are several things, about tidying up the system, which
    1515  many people wonder about once they have done the base install.
    1616  We hope to cover these issues in this chapter.</para>
    1717
    1818  <para>Most people coming from non-Unix like backgrounds to Linux find the
    19   concept of text-only configuration files slightly strange.  In Linux, just 
    20   about all configuration is done via text files. The majority of these files 
    21   can be found in the <filename>/etc</filename> hierarchy. There are often 
    22   graphical configuration programs available for different subsystems but most 
    23   are simply pretty front ends to the process of editing the file. The advantage 
    24   of text-only configuration is that you can edit parameters using your favorite 
    25   text editor, whether that be <command>vim</command>, 
     19  concept of text-only configuration files slightly strange.  In Linux, just
     20  about all configuration is done via text files. The majority of these files
     21  can be found in the <filename>/etc</filename> hierarchy. There are often
     22  graphical configuration programs available for different subsystems but most
     23  are simply pretty front ends to the process of editing the file. The advantage
     24  of text-only configuration is that you can edit parameters using your favorite
     25  text editor, whether that be <command>vim</command>,
    2626  <command>emacs</command>, or anything else.</para>
    2727
    … …  
    2929  critical need. Then the system is configured to ease addition of
    3030  new users, in <xref linkend="postlfs-config-bootdisk"/>, because this
    31   can affect the choices you make in the two subsequent topics&mdash;<xref 
     31  can affect the choices you make in the two subsequent topics&mdash;<xref
    3232  linkend="postlfs-config-profile"/> and <xref linkend="postlfs-config-vimrc"/>.</para>
    3333
    34   <para> The remaining topics, <xref linkend="postlfs-config-logon"/>, 
    35   <xref linkend="postlfs-config-shells"/>, <xref linkend="postlfs-config-random"/>, 
    36   <xref linkend="compressdoc"/>, <xref linkend="autofs"/>, and 
    37   <xref linkend="postlfs-config-netfs"/> are then addressed, in that order. They 
     34  <para> The remaining topics, <xref linkend="postlfs-config-logon"/>,
     35  <xref linkend="postlfs-config-shells"/>, <xref linkend="postlfs-config-random"/>,
     36  <xref linkend="compressdoc"/>, <xref linkend="autofs"/>, and
     37  <xref linkend="postlfs-config-netfs"/> are then addressed, in that order. They
    3838  don't have much interaction with the other topics in this chapter.</para>
    3939

  • postlfs/config/etcshells.xml

    rf009801 re0d33ef  
    2020  </indexterm>
    2121
    22   <para>The <filename>shells</filename> file contains a list of 
     22  <para>The <filename>shells</filename> file contains a list of
    2323  login shells on the system. Applications use this file to determine
    2424  whether a shell is valid. For each shell a single line should be
    … …  
    3131
    3232  <para>It is a requirement for applications such as
    33   <application>GDM</application> which does not populate the 
    34   face browser if it can't find <filename>/etc/shells</filename> or 
    35   FTP daemons which traditionally disallow access to users 
     33  <application>GDM</application> which does not populate the
     34  face browser if it can't find <filename>/etc/shells</filename> or
     35  FTP daemons which traditionally disallow access to users
    3636  with shells not included in this file.</para>
    3737

  • postlfs/config/inputrc.xml

    rf009801 re0d33ef  
    2424  </indexterm>
    2525
    26   <para><filename>/etc/inputrc</filename> deals with the mapping of the 
     26  <para><filename>/etc/inputrc</filename> deals with the mapping of the
    2727  keyboard for certain situations.  This file is the start-up file used by
    28   <application>readline</application>, the input related library used by 
     28  <application>readline</application>, the input related library used by
    2929  <application>bash</application> and most other shells.</para>
    3030
    3131  <para>For more information see <command>info bash</command>&mdash;<emphasis
    3232  role="strong">Node: Readline Init</emphasis> file as well as
    33   <command>info readline</command>. There is a lot that can be done with this 
     33  <command>info readline</command>. There is a lot that can be done with this
    3434  one rc file.</para>
    3535
    … …  
    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
    44   <filename>.inputrc</filename> into the <filename 
     44  <filename>.inputrc</filename> into the <filename
    4545  class="directory">/etc/skel</filename> directory for use with new users.</para>
    4646
    … …  
    5050
    5151  <para>If you will create an <filename>.inputrc</filename> in
    52   <filename class="directory">/etc/skel</filename> using the command below, 
    53   change the command's output to <filename>/etc/skel/.inputrc</filename> and 
     52  <filename class="directory">/etc/skel</filename> using the command below,
     53  change the command's output to <filename>/etc/skel/.inputrc</filename> and
    5454  be sure to check/set permissions afterward. Then you can just copy that
    5555  file to <filename>/etc/inputrc</filename> and the home directory
    56   of any user already existing in the system, including <systemitem 
     56  of any user already existing in the system, including <systemitem
    5757  class="username">root</systemitem>, that needs
    5858  a private version of the file.  Be sure to use the <option>-p</option>
    59   parameter of <command>cp</command> to maintain permissions and be sure to 
     59  parameter of <command>cp</command> to maintain permissions and be sure to
    6060  change owner and group appropriately.</para>
    6161
    … …  
    6767
    6868# Enable 8bit input
    69 set meta-flag On 
     69set meta-flag On
    7070set input-meta On
    7171
    … …  
    7979set bell-style none
    8080
    81 # All of the following map the escape sequence of the 
    82 # value contained inside the 1st argument to the 
     81# All of the following map the escape sequence of the
     82# value contained inside the 1st argument to the
    8383# readline specific functions
    8484

  • postlfs/config/logon.xml

    rf009801 re0d33ef  
    2020  </indexterm>
    2121
    22   <para>When you first boot up your new LFS system, the logon screen will 
    23   be nice and plain (as it should be in a bare-bones system).  Many people 
    24   however, will want their system to display some information in the logon 
    25   message.  This can be accomplished using the 
     22  <para>When you first boot up your new LFS system, the logon screen will
     23  be nice and plain (as it should be in a bare-bones system).  Many people
     24  however, will want their system to display some information in the logon
     25  message.  This can be accomplished using the
    2626  file <filename>/etc/issue</filename>.</para>
    2727
    … …  
    3030  insert information about the system.  There is also the file
    3131  <filename>issue.net</filename> which can be used when logging on remotely.
    32   <command>ssh</command> however, will only use it if you set the option in the 
    33   configuration file and will also <emphasis>not</emphasis> interpret the 
     32  <command>ssh</command> however, will only use it if you set the option in the
     33  configuration file and will also <emphasis>not</emphasis> interpret the
    3434  escape sequences shown below.</para>
    3535
    3636  <para>One of the most common things which people want to do is to clear
    37   the screen at each logon.  The easiest way of doing that is to put a "clear" 
    38   escape-sequence into <filename>/etc/issue</filename>.  A simple way of 
     37  the screen at each logon.  The easiest way of doing that is to put a "clear"
     38  escape-sequence into <filename>/etc/issue</filename>.  A simple way of
    3939  doing this is to do <command>clear &gt; /etc/issue</command>.
    4040  This will insert the relevant escape code into the start of the
    41   <filename>/etc/issue</filename> file.  Note that if you do this, when you 
     41  <filename>/etc/issue</filename> file.  Note that if you do this, when you
    4242  edit the file, you should leave the ^[c character on the first line alone.</para>
    4343
    4444  <para>The following escapes are recognized by <command>agetty</command>
    45   (the program which usually parses <filename>/etc/issue</filename>).  This 
    46   information is from <command>man agetty</command> where you can find 
     45  (the program which usually parses <filename>/etc/issue</filename>).  This
     46  information is from <command>man agetty</command> where you can find
    4747  extra information about the logon process.</para>
    4848
    49   <para>The <filename>issue</filename> file can contain certain escape codes to 
    50   display various information.  All escape codes consist of a backslash (\) 
    51   immediately followed by one of the letters explained below (so 
    52   <option>\d</option> in <filename>/etc/issue</filename> would 
     49  <para>The <filename>issue</filename> file can contain certain escape codes to
     50  display various information.  All escape codes consist of a backslash (\)
     51  immediately followed by one of the letters explained below (so
     52  <option>\d</option> in <filename>/etc/issue</filename> would
    5353  insert the current date).</para>
    5454

  • postlfs/config/netfs.xml

    rf009801 re0d33ef  
    2121  </indexterm>
    2222
    23   <para>While LFS is capable of mounting network file systems such as NFS, 
    24   these are not mounted by the <filename>mountfs</filename> init script. 
    25   Network file systems must be mounted after the networking is activated and 
     23  <para>While LFS is capable of mounting network file systems such as NFS,
     24  these are not mounted by the <filename>mountfs</filename> init script.
     25  Network file systems must be mounted after the networking is activated and
    2626  unmounted before the network goes down.  The <filename>netfs</filename>
    27   bootscript was written to handle both boot-time mounting of network 
    28   filesystems, if the entry in <filename>/etc/fstab</filename> contains the 
    29   <option>_netdev</option> option, and unmounting of all network filesystems 
     27  bootscript was written to handle both boot-time mounting of network
     28  filesystems, if the entry in <filename>/etc/fstab</filename> contains the
     29  <option>_netdev</option> option, and unmounting of all network filesystems
    3030  before the network is brought down.</para>
    3131
    32   <para>As the <systemitem class="username">root</systemitem> user, install 
    33   the <filename>/etc/rc.d/init.d/netfs</filename> bootscript included with the 
     32  <para>As the <systemitem class="username">root</systemitem> user, install
     33  the <filename>/etc/rc.d/init.d/netfs</filename> bootscript included with the
    3434  <xref linkend="intro-important-bootscripts"/> package.</para>
    3535

  • postlfs/config/random.xml

    rf009801 re0d33ef  
    2121
    2222  <para>The Linux kernel supplies a random number generator which is accessed
    23   through <filename class="devicefile">/dev/random</filename> and 
    24   <filename class="devicefile">/dev/urandom</filename>.  Programs that utilize 
    25   the random and urandom devices, such as <application>OpenSSH</application>, 
     23  through <filename class="devicefile">/dev/random</filename> and
     24  <filename class="devicefile">/dev/urandom</filename>.  Programs that utilize
     25  the random and urandom devices, such as <application>OpenSSH</application>,
    2626  will benefit from these instructions.</para>
    2727
    … …  
    3333  start-ups.</para>
    3434
    35   <para>Install the <filename>/etc/rc.d/init.d/random</filename> init script 
     35  <para>Install the <filename>/etc/rc.d/init.d/random</filename> init script
    3636  included with the <xref linkend="intro-important-bootscripts"/> package.</para>
    3737

  • postlfs/config/skel.xml

    rf009801 re0d33ef  
    2525
    2626  <para>Together, the <command>/usr/sbin/useradd</command> command and
    27   <filename class="directory">/etc/skel</filename> directory (both are easy to 
    28   setup and use) provide a way to assure new users are added on your LFS 
    29   system with the same beginning settings for things like <envar>PATH</envar>, 
    30   keyboard processing and environmental variables. Using these two facilities 
     27  <filename class="directory">/etc/skel</filename> directory (both are easy to
     28  setup and use) provide a way to assure new users are added on your LFS
     29  system with the same beginning settings for things like <envar>PATH</envar>,
     30  keyboard processing and environmental variables. Using these two facilities
    3131  makes it easier to assure this initial state for each new user.</para>
    3232
    33   <para>The <filename class="directory">/etc/skel</filename> directory holds 
    34   copies of various initialization and other files that may be copied to the 
     33  <para>The <filename class="directory">/etc/skel</filename> directory holds
     34  copies of various initialization and other files that may be copied to the
    3535  new user's home directory when the <command>/usr/sbin/useradd</command>
    3636  program adds the new user.</para>
    … …  
    4141  default values kept in <filename>/etc/default/useradd</filename>,
    4242  if it exists.  If the file does not exist, then it uses some internal
    43   defaults.  You can see the default values by running 
     43  defaults.  You can see the default values by running
    4444  <command>/usr/sbin/useradd -D</command>.</para>
    4545
    4646  <para>To change these values to something new, create a base <filename>
    47   /etc/default/useradd</filename> file with the same values as the output of 
     47  /etc/default/useradd</filename> file with the same values as the output of
    4848  <command>/usr/sbin/useradd -D</command>.  Here is a sample.</para>
    4949
    … …  
    6464<screen role="root"><userinput>/usr/sbin/useradd -D -s/bin/bash</userinput></screen>
    6565
    66   <para>This will set the <envar>SHELL</envar>= line to 
     66  <para>This will set the <envar>SHELL</envar>= line to
    6767  <envar>SHELL</envar>=/bin/bash.</para>
    6868
    … …  
    7474  <bridgehead renderas="sect5">/etc/skel</bridgehead>
    7575
    76   <para>To get started, create an <filename 
    77   class="directory">/etc/skel</filename> directory and make sure it is 
    78   writable only by the system administrator, usually <systemitem 
    79   class="username">root</systemitem>. Creating the 
    80   directory as <systemitem class="username">root</systemitem> is 
     76  <para>To get started, create an <filename
     77  class="directory">/etc/skel</filename> directory and make sure it is
     78  writable only by the system administrator, usually <systemitem
     79  class="username">root</systemitem>. Creating the
     80  directory as <systemitem class="username">root</systemitem> is
    8181  the best way to go.</para>
    8282
    8383  <para>The mode of any files from this part of the book that you put in
    84   <filename class="directory">/etc/skel</filename> should be writable only by 
    85   the owner. Also, since there is no telling what kind of sensitive information 
     84  <filename class="directory">/etc/skel</filename> should be writable only by
     85  the owner. Also, since there is no telling what kind of sensitive information
    8686  a user may eventually place in their copy of these files, you should
    8787  make them unreadable by "group" and "other".</para>
    8888
    89   <para>You can also put other files in 
     89  <para>You can also put other files in
    9090  <filename class="directory">/etc/skel</filename> and
    9191  different permissions may be needed for them.</para>
    … …  
    9393  <para>Decide which initialization files should be provided in every (or most)
    9494  new user's home directory. The decisions you make will affect what you
    95   do in the next two sections, <xref linkend="postlfs-config-profile"/> and 
     95  do in the next two sections, <xref linkend="postlfs-config-profile"/> and
    9696  <xref linkend="postlfs-config-vimrc"/>. Some or all of those files will be
    97   useful for <systemitem class="username">root</systemitem>, any 
     97  useful for <systemitem class="username">root</systemitem>, any
    9898  already-existing users, and new users.</para>
    9999
    … …  
    108108
    109109  <para>You will run a slightly modified set of commands for files which
    110   are placed in <filename class="directory">/etc/skel</filename>. Each section 
    111   will remind you of this. In brief, the book's commands have been written for 
    112   files <emphasis>not</emphasis> added to 
    113   <filename class="directory">/etc/skel</filename> and just send the results to 
    114   the user's home directory. If the file is going to be in 
    115   <filename class="directory">/etc/skel</filename>, change the book's command(s) 
     110  are placed in <filename class="directory">/etc/skel</filename>. Each section
     111  will remind you of this. In brief, the book's commands have been written for
     112  files <emphasis>not</emphasis> added to
     113  <filename class="directory">/etc/skel</filename> and just send the results to
     114  the user's home directory. If the file is going to be in
     115  <filename class="directory">/etc/skel</filename>, change the book's command(s)
    116116  to send output there instead and then just copy the file from
    117   <filename class="directory">/etc/skel</filename> to the appropriate 
    118   directories, like <filename class="directory">/etc</filename>, 
    119   <filename class="directory">~</filename> or the home directory 
     117  <filename class="directory">/etc/skel</filename> to the appropriate
     118  directories, like <filename class="directory">/etc</filename>,
     119  <filename class="directory">~</filename> or the home directory
    120120  of any other user already in the system.</para>
    121121
    … …  
    125125  the <option>-m</option> parameter, which tells
    126126  <command>useradd</command> to create the user's home directory and
    127   copy files from <filename class="directory">/etc/skel</filename> (can be 
     127  copy files from <filename class="directory">/etc/skel</filename> (can be
    128128  overridden) to the new user's home directory.  For example:</para>
    129129

  • postlfs/config/vimrc.xml

    rf009801 re0d33ef  
    3333  <application>Emacs</application> users!</para>
    3434
    35   <para>The LFS book gives a basic <filename>vimrc</filename> file.  Here, we 
    36   attempt to enhance this file.  At startup, <command>vim</command> reads 
    37   <filename>/etc/vimrc</filename> and <filename>~/.vimrc</filename> (i.e., the 
     35  <para>The LFS book gives a basic <filename>vimrc</filename> file.  Here, we
     36  attempt to enhance this file.  At startup, <command>vim</command> reads
     37  <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
    3939  only true if you compiled <application>vim</application> using LFS-3.1 onwards.
    40   Prior to this, the global <filename>vimrc</filename> was 
     40  Prior to this, the global <filename>vimrc</filename> was
    4141  <filename>/usr/share/vim/vimrc</filename>.</para>
    4242
    43   <para>Here is a slightly expanded <filename>.vimrc</filename> that you can 
    44   put in <filename>~/.vimrc</filename> to provide user specific effects. Of 
    45   course, if you put it into <filename>/etc/skel/.vimrc</filename> instead, it 
     43  <para>Here is a slightly expanded <filename>.vimrc</filename> that you can
     44  put in <filename>~/.vimrc</filename> to provide user specific effects. Of
     45  course, if you put it into <filename>/etc/skel/.vimrc</filename> instead, it
    4646  will be made available to users you add to the system later. You can also copy
    47   the file from <filename>/etc/skel/.vimrc</filename> to the home directory of 
    48   users already on the system, like root. Be sure to set permissions, owner, and 
    49   group if you do copy anything directly from 
     47  the file from <filename>/etc/skel/.vimrc</filename> to the home directory of
     48  users already on the system, like root. Be sure to set permissions, owner, and
     49  group if you do copy anything directly from
    5050  <filename class="directory">/etc/skel</filename>.</para>
    5151
    … …  
    5858" End .vimrc</literal></screen>
    5959
    60   <para>A FAQ on the LFS mailing lists regards the comment tags in 
    61   <filename>vimrc</filename>.  Note that they are " instead of the more 
    62   usual # or //.  This is correct, the syntax for 
     60  <para>A FAQ on the LFS mailing lists regards the comment tags in
     61  <filename>vimrc</filename>.  Note that they are " instead of the more
     62  usual # or //.  This is correct, the syntax for
    6363  <filename>vimrc</filename> is slightly unusual.</para>
    6464
    … …  
    6767
    6868  <itemizedlist>
    69     <!-- 
     69    <!--
    7070    <listitem>
    7171      <para><option>set nocompatible</option> : This option
    … …  
    7676    </listitem>
    7777    <listitem>
    78       <para><option>set bs=2</option>: This influences the behavior 
     78      <para><option>set bs=2</option>: This influences the behavior
    7979      of the backspace option.  It is fairly complex so see <command>:help 'bs'
    8080      </command> for more details.</para>
    … …  
    8282    -->
    8383    <listitem>
    84       <para><option>set columns=80</option>: This simply sets the 
     84      <para><option>set columns=80</option>: This simply sets the
    8585      number of columns used on the screen.</para>
    8686    </listitem>
    87     <!-- 
     87    <!--
    8888    <listitem>
    8989      <para><option>set background=dark</option>: This tells
    90       <command>vim</command> to use colors which look good on a dark 
     90      <command>vim</command> to use colors which look good on a dark
    9191      background.</para>
    9292    </listitem>
    9393    -->
    9494    <listitem>
    95       <para><option>set wrapmargin=8</option>: This is the number of 
     95      <para><option>set wrapmargin=8</option>: This is the number of
    9696      characters from the right window border where wrapping starts.</para>
    9797    </listitem>
    98     <!-- 
     98    <!--
    9999    <listitem>
    100100      <para><option>syntax on</option>: Enables
    … …  
    109109
    110110  <para>More information on the <emphasis>many</emphasis>
    111   <command>vim</command> options can be found by reading the help 
    112   inside <command>vim</command> itself.  Do this by typing 
    113   <command>:</command><option>help</option> in 
    114   <command>vim</command> to get the general help, or by typing 
    115   <command>:</command><option>help usr_toc.txt</option> to view 
     111  <command>vim</command> options can be found by reading the help
     112  inside <command>vim</command> itself.  Do this by typing
     113  <command>:</command><option>help</option> in
     114  <command>vim</command> to get the general help, or by typing
     115  <command>:</command><option>help usr_toc.txt</option> to view
    116116  the User Manual Table of Contents.</para>
    117117
Note: See TracChangeset for help on using the changeset viewer.