kernel: adjust the instruction for mounting /boot

LFS and the host may use different /boot configuration, so do not assume
they'll share a /boot partition (two different /boot partition or only one
with separate /boot are possible).

1 files changed, 12 insertions, 6 deletions

diff --git a/chapter10/kernel.xml b/chapter10/kernel.xml
index ac104e4b4..e7bcfdb87 100644
--- a/chapter10/kernel.xml
+++ b/chapter10/kernel.xml
@@ -335,12 +335,18 @@ Device Drivers --->
     the <filename class="directory">/boot</filename> directory.</para>
 
     <caution>
-      <para>If the host system has a separate /boot partition, the files copied
-      below should go there. The easiest way to do that is to bind /boot on the
-      host (outside chroot) to /mnt/lfs/boot before proceeding.  As the
-      &root; user in the <emphasis>host system</emphasis>:</para>
-
-<screen role="nodump"><userinput>mount --bind /boot /mnt/lfs/boot</userinput></screen>
+      <para>If you've decided to use a separate &boot-dir; partition for the
+      LFS system (maybe sharing a &boot-dir; partition with the host
+      distro) , the files copied below should go there. The easiest way to
+      do that is to create the entry for &boot-dir; in &fstab; first (read
+      the previous section for details), then issue the following command
+      as the &root; user in the
+      <emphasis>chroot environment</emphasis>:</para>
+
+<screen role="nodump"><userinput>mount /boot</userinput></screen>
+
+      <para>The path to the device node is omitted in the command because
+      <command>mount</command> can read it from &fstab;.</para>
     </caution>
 
     <para>The path to the kernel image may vary depending on the platform being