Browse Source

Fixed Bash startup files to handle HOME and PS1.

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3132 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Greg Schafer 21 years ago
parent
commit
07ecae2532
3 changed files with 16 additions and 12 deletions
  1. 3 0
      chapter01/changelog.xml
  2. 11 10
      chapter05/chapter05.xml
  3. 2 2
      index.xml

+ 3 - 0
chapter01/changelog.xml

@@ -45,6 +45,9 @@
 </itemizedlist>
 </itemizedlist>
 </listitem>
 </listitem>
 
 
+<listitem><para>December 11th, 2003 [greg]: Chapter 5: - Setting up the
+environment: Fixed Bash startup files to handle HOME and PS1.</para></listitem>
+
 <listitem><para>December 3rd, 2003 [greg]: Upgraded to Gettext-0.13,
 <listitem><para>December 3rd, 2003 [greg]: Upgraded to Gettext-0.13,
 Man-pages-1.64, Linux-2.4.23 and Psmisc-21.4.</para></listitem>
 Man-pages-1.64, Linux-2.4.23 and Psmisc-21.4.</para></listitem>
 
 

+ 11 - 10
chapter05/chapter05.xml

@@ -352,17 +352,18 @@ startup files for the Bash shell. While logged in as user
 <filename>.bash_profile</filename>:</para>
 <filename>.bash_profile</filename>:</para>
 
 
 <screen><userinput>cat &gt; ~/.bash_profile &lt;&lt; "EOF"</userinput>
 <screen><userinput>cat &gt; ~/.bash_profile &lt;&lt; "EOF"</userinput>
-exec env -i TERM=$TERM /bin/bash
+exec env -i HOME=$HOME TERM=$TERM PS1='\u:\w\$ ' /bin/bash
 <userinput>EOF</userinput></screen>
 <userinput>EOF</userinput></screen>
 
 
-<para>The <userinput>exec env -i TERM=$TERM /bin/bash</userinput> command
-creates a new instance of Bash with a completely empty environment, except for
-the TERM variable. This is needed to ensure that no unwanted and potentially
-hazardous environment variables from the host system leak into our build
-environment. The technique used here is a little non-standard but it achieves
-the goal of enforcing a clean environment. By way of explanation, the initial
-shell is a <emphasis>login</emphasis> shell which reads the
-<filename>.bash_profile</filename>. The new shell instance is a
+<para>The
+<userinput>exec env -i HOME=$HOME TERM=$TERM PS1='\u:\w\$ ' /bin/bash</userinput>
+command creates a new instance of Bash with a completely empty environment,
+except for the HOME, TERM and PS1 variables. This is needed to ensure that no
+unwanted and potentially hazardous environment variables from the host system
+leak into our build environment. The technique used here is a little
+non-standard but it achieves the goal of enforcing a clean environment. By way
+of explanation, the initial shell is a <emphasis>login</emphasis> shell which
+reads the <filename>.bash_profile</filename>. The new shell instance is a
 <emphasis>non-login</emphasis> shell which reads the
 <emphasis>non-login</emphasis> shell which reads the
 <filename>.bashrc</filename> (created next).</para>
 <filename>.bashrc</filename> (created next).</para>
 
 
@@ -391,7 +392,7 @@ the newest available version during the build process.</para>
 <para>Setting the user file-creation mask to 022 ensures that newly created
 <para>Setting the user file-creation mask to 022 ensures that newly created
 files and directories are only writable for their owner, but readable and
 files and directories are only writable for their owner, but readable and
 executable for anyone.</para>
 executable for anyone.</para>
- 
+
 <para>The LFS variable should of course be set to the mount point you
 <para>The LFS variable should of course be set to the mount point you
 chose.</para>
 chose.</para>
 
 

+ 2 - 2
index.xml

@@ -3,8 +3,8 @@
 				"/usr/share/docbook/docbookx.dtd" [
 				"/usr/share/docbook/docbookx.dtd" [
 
 
 
 
-<!ENTITY version "CVS-20031203">
-<!ENTITY releasedate "December 3rd, 2003">
+<!ENTITY version "CVS-20031211">
+<!ENTITY releasedate "December 11th, 2003">
 <!ENTITY milestone "5.1">
 <!ENTITY milestone "5.1">
 <!ENTITY nbsp " ">
 <!ENTITY nbsp " ">