Changes in / [452e11e:cdf768f]


Ignore:
File:
1 edited

Legend:

Unmodified
Added
Removed

  • BOOK/temp-system/common/choose.xml

    r452e11e rcdf768f  
    1414  to build the final system. You can build a kernel, a bootloader, and
    1515  a few other utilities, boot into the temporary system, and build the
    16   rest there. Alternatively, you can mount a few virtual filesystems and
    17   chroot into the temporary system.</para>
     16  rest there. Alternatively, you can chroot into the temporary system.</para>
    1817
    19   <para os="b">The <command>chroot</command> (change root) program is used to
    20   enter a virtual environment and start a new shell whose root directory will
    21   be set to the CLFS partition. This is very similar to rebooting and
    22   instructing the kernel to mount the CLFS partition as the root partition.
     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.
    2322  The major advantage is that <quote>chrooting</quote> allows the builder to
    2423  continue using the host while CLFS is being built. While waiting for package
    … …  
    2625  (VC) or X desktop and continue using the computer as normal.</para>
    2726
    28   <!-- We also describe some alternative booting methods in <xref linkend="ch-boot-whatnext"/> -->
    29 
    30   <para os="c">The main downside to chrooting is that you are more limited in
    31   when you can use it - booting will always work for any CLFS build, but the
    32   chroot method can only be used when you are building on the same
    33   architecture. For example, if you are building on, and for, an x86 system,
    34   you can simply chroot. Booting is required when you are compiling for a
    35   different architecture, such as building a PowerPC system from an x86. The
    36   rule of thumb here is that if the architectures match and you are running
    37   the same series kernel you can just chroot. If you aren't running the same
    38   series kernel, or are wanting to run a different ABI, you will need to use
    39   the boot option.</para>
     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
     35  architecture. For example, if you are building a PowerPC system from
     36  an x86, you can't chroot. The chroot method is for when you are
     37  building on the same architecture. If you are building on, and for,
     38  an x86 system, you can simply chroot. The rule of thumb here is if
     39  the architectures match and you are running the same series kernel
     40  you can just chroot. If you aren't running the same series kernel, or are
     41  wanting to run a different ABI, you will need to use the boot option.</para>
    4042
    4143  <para os="d">If you are in any doubt about this, you can try the following
    42   commands to see if you can chroot:</para>
     44 commands to see if you can chroot:</para>
    4345
    4446<screen os="e"><userinput>/tools/lib/libc.so.6
    4547/tools/bin/gcc -v</userinput></screen>
    4648
    47   <para os="f">If either of these commands fail, you will have to follow the
    48   boot method.</para>
     49  <para os="f">If either of these commands fail, you will have to follow the boot
     50  method.</para>
    4951
    50   <para os="g">To chroot, you will also need a Linux Kernel, version
    51   2.6.32 or higher, having been compiled with GCC-4.1.2 or greater.
    52   This is required because Glibc was built to generate libraries for the
    53   smallest version of the Linux kernel expected to be supported.</para>
     52  <para os="g">To chroot, you will also need a Linux Kernel-2.6.32 or greater
     53  (having been compiled with GCC-4.1.2 or greater). The reason for the
     54  kernel version requirement is that Glibc is built to generate the library
     55  for the smallest version of the Linux kernel expected to be supported.</para>
    5456
    5557  <para os="h">To check your kernel version, run <command>cat /proc/version</command>
Note: See TracChangeset for help on using the changeset viewer.