Changes in chapter04/settingenviron.xml [4e26453:aa9ade1]
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter04/settingenviron.xml
r4e26453 raa9ade1 20 20 EOF</userinput></screen> 21 21 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> command24 with the<quote><parameter>-</parameter></quote> option,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> command 24 with <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.</para> 33 leak into the build environment. The technique used here achieves the goal of 34 ensuring a clean environment.</para> 34 35 35 36 <para>The new instance of the shell is a <emphasis>non-login</emphasis> … … 100 101 Setting <envar>LC_ALL</envar> to <quote>POSIX</quote> or <quote>C</quote> 101 102 (the two are equivalent) ensures that everything will work as expected in 102 the c ross-compilationenvironment.</para>103 the chroot environment.</para> 103 104 </listitem> 104 105 </varlistentry> … … 108 109 <listitem> 109 110 <para>The <envar>LFS_TGT</envar> variable sets a non-default, but compatible machine 110 description for use when building our cross -compiler and linker and when111 c ross-compiling our temporary toolchain. More information is provided by111 description for use when building our cross compiler and linker and when cross 112 compiling our temporary toolchain. More information is contained in 112 113 <xref linkend="ch-tools-toolchaintechnotes" role=""/>.</para> 113 114 </listitem> … … 132 133 <listitem> 133 134 <para>If <filename class="directory">/bin</filename> is not a symbolic 134 link, it mustbe added to the <envar>PATH</envar> variable.</para>135 link, then it has to be added to the <envar>PATH</envar> variable.</para> 135 136 </listitem> 136 137 </varlistentry> … … 163 164 <term><parameter>export ...</parameter></term> 164 165 <listitem> 165 <para>While the precedingcommands have set some variables, in order166 <para>While the above commands have set some variables, in order 166 167 to make them visible within any sub-shells, we export them.</para> 167 168 </listitem> … … 172 173 <important> 173 174 174 <para>Several commercial distributions add a n undocumented instantiation175 <para>Several commercial distributions add a non-documented instantiation 175 176 of <filename>/etc/bash.bashrc</filename> to the initialization of 176 177 <command>bash</command>. This file has the potential to modify the … … 185 186 <screen role="nodump"><userinput>[ ! -e /etc/bash.bashrc ] || mv -v /etc/bash.bashrc /etc/bash.bashrc.NOUSE</userinput></screen> 186 187 187 <para> Whenthe <systemitem class="username">lfs</systemitem>188 user is no longer needed (at the beginning of <xref189 linkend="chapter-chroot-temporary-tools"/> ), you may safelyrestore188 <para>After use of the <systemitem class="username">lfs</systemitem> 189 user is finished at the beginning of <xref 190 linkend="chapter-chroot-temporary-tools"/>, you can restore 190 191 <filename>/etc/bash.bashrc</filename> (if desired).</para> 191 192 … … 196 197 </important> 197 198 198 <para>Finally, to ensure the environment isfully prepared for building the199 <para>Finally, to have the environment fully prepared for building the 199 200 temporary tools, force the <command>bash</command> shell to read 200 201 the new user profile:</para>
Note:
See TracChangeset
for help on using the changeset viewer.