Index: chapter02/aboutlfs.xml
===================================================================
--- chapter02/aboutlfs.xml	(revision 201aa93863b8999290f262baa52e487e01bfada3)
+++ chapter02/aboutlfs.xml	(revision e4b4c5a0b1ae2aa23095d957e7d63ca37c77b5eb)
@@ -15,9 +15,7 @@
   throughout the LFS build process. It should be set to the name of the
   directory where you will be building your LFS system - we will use
-  <filename class="directory">/mnt/lfs</filename> as an example, but you may
-  choose any directory name you want. If you are building LFS on a separate
-  partition, this directory will be the mount point for the partition.
-  Choose a directory location and set the variable with the
-  following command:</para>
+  <filename class="directory">/mnt/lfs</filename> as an example, but the
+  choose any directory name you want. Choose a directory location and set the
+  variable with the following command:</para>
 
 <screen role="nodump"><userinput>export LFS=<replaceable>/mnt/lfs</replaceable></userinput></screen>
@@ -28,4 +26,11 @@
   <quote>/mnt/lfs</quote> (or whatever value the variable was set to) when it
   processes the command line.</para>
+
+  <para>Create the directory:</para>
+
+<screen role="nodump"><userinput>mkdir -pv $LFS</userinput></screen>
+
+  <para>If you don't have much space in the partition holding the directory,
+  you can mount another partition on it.</para>
 
   <caution>
Index: chapter02/chapter02.xml
===================================================================
--- chapter02/chapter02.xml	(revision 201aa93863b8999290f262baa52e487e01bfada3)
+++ chapter02/chapter02.xml	(revision e4b4c5a0b1ae2aa23095d957e7d63ca37c77b5eb)
@@ -15,8 +15,5 @@
   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="hostreqs.xml"/>
   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="stages.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="creatingpartition.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="creatingfilesystem.xml"/>
   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="aboutlfs.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="mounting.xml"/>
 
 </chapter>
Index: chapter02/hostreqs.xml
===================================================================
--- chapter02/hostreqs.xml	(revision 201aa93863b8999290f262baa52e487e01bfada3)
+++ chapter02/hostreqs.xml	(revision e4b4c5a0b1ae2aa23095d957e7d63ca37c77b5eb)
@@ -16,4 +16,9 @@
      <para>The LFS editors recommend that the system CPU have at least
      four cores and that the system have at least 8 GB of memory. 
+
+     For the Cross Edition, it's recommended that both the system running
+     the host distribution and the target system should meet the
+     requirements.
+
      Older systems that do not meet these requirements will still work,
      but the time to build packages will be significantly longer
@@ -52,4 +57,9 @@
 
     <listitem>
+      <!-- needed to cross build the kernel in chapter 6 -->
+      <para><emphasis role="strong">Bc-1.07.0</emphasis></para>
+    </listitem>
+
+    <listitem>
       <para><emphasis role="strong">Bison-2.7</emphasis> (/usr/bin/yacc
       should be a link to bison or a small script that executes bison)</para>
@@ -90,37 +100,4 @@
     <listitem>
       <para><emphasis role="strong">Gzip-1.3.12</emphasis></para>
-    </listitem>
-
-    <listitem>
-      <para><emphasis role="strong">Linux Kernel-&min-kernel;</emphasis></para>
-
-      <para>The reason for the kernel version requirement is that we specify
-      that version when building <application>glibc</application> in
-      <xref linkend="chapter-cross-tools"/> and
-      <xref linkend="chapter-building-system"/>, so the workarounds for
-      older kernels are not enabled and the compiled
-      <application>glibc</application> is slightly faster and smaller.
-      As at Feb 2024, &min-kernel; is the oldest kernel release still
-      supported by the kernel developers.  Some kernel releases older than
-      &min-kernel; may be still supported by third-party teams, but they
-      are not considered official upstream kernel releases; read
-      <ulink url='https://kernel.org/category/releases.html'/> for the
-      details.</para>
-
-      <para>If the host kernel is earlier than &min-kernel; you will need to replace
-      the kernel with a more up-to-date version. There are two ways
-      you can go about this. First, see if your Linux vendor provides a &min-kernel;
-      or later kernel package. If so, you may wish to install it. If your
-      vendor doesn't offer an acceptable kernel package, or you would prefer not to
-      install it, you can compile a kernel yourself. Instructions for
-      compiling the kernel and configuring the boot loader (assuming the host
-      uses GRUB) are located in <xref linkend="chapter-bootable"/>.</para>
-
-      <para>We require the host kernel to support UNIX 98 pseudo terminal
-      (PTY).  It should be enabled on all desktop or server distros shipping
-      Linux &min-kernel; or a newer kernel. If you are building a custom
-      host kernel, ensure <option>CONFIG_UNIX98_PTYS</option> is set to
-      <literal>y</literal> in the kernel configuration.</para>
-
     </listitem>
 
@@ -213,19 +190,8 @@
 }
 
-ver_kernel()
-{
-   kver=$(uname -r | grep -E -o '^[0-9\.]+')
-   if printf '%s\n' $1 $kver | sort --version-sort --check &amp;>/dev/null
-   then 
-     printf "OK:    Linux Kernel $kver >= $1\n"; return 0;
-   else 
-     printf "ERROR: Linux Kernel ($kver) is TOO OLD ($1 or later required)\n" "$kver"; 
-     return 1; 
-   fi
-}
-
 # Coreutils first because --version-sort needs Coreutils >= 7.0
 ver_check Coreutils      sort     8.1 || bail "Coreutils too old, stop"
 ver_check Bash           bash     3.2
+ver_check Bc             bc       1.07.0
 ver_check Binutils       ld       2.13.1
 ver_check Bison          bison    2.7
@@ -246,9 +212,4 @@
 ver_check Texinfo        texi2any 5.0
 ver_check Xz             xz       5.0.0
-ver_kernel &min-kernel;
-
-if mount | grep -q 'devpts on /dev/pts' &amp;&amp; [ -e /dev/ptmx ]
-then echo "OK:    Linux Kernel supports UNIX 98 PTY";
-else echo "ERROR: Linux Kernel does NOT support UNIX 98 PTY"; fi
 
 alias_check() {
Index: chapter02/stages.xml
===================================================================
--- chapter02/stages.xml	(revision 201aa93863b8999290f262baa52e487e01bfada3)
+++ chapter02/stages.xml	(revision e4b4c5a0b1ae2aa23095d957e7d63ca37c77b5eb)
@@ -65,27 +65,17 @@
     <itemizedlist>
       <listitem>
-         <para>The /mnt/lfs partition must be mounted.</para>
+        <para>You must boot the temporary system on the target machine.</para>
       </listitem>
 
       <listitem>
-        <para>A few operations, from <quote>Changing Ownership</quote> to
-        <quote>Entering the Chroot Environment,</quote> must be done as the
-        <systemitem class="username">root</systemitem> user, with the LFS
-        environment variable set for the &root; user.</para>
+        <para>A few operations, from
+        <quote>Preparing Virtual Kernel File Systems</quote> to
+        <quote>Setting up Environment,</quote> must be done.</para>
       </listitem>
 
       <listitem>
-         <para> When entering chroot, the LFS environment variable must be set
-         for <systemitem class="username">root</systemitem>. The LFS
-         variable is not used after the chroot environment has been entered.</para>
-      </listitem>
-
-      <listitem>
-         <para> The virtual file systems must be mounted.  This can be done
-         before or after entering chroot by changing to a host virtual terminal
-         and, as <systemitem class="username">root</systemitem>, running the
-         commands in
-         <xref linkend='ch-tools-bindmount'/> and
-         <xref linkend='ch-tools-kernfsmount' role='.'/></para>
+        <para>The operations in <xref linkend="ch-tools-lo"/> must be done
+        before starting or continuing from
+        <xref linkend="chapter-building-system" role='.'/></para>
       </listitem>
     </itemizedlist>
