Changes in chapter07/chroot.xml [7152faa:e49e2ea]

File:

• chapter07/chroot.xml (modified) (4 diffs)

chapter07/chroot.xml

@@ -1 @@
-<?xml version="1.0" encoding="UTF-8"?>
+<?xml version="1.0" encoding="ISO-8859-1"?>
 <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
   "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
@@ -7 +7 @@
 
 <sect1 id="ch-tools-chroot">
-  <?dbhtml filename="chroot.html"?>
+  <?dbhtml filename="env.html"?>
 
-  <title>Entering the Chroot Environment</title>
+  <title>Setting up the Environment</title>
 
-  <para>Now that all the packages which are required to build the rest of the
-  needed tools are on the system, it is time to enter the chroot environment and
-  finish installing the temporary tools. This environment will also be
-  used to install the final system. As user <systemitem
-  class="username">root</systemitem>, run the following command to enter the
-  environment that is, at the moment, populated with nothing but temporary
-  tools:</para>
+    <para>The current shell is also the <command>init</command> process,
+    so exiting from it will cause kernel panic.  Prevent exiting from the
+    shell accidentally:</para>
 
-<screen role="nodump"><userinput>chroot "$LFS" /usr/bin/env -i   \
+<screen role="nodump"><userinput>enable -n exit
+readonly IGNOREEOF=1000</userinput></screen>
+
+    <para>The standard I/O streams of the initial shell process is connected
+    with <filename>/dev/console</filename>.  However, the testsuite of some
+    packages may expect the standard I/O streams to be connected with a
+    <quote>real</quote> TTY device node.  Spawn a new shell process on the
+    TTY device with <command>agetty</command>:</para>
+
+<screen role="nodump"><userinput>agetty -n -l /bin/bash <replaceable>tty0</replaceable></userinput></screen>
+
+    <para>If you are working via a serial console, replace
+    <replaceable>tty0</replaceable> with the name of the serial console
+    device node, for example <literal>ttyS0</literal>.</para>
+
+    <para>The command above spawns a new shell process on the TTY device
+    specified in the command, and the initial shell process will run in
+    background as an init process with very limited functions. The new shell
+    process will output:</para>
+
+<screen role="nodump"><computeroutput>bash: cannot set terminal process group (-1): Inappropriate ioctl for device
+bash: no job control in this shell</computeroutput></screen>
+
+    <para>This is normal because the shell is not assigned with a
+    controlling terminal yet.  Now set up the controlling terminal and
+    some environment variables:</para>
+
+<screen><userinput>exec setsid -c /usr/bin/env -i  \
     HOME=/root                  \
     TERM="$TERM"                \
-    PS1='(lfs chroot) \u:\w\$ ' \
+    PS1='(lfs) \u:\w\$ '        \
     PATH=/usr/bin:/usr/sbin     \
     MAKEFLAGS="-j<replaceable>$(nproc)</replaceable>"      \
     TESTSUITEFLAGS="-j<replaceable>$(nproc)</replaceable>" \
     /bin/bash --login</userinput></screen>
+
+    <para>The command replaces the current shell process with a new shell
+    process, with controlling terminal set up.</para>
 
   <para>
@@ -39 +65 @@
 
   <para>The <parameter>-i</parameter> option given to the <command>env</command>
-  command will clear all the variables in the chroot environment. After that, only
+  command will clear all the variables in the environment. 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 sets the <envar>TERM</envar>
-  variable inside chroot to the same value as outside chroot. This variable is
+  <parameter>TERM=$TERM</parameter> construct will set the <envar>TERM</envar>
+  variable to the default value specified by <command>agetty</command>. This variable is
   needed so programs like <command>vim</command> and <command>less</command>
   can operate properly.  If other variables are desired, such as
   <envar>CFLAGS</envar> or <envar>CXXFLAGS</envar>, this is a good place to set
   them.</para>
-
-  <para>From this point on, there is no need to use the
-  <envar>LFS</envar> variable any more because all work will be restricted
-  to the LFS file system; the <command>chroot</command> command runs the
-  Bash shell with the root
-  (<filename class="directory">/</filename>) directory set to
-  <filename class='directory'>$LFS</filename>.</para>
 
   <para>Notice that <filename class="directory">/tools/bin</filename> is not
@@ -64 +83 @@
   <filename>/etc/passwd</filename> file has not been created yet.</para>
 
+  <para>Now set up a temporary hostname, which is required by test suite of
+  some packages:</para>
+
+<screen><userinput>hostname lfs</userinput></screen>
+
   <note>
     <para>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
+    chapter and the following chapters are run from within the environment
+    we've set. If you leave this environment for any reason (rebooting for
     example), ensure that the virtual kernel filesystems are mounted as
-    explained in <xref linkend="ch-tools-bindmount"/> and <xref
-    linkend="ch-tools-kernfsmount"/> and enter chroot again before continuing
-    with the installation.</para>
+    explained in <xref linkend="ch-tools-kernfsmount"/> and
+    <xref linkend="ch-tools-devadjust"/> and set up the environment again before
+    continuing with the installation.</para>
   </note>