source: temp-system/common/choose.xml @ e5be257

Last change on this file since e5be257 was e5be257, checked in by Jim Gifford <clfs@…>, 17 years ago

r3122@server (orig r1465): chris | 2006-04-24 22:04:33 -0700
Minor text/grammar fixes

  • Property mode set to 100644
File size: 1.7 KB
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//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 chroot into the temporary system.</para>
18  <para os="b">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>
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>
30<screen ><userinput>/tools/lib/
31/tools/bin/gcc -v</userinput></screen>
33  <para os="d">If any of these commands fail, you will have to follow the boot
34  method.</para>
36  <para os="e">For the boot method, follow <xref linkend="chapter-boot"/>.</para>
38  <para os="f">For the chroot method, follow <xref linkend="chapter-chroot"/>.</para>
Note: See TracBrowser for help on using the repository browser.