Index: postlfs/config/bootdisk.xml
===================================================================
--- postlfs/config/bootdisk.xml	(revision 71f73f0f2cded73b234445df8a37ea9887bf30f2)
+++ postlfs/config/bootdisk.xml	(revision cfc2a547642d6812dab3f7df0655f3151fbd3cfa)
@@ -5,15 +5,19 @@
 <para>How to create a decent bootdisk</para>
 <para>The intent here is to create a "rescue bootdisk" that will load
-enough 'linux' to enable you to do rescue operations.  With what is presented here 
-you will be able to do file manipulation, mounting and unmounting, and other tasks.
-This however is not the limit.  The minimal disk is described here, and you can 
+enough 'linux' to enable you to do rescue operations.  What is presented here 
+is enough to do file manipulation, mounting and unmounting, and other tasks.
+This, however, is not the limit.  The minimal disk is described here, and you can 
 add anything you can fit on the floppy.</para>
 <para>
-Boot disk/Rescue Disk
+Boot Disk/Rescue Disk
 </para>
 <para>
-First we will create a loopback file to build our rescue disk image on, next
-we'll make a file system on the image file, then we'll use 'mount' to mount 
-the file as a regular disk, allowing us to read and write files from the loopback file.
+First we will create a loopback file on which we build the root file
+system for our rescue disk image.  This is commonly known as the initial
+ramdisk, or initrd for short, and it is automatically loaded by the boot
+process if all setup is done correctly.</para>
+<para>
+Next we'll make a file system on the loopback file and use 'mount' to mount 
+the loopback file as a regular disk, allowing us to read and write files there.
 The following commands will build us a 4 MB image.
 </para>
@@ -33,5 +37,5 @@
 anyway.  If you used MAKEDEV to create your devices, you'll want to
 trim the <filename>/mnt/loop1/dev</filename> directory to reclaim the inode space wasted 
-by all of the devices in the <filename>dev</filename> directory you don't use.</para>
+by the devices you don't use in the <filename>dev</filename> directory.</para>
 <para><screen><userinput>cp -dpR /dev/* /mnt/loop1/dev</userinput></screen></para>
 <para>Now to tend to the <filename>/etc</filename> directory.  To start, all we will do is use 
Index: postlfs/config/config.xml
===================================================================
--- postlfs/config/config.xml	(revision 71f73f0f2cded73b234445df8a37ea9887bf30f2)
+++ postlfs/config/config.xml	(revision cfc2a547642d6812dab3f7df0655f3151fbd3cfa)
@@ -4,6 +4,6 @@
 
 <para>The intention of LFS is to provide a basic system which you can
-build upon.  There are several things which many people wonder about to
-do with tidying up their system once they have done the base install.
+build upon.  There are several things, about tidying up the system,
+which many people wonder about once they have done the base install.
 We hope to cover these issues in this chapter.</para>
 
@@ -13,18 +13,32 @@
 these files can be found in the <filename>/etc</filename> hierarchy.
 There are often graphical configuration programs available for different
-subsystems but these are mostly simply pretty frontends to the process
+subsystems but most are simply pretty frontends to the process
 of editing the file.  The advantage of text-only configuration is that
 you can edit parameters using your favorite text editor, whether that
 be vim, emacs or anything else.</para>
 
+<para>The first task is making a recovery diskette because it's the most
+critical need. Then the system is configured to ease addition of
+new users, in "Configuring for Adding Users", because this
+can affect the choices you make in the three subsequent topics -
+"/etc/inputrc", "The Bash Shell Startup Files" and
+"/etc/vimrc, ~/.vimrc".
+</para>
+
+<para> The remaining topics, "/etc/issue (Customizing your logon)",
+"Random number generation", "Man page issues" and "Info page issues" are
+then addressed, in that order. They don't have much interaction with the
+other topics in this chapter.
+</para>
+
+&postlfs-config-bootdisk;
+&postlfs-config-skel;
+&postlfs-config-inputrc;
+&postlfs-config-profile;
+&postlfs-config-vimrc;
 &postlfs-config-logon;
-&postlfs-config-profile;
-&postlfs-config-inputrc;
 &postlfs-config-random;
-&postlfs-config-vimrc;
-&postlfs-config-bootdisk;
 &postlfs-config-manpages;
 &postlfs-config-infopages;
-&postlfs-config-skel;
 
 </chapter>
Index: postlfs/config/inputrc.xml
===================================================================
--- postlfs/config/inputrc.xml	(revision 71f73f0f2cded73b234445df8a37ea9887bf30f2)
+++ postlfs/config/inputrc.xml	(revision cfc2a547642d6812dab3f7df0655f3151fbd3cfa)
@@ -3,5 +3,5 @@
 <title>/etc/inputrc</title>
 
-<para><filename>inputrc</filename> deals with the mapping of the keyboard for 
+<para><filename>Inputrc</filename> deals with the mapping of the keyboard for 
 certain situations.  This file is the start-up file used by
 <application>readline</application> - the input related library used by 
@@ -13,9 +13,32 @@
 one rc file.</para>
 
-<para>The following is a base <filename>/etc/inputrc</filename> along with
-comments to explain what the various options do.</para>
+<para>Global values are set in <filename>/etc/inputrc</filename>.
+Personal user values are set in <filename>~/.inputrc</filename>. The
+<filename>~/.inputrc</filename> file will override the global settings
+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).  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
+<filename>.inputrc</filename> into the <filename>/etc/skel</filename>
+directory for use with new users.</para>
 
-<para>Please note that comments can <emphasis>not</emphasis> be on the
-same line as commands in <filename>inputrc</filename>.</para>
+<para>
+Below is a base <filename>/etc/inputrc</filename> along with
+comments to explain what the various options do.  Note that comments
+can <emphasis>not</emphasis> be on the same line as commands.
+</para>
+
+<para>If you will create an <filename>.inputrc</filename> in
+<filename>/etc/skel</filename> using the command below, change the
+command's output to <filename>/etc/skel/.inputrc</filename> and be
+sure to check/set permissions afterward. Then you can just copy that
+file to <filename>/etc/inputrc</filename> and the home directory
+of any user already existing in the system, including root, that needs
+a private version of the file.  Be sure to use the "-p"  parameter
+of "cp" to maintain permissions and be sure to change owner and group
+appropriately.
+</para>
 
 <screen><userinput><command>cat &gt; /etc/inputrc &lt;&lt; "EOF"</command>
@@ -60,12 +83,3 @@
 <command>EOF</command></userinput></screen>
 
-<para>Global values are set in <filename>/etc/inputrc</filename>.
-Personal user values as are set in <filename>~/.inputrc</filename>. The
-<filename>~/.inputrc</filename> file will override the global settings
-file.  The previous page sets up <application>Bash</application> to use
-<filename>/etc/inputrc</filename> by default.  If you want your system
-to use both, it might be a good idea to place a default
-<filename>.inputrc</filename> into the <filename>/etc/skel</filename>
-directory for use with new users.</para>
-
 </sect1>
Index: postlfs/config/logon.xml
===================================================================
--- postlfs/config/logon.xml	(revision 71f73f0f2cded73b234445df8a37ea9887bf30f2)
+++ postlfs/config/logon.xml	(revision cfc2a547642d6812dab3f7df0655f3151fbd3cfa)
@@ -16,9 +16,9 @@
 <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 
-escape sequences as shown below.</para>
+escape sequences shown below.</para>
 
 <para>One of the most common things which people want to do is to clear
 the screen at each logon.  The easiest way of doing that is to put a
-"clear" escape into <filename>/etc/issue</filename>.  A simple way of doing 
+"clear" escape-sequence into <filename>/etc/issue</filename>.  A simple way of doing 
 this is to do <userinput><command>clear &gt; /etc/issue</command></userinput>.  
 This will insert the relevant escape code into the start of the
Index: postlfs/config/profile.xml
===================================================================
--- postlfs/config/profile.xml	(revision 71f73f0f2cded73b234445df8a37ea9887bf30f2)
+++ postlfs/config/profile.xml	(revision cfc2a547642d6812dab3f7df0655f3151fbd3cfa)
@@ -6,8 +6,12 @@
 referred to as just "the shell") uses a collection of startup files to
 help create an environment to run in.  Each file has a specific use and
-may affect login and interactive environments differently.</para>
-
-<para>An interactive login shell is started after a successful login by
-<filename>/bin/login</filename> by reading the
+may affect login and interactive environments differently.  The files in
+the <filename>/etc</filename> directory generally provide global
+settings. If an equivalent file exists in your home directory it may
+override the global settings.
+</para>
+
+<para>An interactive login shell is started after a successful login, using
+<filename>/bin/login</filename>, by reading the
 <filename>/etc/passwd</filename> file.  An
 interactive non-login shell is started at the command line (e.g.
@@ -21,16 +25,28 @@
 Shells.</emphasis></para>
 
-<para>The following files are needed to make sure that the correct
-environment is read for each of the ways the shell can be invoked:
-<filename>/etc/profile</filename>, <filename>/etc/bashrc</filename>,
+<para>The following files are used to make sure that the correct
+environment is established for each of the ways the shell can be invoked:
+<filename>/etc/profile</filename> and its private equivalent
 <filename>~/.bash_profile</filename>, and
-<filename>~/.bashrc</filename>.  The file
-<filename>~/.bash_logout</filename> is not used for an invocation of the
-shell.  It is read by the shell when a user logouts of the system.  The
-files <filename>/etc/profile</filename> and
+<filename>/etc/bashrc</filename> (unofficial) and its private equivalent
+<filename>~/.bashrc</filename>.
+</para>
+
+<para>
+The file <filename>~/.bash_logout</filename> is not used for an
+invocation of the shell.  It is read by the shell when a user logs out
+of the system.</para>
+
+<para>The files <filename>/etc/profile</filename> and
 <filename>~/.bash_profile</filename> are read when the shell is invoked
-as a interactive login shell.  The file <filename>~/.bashrc</filename>
+as an interactive login shell.  The file <filename>~/.bashrc</filename>
 is read when the shell is invoked as an interactive non-login
-shell.</para> 
+shell and it reads <filename>/etc/bashrc</filename> if it exists</para> 
+
+<para>Also useful are the <filename>/etc/dircolors</filename> and
+<filename>~/.dircolors</filename> files called from
+<filename>/etc/profile</filename>. They control colorized output of
+things like <emphasis>ls --color</emphasis>.
+</para>
 
 <para>Here is a base <filename>/etc/profile</filename>.  Comments in the
@@ -141,5 +157,12 @@
 
 <para>Here is a base <filename>~/.bash_profile</filename>.  Comments in
-the file should explain everything you need.</para>
+the file should explain everything you need.  If you want each new user
+to have this file automatically provided, just change the output of the
+next command to <filename>/etc/skel/.bash_profile</filename> and check the
+permissions after the command is run. You can then copy
+<filename>/etc/skel/.bash_profile</filename> to the home directories of
+already existing users, including root, and set the owner and group
+appropriately. 
+</para>
 
 <screen><userinput><command>cat &gt; ~/.bash_profile &lt;&lt; "EOF"</command>
@@ -168,5 +191,8 @@
 
 <para>Here is a base <filename>~/.bashrc</filename>.  Comments in the
-file should explain everything you need.</para>
+file should explain everything you need.  The comments and
+instructions for using <filename>/etc/skel</filename> for
+<filename>.bash_profile</filename> above also apply here. Only the
+target file names are different.</para>
 
 <screen><userinput><command>cat &gt; ~/.bashrc &lt;&lt; "EOF"</command>
@@ -205,14 +231,17 @@
 <command>EOF</command></userinput></screen>
 
-<para>If you want to use the <filename>/etc/dircolors</filename> or
-<filename>~/.dircolors</filename> files called from
-<filename>/etc/profile</filename>, then run the following: 
-<userinput>/bin/dircolors -p > /etc/dircolors</userinput> or 
-<userinput>/bin/dircolors -p > ~/.dircolors</userinput> respectively.
-The file in the <filename>/etc</filename> directory should be used for
-global settings and if one exists in your home directory then it will
-overwrite the global settings.  It might be a good idea to create a base
-<filename>.dircolors</filename> file and place it in the
-<filename>/etc/skel</filename> directory for new users.</para>
+<para>
+If you want to use the <filename>dircolors</filename> capability
+then run the following command. The <filename>/etc/skel</filename> setup
+steps seen above also can be used here to provide a
+<filename>.dircolors</filename> file when a new user is set up. As
+before, just change the output file name on the following command and
+assure the permissions, owner and group are correct on the files created
+and/or copied.
+</para>
+
+<para>
+<userinput><command>/bin/dircolors -p > /etc/dircolors</command></userinput>
+</para>
 
 <para>Ian Macdonald has written an excellent collection of tips and
Index: postlfs/config/skel.xml
===================================================================
--- postlfs/config/skel.xml	(revision 71f73f0f2cded73b234445df8a37ea9887bf30f2)
+++ postlfs/config/skel.xml	(revision cfc2a547642d6812dab3f7df0655f3151fbd3cfa)
@@ -1,33 +1,28 @@
 <sect1 id="postlfs-config-skel">
 <?dbhtml filename="skel.html" dir="postlfs"?>
-<title>/etc/skel</title>
+<title>Configuring for Adding Users</title>
 
-<para>The <filename>/etc/skel</filename> directory is quite simple
-to setup and use.  It provides a way to make sure that all new users on
-your LFS system begin with the same settings.  The
-<filename>/etc/skel</filename> directory is used by the
-<filename>/usr/sbin/useradd</filename> program.</para>
+<para>Together, the <filename>/usr/sbin/useradd</filename> command and
+<filename>/etc/skel</filename> directory (both are easy to setup and use)
+provide a way to assure new users are added on your LFS system with the
+same beginning settings for things like $PATH, keyboard processing and
+environmental variables.  Using these two facilities makes it easier to
+assure this initial state for each new user.
+</para>
 
-<para>For more information see <userinput>man useradd</userinput>.</para>
+<para>
+The <filename>/etc/skel</filename> directory holds copies of various
+initialization and other files that may be copied to the new user's home
+directory when the <filename>/usr/sbin/useradd</filename>
+program adds the new user.</para>
 
-<para>To get started create a <filename>/etc/skel</filename> directory.
-Creating the directory as root is the best way to go.  Next copy any
-files into <filename>/etc/skel</filename> that you want every new user
-to have placed in their home drive.  Examples include
-<filename>.bash_profile</filename>, <filename>.bashrc</filename>,
-<filename>.bash_logout</filename>, <filename>dircolors</filename>,
-<filename>.inputrc</filename> and <filename>.vimrc</filename>.</para>
+<para>Useradd</para>
 
-<para>When creating a new user with
-<filename>/usr/sbin/useradd</filename> use the <userinput>-m</userinput>
-parameter.  For example:</para>
-
-<para><screen><userinput>useradd -m -s/bin/bash jwrober</userinput></screen></para>
-
-<para>The <filename>/usr/sbin/useradd</filename> program uses a
-collection of default values.  It will read them from the
-<filename>/etc/default/useradd</filename> file if it exists.  If the
-file does not exist, then it uses some internal defaults.  They can be
-found by running <userinput>/usr/sbin/useradd -D</userinput>.</para>
+<para>The <filename>useradd</filename> program uses a collection of
+default values kept in <filename>/etc/default/useradd</filename>,
+if it exists.  If the file does not exist, then it uses some internal
+defaults.  You can see the default values by running
+<userinput>/usr/sbin/useradd -D</userinput>.
+</para>
 
 <para>To change these values to something new, create a base
@@ -53,9 +48,64 @@
 
 <para>This will set the <userinput>SHELL=</userinput> line to
-<userinput>SHELL=/bin/bash</userinput>.  This makes it even easier to
-add new users to your LFS system.  The
-<filename>/usr/sbin/useradd</filename> has many parameters that can be
-set in the <filename>/etc/default/useradd</filename> file.  See the man
-page for more details.</para>
+<userinput>SHELL=/bin/bash</userinput>.</para>
+
+<para><filename>Useradd</filename> has many parameters that
+can be set in the <filename>/etc/default/useradd</filename> file.
+</para>
+
+<para>For more information see <userinput>man useradd</userinput>.</para>
+
+<para>/etc/skel</para>
+
+<para>To get started create an <filename>/etc/skel</filename> directory
+and make sure it is writable only by the system administrator, usually
+root. Creating the directory as root is the best way to go.</para>
+
+<para>The mode of any files from this part of the book that you put in
+<filename>/etc/skel</filename> should be writable only by the owner.
+Also, since there is no telling what kind of sensitive information a
+user may eventually place in their copy of these files, you should
+make them unreadable by "group" and "other".</para>
+
+<para>You can also put other files in <filename>/etc/skel</filename> and
+different permissions may be needed for them.
+</para>
+
+<para>
+Decide which initialization files should be provided in every (or most)
+new user's home directory. The decisions you make will affect what you
+do in the next three sections, "/etc/inputrc", "The Bash Shell Startup
+Files" and "/etc/vimrc, ~/.vimrc". Some or all of those files will be
+useful for root, any already-existing users, and new users.</para>
+
+<para>The files from those sections that you might want to place in
+<filename>/etc/skel</filename> include
+<filename>.inputrc</filename>, <filename>.bash_profile</filename>,
+<filename>.bashrc</filename>, <filename>.bash_logout</filename>,
+<filename>.dircolors</filename>, and <filename>.vimrc</filename>. If
+you are unsure which of these should be placed there, just continue to
+the following sections, read each section and any references provided,
+and then make your decision.</para>
+
+<para>You will run a slightly modified set of commands for files which
+are placed in <filename>/etc/skel</filename>. Each section will remind
+you of this. In brief, the book's commands have been written for files
+<emphasis>not</emphasis> added to <filename>/etc/skel</filename> and
+just send the results to the user's home directory. If the file is going
+to be in <filename>/etc/skel</filename>, change the book's command(s) to
+send output there instead and then just copy the file from
+<filename>/etc/skel</filename> to the appropriate directories, like
+<filename>/etc</filename>, <filename>~</filename> or the home directoriy
+of any other user already in the system.</para>
+
+<para>When Adding a User</para>
+
+<para>When adding a new user with <filename>useradd</filename> use
+the <userinput>-m</userinput> parameter, which tells
+<filename>useradd</filename> to create the user's home directory and
+copy files from <filename>/etc/skel</filename> (can be overridden) to
+the new user's home directory.  For example:</para>
+
+<para><screen><userinput>useradd -m -s/bin/bash jwrober</userinput></screen></para>
 
 </sect1>
Index: postlfs/config/vimrc.xml
===================================================================
--- postlfs/config/vimrc.xml	(revision 71f73f0f2cded73b234445df8a37ea9887bf30f2)
+++ postlfs/config/vimrc.xml	(revision cfc2a547642d6812dab3f7df0655f3151fbd3cfa)
@@ -17,5 +17,12 @@
 the global vimrc was <filename>/usr/share/vim/vimrc</filename>.</para>
 
-<para>Here is an example of a slightly expanded vimrc:</para>
+<para>Here is a slightly expanded vimrc that you can put in
+<filename>/etc/vimrc</filename> to provide global effect. Of course, if
+you put it into <filename>/etc/skel/.vimrc</filename> instead, it will
+be made available to users you add to the system later. You can also copy
+the file from <filename>/etc/skel/.vimrc</filename> to
+<filename>/etc/vimrc</filename> and the home directory of users already
+on the system, like root. Be sure to set permissions, owner and group if
+you do copy anything directly from <filename>/etc/skel</filename>.</para>
 
 <para><screen>" Begin .vimrc
