source: BOOK/temp-system/common/choose.xml @ 44a25cc

Last change on this file since 44a25cc was 44a25cc, checked in by Chris Staub <chris@…>, 6 years ago

Updates to choose page

  • Property mode set to 100644
File size: 3.0 KB
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3  "" [
4  <!ENTITY % general-entities SYSTEM "../../general.ent">
5  %general-entities;
8<sect1 id="ch-temp-system-choose">
9  <?dbhtml filename="choose.html"?>
11  <title>To Boot or to Chroot?</title>
13  <para os="a"> There are two different ways you can proceed from this point
14  to build the final system. You can build a kernel, a bootloader, and
15  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>
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.
23  The major advantage is that <quote>chrooting</quote> allows the builder to
24  continue using the host while CLFS is being built. While waiting for package
25  compilation to complete, a user can switch to a different virtual console
26  (VC) or X desktop and continue using the computer as normal.</para>
28  <!-- We also describe some alternative booting methods in <xref linkend="ch-boot-whatnext"/> -->
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>
41  <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<screen os="e"><userinput>/tools/lib/
45/tools/bin/gcc -v</userinput></screen>
47  <para os="f">If either of these commands fail, you will have to follow the
48  boot method.</para>
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>
55  <para os="h">To check your kernel version, run <command>cat /proc/version</command>
56  - if it does not say that you are running a 2.6.32 or later Linux kernel,
57  compiled with GCC 4.1.2 or later, you cannot chroot.</para>
59  <para os="i">For the boot method, follow <xref linkend="chapter-boot"/>.</para>
61  <para os="j">For the chroot method, follow <xref linkend="chapter-chroot"/>.</para>
Note: See TracBrowser for help on using the repository browser.