Changeset 07ecae2
- Timestamp:
- 12/12/2003 01:43:31 AM (21 years ago)
- Branches:
- 10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 12.2, 12.2-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/loongarch-12.2, xry111/mips64el, xry111/multilib, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- 9c8916b
- Parents:
- 6213d4c
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter01/changelog.xml
r6213d4c r07ecae2 45 45 </itemizedlist> 46 46 </listitem> 47 48 <listitem><para>December 11th, 2003 [greg]: Chapter 5: - Setting up the 49 environment: Fixed Bash startup files to handle HOME and PS1.</para></listitem> 47 50 48 51 <listitem><para>December 3rd, 2003 [greg]: Upgraded to Gettext-0.13, -
chapter05/chapter05.xml
r6213d4c r07ecae2 353 353 354 354 <screen><userinput>cat > ~/.bash_profile << "EOF"</userinput> 355 exec env -i TERM=$TERM/bin/bash355 exec env -i HOME=$HOME TERM=$TERM PS1='\u:\w\$ ' /bin/bash 356 356 <userinput>EOF</userinput></screen> 357 357 358 <para>The <userinput>exec env -i TERM=$TERM /bin/bash</userinput> command 359 creates a new instance of Bash with a completely empty environment, except for 360 the TERM variable. This is needed to ensure that no unwanted and potentially 361 hazardous environment variables from the host system leak into our build 362 environment. The technique used here is a little non-standard but it achieves 363 the goal of enforcing a clean environment. By way of explanation, the initial 364 shell is a <emphasis>login</emphasis> shell which reads the 365 <filename>.bash_profile</filename>. The new shell instance is a 358 <para>The 359 <userinput>exec env -i HOME=$HOME TERM=$TERM PS1='\u:\w\$ ' /bin/bash</userinput> 360 command creates a new instance of Bash with a completely empty environment, 361 except for the HOME, TERM and PS1 variables. This is needed to ensure that no 362 unwanted and potentially hazardous environment variables from the host system 363 leak into our build environment. The technique used here is a little 364 non-standard but it achieves the goal of enforcing a clean environment. By way 365 of explanation, the initial shell is a <emphasis>login</emphasis> shell which 366 reads the <filename>.bash_profile</filename>. The new shell instance is a 366 367 <emphasis>non-login</emphasis> shell which reads the 367 368 <filename>.bashrc</filename> (created next).</para> … … 392 393 files and directories are only writable for their owner, but readable and 393 394 executable for anyone.</para> 394 395 395 396 <para>The LFS variable should of course be set to the mount point you 396 397 chose.</para> -
index.xml
r6213d4c r07ecae2 4 4 5 5 6 <!ENTITY version "CVS-200312 03">7 <!ENTITY releasedate "December 3rd, 2003">6 <!ENTITY version "CVS-20031211"> 7 <!ENTITY releasedate "December 11th, 2003"> 8 8 <!ENTITY milestone "5.1"> 9 9 <!ENTITY nbsp " ">
Note:
See TracChangeset
for help on using the changeset viewer.