[3f8be484] | 1 | <?xml version="1.0" encoding="ISO-8859-1"?> |
---|
[aa18ac0] | 2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" |
---|
| 3 | "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ |
---|
[3f8be484] | 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 | |
---|
[15138c5] | 13 | <para os="a"> There are two different ways you can proceed from this point |
---|
[398f5bd1] | 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 |
---|
[c2f6972] | 16 | rest there. Alternatively, you can chroot into the temporary system.</para> |
---|
[3f8be484] | 17 | |
---|
[040521bc] | 18 | <para os="b">The boot method is needed when you are building on a different |
---|
[398f5bd1] | 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 |
---|
[9aed5b3] | 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> |
---|
[a0acd90] | 26 | |
---|
[15138c5] | 27 | <para os="c">If you are in any doubt about this, you can try the following |
---|
| 28 | commands to see if you can chroot:</para> |
---|
[398f5bd1] | 29 | |
---|
[bc2e3fa] | 30 | <screen ><userinput>/tools/lib/libc.so.6 |
---|
| 31 | /tools/bin/gcc -v</userinput></screen> |
---|
[15138c5] | 32 | |
---|
[36aa076] | 33 | <para>If either of these commands fail, you will have to follow the boot |
---|
[15138c5] | 34 | method.</para> |
---|
| 35 | |
---|
[65ab9ce] | 36 | <para>To chroot, you will also need a Linux Kernel-2.6.32 or greater |
---|
| 37 | (having been compiled with GCC-4.1.2 or greater). The reason for the |
---|
[cbbd1e4] | 38 | kernel version requirement is that glibc is built to generate the library |
---|
[65ab9ce] | 39 | for the smallest version of the Linux kernel expected to be supported.</para> |
---|
[040521bc] | 40 | |
---|
| 41 | <para>To check your kernel version, run <command>cat /proc/version</command> |
---|
[65ab9ce] | 42 | - if it does not say that you are running a 2.6.32 or later Linux kernel, |
---|
| 43 | compiled with GCC 4.1.2 or later, you cannot chroot.</para> |
---|
[040521bc] | 44 | |
---|
[15138c5] | 45 | <para os="e">For the boot method, follow <xref linkend="chapter-boot"/>.</para> |
---|
| 46 | |
---|
| 47 | <para os="f">For the chroot method, follow <xref linkend="chapter-chroot"/>.</para> |
---|
[3f8be484] | 48 | |
---|
| 49 | </sect1> |
---|