Changeset 8bfae90 for BOOK/temp-system/common/choose.xml

Timestamp:

May 29, 2014, 12:40:16 AM (10 years ago)

Author:

Chris Staub <chris@…>

Branches:

clfs-3.0.0-systemd, master, systemd

Children:

e5ca899d

Parents:

cdc0f7c

Message:

Moved details about booting/chrooting from how.xml to choose.xml

File:

• BOOK/temp-system/common/choose.xml (modified) (2 diffs)

BOOK/temp-system/common/choose.xml

@@ -16 +16 @@
   rest there. Alternatively, you can chroot into the temporary system.</para>
 
-  <para os="b">The boot method is needed when you are building on a different
+  <para os="b">The <command>chroot</command> (change root) program is used to enter
+  a virtual environment and start a new shell whose root directory will be set
+  to the CLFS partition. This is very similar to rebooting and instructing the
+  kernel to mount the CLFS partition as the root partition.
+  The major advantage is that <quote>chrooting</quote> allows the builder to
+  continue using the host while CLFS is being built. While waiting for package
+  compilation to complete, a user can switch to a different virtual console
+  (VC) or X desktop and continue using the computer as normal.</para>
+
+  <para os="c">Some systems cannot be built by chrooting so they must be
+  booted instead. Generally, if you building for a different arch than
+  the host system, you must reboot because the kernel will likely not
+  support the target machine. Booting involves installing a few
+  additional packages that are needed for bootup, installing
+  boot-scripts, and building a miminal kernel.<!-- We also describe some
+  alternative booting methods in <xref linkend="ch-boot-whatnext"/> -->
+  The boot method is needed when you are building on a different
   architecture. For example, if you are building a PowerPC system from
   an x86, you can't chroot. The chroot method is for when you are
@@ -25 +41 @@
   wanting to run a different ABI, you will need to use the boot option.</para>
 
-  <para os="c">If you are in any doubt about this, you can try the following
+  <para os="d">If you are in any doubt about this, you can try the following
  commands to see if you can chroot:</para>
 
-<screen ><userinput>/tools/lib/libc.so.6
+<screen os="e"><userinput>/tools/lib/libc.so.6
 /tools/bin/gcc -v</userinput></screen>
 
-  <para>If either of these commands fail, you will have to follow the boot
+  <para os="f">If either of these commands fail, you will have to follow the boot
   method.</para>
 
-  <para>To chroot, you will also need a Linux Kernel-2.6.32 or greater
+  <para os="g">To chroot, you will also need a Linux Kernel-2.6.32 or greater
   (having been compiled with GCC-4.1.2 or greater). The reason for the
   kernel version requirement is that Glibc is built to generate the library
   for the smallest version of the Linux kernel expected to be supported.</para>
 
-  <para>To check your kernel version, run <command>cat /proc/version</command>
+  <para os="h">To check your kernel version, run <command>cat /proc/version</command>
   - if it does not say that you are running a 2.6.32 or later Linux kernel,
   compiled with GCC 4.1.2 or later, you cannot chroot.</para>
 
-  <para os="e">For the boot method, follow <xref linkend="chapter-boot"/>.</para>
+  <para os="i">For the boot method, follow <xref linkend="chapter-boot"/>.</para>
 
-  <para os="f">For the chroot method, follow <xref linkend="chapter-chroot"/>.</para>
+  <para os="j">For the chroot method, follow <xref linkend="chapter-chroot"/>.</para>
 
 </sect1>