1 | <?xml version="1.0" encoding="ISO-8859-1"?> |
---|
2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" |
---|
3 | "http://www.oasis-open.org/docbook/xml/4.4/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> 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. The other option is to chroot into the temporary system.</para> |
---|
17 | |
---|
18 | <para>The boot method is for when you are building on a different |
---|
19 | architecture. For example, if you are building a PowerPC system from |
---|
20 | an x86, you can't chroot. The chroot method is for when you are |
---|
21 | building on the same architecture. If you are building on, and for, |
---|
22 | an x86 system, you can simply chroot. The rule of thumb here is if |
---|
23 | the architectures match and you are running the same series kernel |
---|
24 | you can just chroot. If you aren't running the same series kernel, or are |
---|
25 | wanting to run a different ABI, you will need to use the boot option.</para> |
---|
26 | |
---|
27 | <para>For the boot method, follow <xref linkend="chapter-boot"/>.</para> |
---|
28 | |
---|
29 | <para>For the chroot method, follow <xref linkend="chapter-chroot"/>.</para> |
---|
30 | |
---|
31 | </sect1> |
---|