Ignore:
Timestamp:
May 29, 2014, 12:40:16 AM (9 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:
1 edited

Legend:

Unmodified
Added
Removed
  • BOOK/temp-system/common/choose.xml

    rcdc0f7c r8bfae90  
    1616  rest there. Alternatively, you can chroot into the temporary system.</para>
    1717
    18   <para os="b">The boot method is needed when you are building on a different
     18  <para os="b">The <command>chroot</command> (change root) program is used to enter
     19  a virtual environment and start a new shell whose root directory will be set
     20  to the CLFS partition. This is very similar to rebooting and instructing the
     21  kernel to mount the CLFS partition as the root partition.
     22  The major advantage is that <quote>chrooting</quote> allows the builder to
     23  continue using the host while CLFS is being built. While waiting for package
     24  compilation to complete, a user can switch to a different virtual console
     25  (VC) or X desktop and continue using the computer as normal.</para>
     26
     27  <para os="c">Some systems cannot be built by chrooting so they must be
     28  booted instead. Generally, if you building for a different arch than
     29  the host system, you must reboot because the kernel will likely not
     30  support the target machine. Booting involves installing a few
     31  additional packages that are needed for bootup, installing
     32  boot-scripts, and building a miminal kernel.<!-- We also describe some
     33  alternative booting methods in <xref linkend="ch-boot-whatnext"/> -->
     34  The boot method is needed when you are building on a different
    1935  architecture. For example, if you are building a PowerPC system from
    2036  an x86, you can't chroot. The chroot method is for when you are
     
    2541  wanting to run a different ABI, you will need to use the boot option.</para>
    2642
    27   <para os="c">If you are in any doubt about this, you can try the following
     43  <para os="d">If you are in any doubt about this, you can try the following
    2844 commands to see if you can chroot:</para>
    2945
    30 <screen ><userinput>/tools/lib/libc.so.6
     46<screen os="e"><userinput>/tools/lib/libc.so.6
    3147/tools/bin/gcc -v</userinput></screen>
    3248
    33   <para>If either of these commands fail, you will have to follow the boot
     49  <para os="f">If either of these commands fail, you will have to follow the boot
    3450  method.</para>
    3551
    36   <para>To chroot, you will also need a Linux Kernel-2.6.32 or greater
     52  <para os="g">To chroot, you will also need a Linux Kernel-2.6.32 or greater
    3753  (having been compiled with GCC-4.1.2 or greater). The reason for the
    3854  kernel version requirement is that Glibc is built to generate the library
    3955  for the smallest version of the Linux kernel expected to be supported.</para>
    4056
    41   <para>To check your kernel version, run <command>cat /proc/version</command>
     57  <para os="h">To check your kernel version, run <command>cat /proc/version</command>
    4258  - if it does not say that you are running a 2.6.32 or later Linux kernel,
    4359  compiled with GCC 4.1.2 or later, you cannot chroot.</para>
    4460
    45   <para os="e">For the boot method, follow <xref linkend="chapter-boot"/>.</para>
     61  <para os="i">For the boot method, follow <xref linkend="chapter-boot"/>.</para>
    4662
    47   <para os="f">For the chroot method, follow <xref linkend="chapter-chroot"/>.</para>
     63  <para os="j">For the chroot method, follow <xref linkend="chapter-chroot"/>.</para>
    4864
    4965</sect1>
Note: See TracChangeset for help on using the changeset viewer.