Index: general.ent
===================================================================
--- general.ent	(revision ebbe967575defd2ca6e2cbb440abb8a6a7c75099)
+++ general.ent	(revision 6f365541438cef3337bb3256453ef02a30eb33f8)
@@ -1,5 +1,5 @@
 <!-- $LastChangedBy$ $Date$ -->
 
-<!ENTITY day          "07">                   <!-- Always 2 digits -->
+<!ENTITY day          "08">                   <!-- Always 2 digits -->
 <!ENTITY month        "03">                   <!-- Always 2 digits -->
 <!ENTITY year         "2017">
@@ -7,5 +7,5 @@
 <!ENTITY copyholder   "The BLFS Development Team">
 <!ENTITY version      "&year;-&month;-&day;">
-<!ENTITY releasedate  "March 7th &year;">
+<!ENTITY releasedate  "March 8th &year;">
 <!ENTITY pubdate      "&year;-&month;-&day;"> <!-- metadata req. by TLDP -->
 <!ENTITY blfs-version "svn">                  <!-- svn|[release #] -->
Index: introduction/welcome/changelog.xml
===================================================================
--- introduction/welcome/changelog.xml	(revision ebbe967575defd2ca6e2cbb440abb8a6a7c75099)
+++ introduction/welcome/changelog.xml	(revision 6f365541438cef3337bb3256453ef02a30eb33f8)
@@ -44,4 +44,13 @@
 
     <listitem>
+      <para>March 8th, 2017</para>
+      <itemizedlist>
+        <listitem>
+          <para>[dj] - Add ~/.profile to bash shell startup files.</para>
+        </listitem>
+      </itemizedlist>
+    </listitem>
+
+    <listitem>
       <para>March 7th, 2017</para>
       <itemizedlist>
Index: postlfs/config/profile.xml
===================================================================
--- postlfs/config/profile.xml	(revision ebbe967575defd2ca6e2cbb440abb8a6a7c75099)
+++ postlfs/config/profile.xml	(revision 6f365541438cef3337bb3256453ef02a30eb33f8)
@@ -25,8 +25,9 @@
 
   <para>An interactive login shell is started after a successful login, using
-  <filename>/bin/login</filename>, by reading the <filename>/etc/passwd</filename>
-  file.  This shell invocation normally reads <filename>/etc/profile</filename>
-  and its private equivalent <filename>~/.bash_profile</filename> upon
-  startup.</para>
+  <filename>/bin/login</filename>, by reading the
+  <filename>/etc/passwd</filename> file. This shell invocation normally reads
+  <filename>/etc/profile</filename> and its private equivalent
+  <filename>~/.bash_profile</filename> (or <filename>~/.profile</filename> if
+  called as <command>/bin/sh</command>) upon startup.</para> 
 
   <para>An interactive non-login shell is normally started at the command-line
@@ -37,6 +38,6 @@
   <command>konsole</command> from within a graphical environment. This type of
   shell invocation normally copies the parent environment and then reads the
-  user's <filename>~/.bashrc</filename> file for additional startup configuration
-  instructions.</para>
+  user's <filename>~/.bashrc</filename> file for additional startup
+  configuration instructions.</para>
 
   <para>A non-interactive shell is usually present when a shell script is
@@ -431,4 +432,29 @@
   </sect2>
 
+  <sect2 id="dot_profile-profile">
+    <title>~/.profile</title>
+
+    <indexterm zone="postlfs-config-profile dot_profile-profile">
+      <primary sortas="e-AA.dot_profile">~/.profile</primary>
+    </indexterm>
+
+    <para>Here is a base <filename>~/.profile</filename>. The comments and
+    instructions for using <filename class="directory">/etc/skel</filename> for
+    <filename>.bash_profile</filename> above also apply here. Only the target
+    file names are different.</para>
+
+<screen><userinput>cat &gt; ~/.profile &lt;&lt; "EOF"
+<literal># Begin ~/.profile
+# Personal environment variables and startup programs.
+
+if [ -d "$HOME/bin" ] ; then
+  pathprepend $HOME/bin
+fi
+
+# End ~/.profile</literal>
+EOF</userinput></screen>
+
+  </sect2>
+
   <sect2 id="bashrc-profile">
     <title>~/.bashrc</title>
@@ -438,8 +464,5 @@
     </indexterm>
 
-    <para>Here is a base <filename>~/.bashrc</filename>.  The comments and
-    instructions for using <filename class="directory">/etc/skel</filename> for
-    <filename>.bash_profile</filename> above also apply here. Only the target file
-    names are different.</para>
+    <para>Here is a base <filename>~/.bashrc</filename>.</para>
 
 <screen><userinput>cat &gt; ~/.bashrc &lt;&lt; "EOF"
@@ -501,17 +524,17 @@
     </indexterm>
 
-    <para> If you want to use the <filename>dircolors</filename> capability, then
-    run the following command. The <filename class="directory">/etc/skel</filename>
-    setup steps shown 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> If you want to use the <filename>dircolors</filename> capability,
+    then run the following command. The
+    <filename class="directory">/etc/skel</filename> setup steps shown 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>
 
 <screen role="root"><userinput>dircolors -p > /etc/dircolors</userinput></screen>
 
-    <para>If you wish to customize the colors used for different file types, you can
-    edit the <filename>/etc/dircolors</filename> file.  The instructions for setting
-    the colors are embedded in the file.</para>
+    <para>If you wish to customize the colors used for different file types,
+    you can edit the <filename>/etc/dircolors</filename> file. The instructions
+    for setting the colors are embedded in the file.</para>
 
 
