Changes in chapter04/settingenviron.xml [aa9ade1:4e26453]
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter04/settingenviron.xml
raa9ade1 r4e26453 20 20 EOF</userinput></screen> 21 21 22 <para>When logged on as user <systemitem class="username">lfs</systemitem> 23 or switched to the &lfs-user; user using a<command>su</command> command24 with <quote><parameter>-</parameter></quote> option,22 <para>When logged on as user <systemitem class="username">lfs</systemitem>, 23 or when switched to the &lfs-user; user using an <command>su</command> command 24 with the <quote><parameter>-</parameter></quote> option, 25 25 the initial shell is a <emphasis>login</emphasis> shell which reads 26 26 the <filename>/etc/profile</filename> of the host (probably containing some … … 31 31 <envar>TERM</envar>, and <envar>PS1</envar> variables. This ensures that no 32 32 unwanted and potentially hazardous environment variables from the host system 33 leak into the build environment. The technique used here achieves the goal of 34 ensuring a clean environment.</para> 33 leak into the build environment.</para> 35 34 36 35 <para>The new instance of the shell is a <emphasis>non-login</emphasis> … … 101 100 Setting <envar>LC_ALL</envar> to <quote>POSIX</quote> or <quote>C</quote> 102 101 (the two are equivalent) ensures that everything will work as expected in 103 the c hrootenvironment.</para>102 the cross-compilation environment.</para> 104 103 </listitem> 105 104 </varlistentry> … … 109 108 <listitem> 110 109 <para>The <envar>LFS_TGT</envar> variable sets a non-default, but compatible machine 111 description for use when building our cross compiler and linker and when cross112 c ompiling our temporary toolchain. More information is contained in110 description for use when building our cross-compiler and linker and when 111 cross-compiling our temporary toolchain. More information is provided by 113 112 <xref linkend="ch-tools-toolchaintechnotes" role=""/>.</para> 114 113 </listitem> … … 133 132 <listitem> 134 133 <para>If <filename class="directory">/bin</filename> is not a symbolic 135 link, then it has tobe added to the <envar>PATH</envar> variable.</para>134 link, it must be added to the <envar>PATH</envar> variable.</para> 136 135 </listitem> 137 136 </varlistentry> … … 164 163 <term><parameter>export ...</parameter></term> 165 164 <listitem> 166 <para>While the abovecommands have set some variables, in order165 <para>While the preceding commands have set some variables, in order 167 166 to make them visible within any sub-shells, we export them.</para> 168 167 </listitem> … … 173 172 <important> 174 173 175 <para>Several commercial distributions add a non-documented instantiation174 <para>Several commercial distributions add an undocumented instantiation 176 175 of <filename>/etc/bash.bashrc</filename> to the initialization of 177 176 <command>bash</command>. This file has the potential to modify the … … 186 185 <screen role="nodump"><userinput>[ ! -e /etc/bash.bashrc ] || mv -v /etc/bash.bashrc /etc/bash.bashrc.NOUSE</userinput></screen> 187 186 188 <para> After use ofthe <systemitem class="username">lfs</systemitem>189 user is finishedat the beginning of <xref190 linkend="chapter-chroot-temporary-tools"/> , you canrestore187 <para>When the <systemitem class="username">lfs</systemitem> 188 user is no longer needed (at the beginning of <xref 189 linkend="chapter-chroot-temporary-tools"/>), you may safely restore 191 190 <filename>/etc/bash.bashrc</filename> (if desired).</para> 192 191 … … 197 196 </important> 198 197 199 <para>Finally, to have the environmentfully prepared for building the198 <para>Finally, to ensure the environment is fully prepared for building the 200 199 temporary tools, force the <command>bash</command> shell to read 201 200 the new user profile:</para>
Note:
See TracChangeset
for help on using the changeset viewer.