| 12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061 | <?xml version="1.0" encoding="ISO-8859-1"?><!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [  <!ENTITY % general-entities SYSTEM "../general.ent">  %general-entities;]><sect1 id="ch-system-chroot"><title>Entering the Chroot Environment</title><?dbhtml filename="chroot.html"?><para>It is time to enter the chroot environment to beginbuilding and installing the final LFS system. As user<emphasis>root</emphasis>, run the following command to enter therealm that is, at the moment, populated with only the temporarytools:</para><screen><userinput>chroot "$LFS" /tools/bin/env -i \    HOME=/root TERM="$TERM" PS1='\u:\w\$ ' \    PATH=/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin \    /tools/bin/bash --login +h</userinput></screen><para>The <parameter>-i</parameter> option given to the<command>env</command> command will clear all variables of the chrootenvironment. After that, only the <envar>HOME</envar>,<envar>TERM</envar>, <envar>PS1</envar>, and<envar>PATH</envar> variables are set again. The<parameter>TERM=$TERM</parameter> construct will set the<envar>TERM</envar> variable inside chroot to the same value asoutside chroot. This variable is needed for programs like<command>vim</command> and <command>less</command> to operateproperly.  If other variables are needed, such as<envar>CFLAGS</envar> or <envar>CXXFLAGS</envar>, this isa good place to set them again.</para><para>From this point on, there is no need to use the<envar>LFS</envar> variable anymore, because all work will berestricted to the LFS file system.  This is because the Bash shell istold that <filename class="directory">$LFS</filename> is now the root(<filename class="directory">/</filename>) directory.</para><para>Notice that <filename class="directory">/tools/bin</filename> comes lastin the <envar>PATH</envar>. This means that a temporary tool will no longer beused once its final version is installed. This occurs when the shell does not<quote>remember</quote> the locations of executed binaries—for thisreason, hashing is switched off by passing the <parameter>+h</parameter> optionto <command>bash</command>.</para><para>It is important that all the commands throughout the remainderof this chapter and the following chapters are run from within thechroot environment. If you leave this environment for any reason(rebooting for example), remember to first mount the <systemitemclass="filesystem">proc</systemitem> and <systemitemclass="filesystem">devpts</systemitem> file systems (discussed in theprevious section) and enter chroot again before continuing with theinstallations.</para><para>Note that the <command>bash</command> prompt will say<computeroutput>I have no name!</computeroutput> This is normal because the<filename>/etc/passwd</filename> file has not been created yet.</para></sect1>
 |