source: BOOK/temp-system/common/choose.xml @ 8bfae90

clfs-3.0.0-systemdsystemd
Last change on this file since 8bfae90 was 8bfae90, checked in by Chris Staub <chris@…>, 6 years ago

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

  • Property mode set to 100644
File size: 3.3 KB
Line 
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
4  <!ENTITY % general-entities SYSTEM "../../general.ent">
5  %general-entities;
6]>
7
8<sect1 id="ch-temp-system-choose">
9  <?dbhtml filename="choose.html"?>
10
11  <title>To Boot or to Chroot?</title>
12
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 chroot into the temporary system.</para>
17
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
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>
42
43  <para os="d">If you are in any doubt about this, you can try the following
44 commands to see if you can chroot:</para>
45
46<screen os="e"><userinput>/tools/lib/libc.so.6
47/tools/bin/gcc -v</userinput></screen>
48
49  <para os="f">If either of these commands fail, you will have to follow the boot
50  method.</para>
51
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>
56
57  <para os="h">To check your kernel version, run <command>cat /proc/version</command>
58  - if it does not say that you are running a 2.6.32 or later Linux kernel,
59  compiled with GCC 4.1.2 or later, you cannot chroot.</para>
60
61  <para os="i">For the boot method, follow <xref linkend="chapter-boot"/>.</para>
62
63  <para os="j">For the chroot method, follow <xref linkend="chapter-chroot"/>.</para>
64
65</sect1>
Note: See TracBrowser for help on using the repository browser.