It is time to enter the chroot environment to begin building and
installing the final CLFS system. As user root, run the following command to enter the
realm that is, at the moment, populated with only the temporary
tools:
chroot "${CLFS}" /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
The -i option given to the
env command will clear
all variables of the chroot environment. After that, only the
HOME, TERM,
PS1, and PATH
variables are set again. The TERM=${TERM} construct will set the
TERM variable inside chroot to the same
value as outside chroot. This variable is needed for programs like
vim and less to operate properly. If other
variables are needed, such as CFLAGS or
CXXFLAGS, this is a good place to set them
again.
From this point on, there is no need to use the CLFS variable anymore, because all work will be
restricted to the CLFS file system. This is because the Bash shell is
told that ${CLFS} is now the root
(/) directory.
Notice that /tools/bin comes last in
the PATH. This means that a temporary tool
will no longer be used once its final version is installed. This
occurs when the shell does not “remember” the locations of executed
binaries—for this reason, hashing is switched off by passing
the +h option to bash.
It is important that all the commands throughout the remainder of
this chapter and the following chapters are run from within the
chroot environment. If you leave this environment for any reason
(rebooting for example), remember to first mount the proc and devpts
file systems (discussed in the previous section) and enter chroot
again before continuing with the installations.
Note that the bash
prompt will say I have no name!
This is normal because the /etc/passwd
file has not been created yet.