- Timestamp:
- Feb 21, 2006, 2:24:08 AM (19 years ago)
- Branches:
- clfs-1.2, clfs-2.1, clfs-3.0.0-systemd, clfs-3.0.0-sysvinit, master, systemd, sysvinit
- Children:
- 953b2eb
- Parents:
- eba8490
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
BOOK/temp-system/common/choose.xml
reba8490 r398f5bd1 11 11 <title>To Boot or to Chroot?</title> 12 12 13 <para>The boot method is for when you are building on a different architecture. 14 Like building PowerPC and x86, you can't chroot.</para> 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. 15 17 16 <para>For the boot method, follow to <xref linkend="chapter-boot"/>.</para> 17 18 <para>The chroot method is for when you are building on the same architecture, 19 Like building x86 and x86, you simply just chroot. The rule of thumb 20 here is if the architectures match and you are running the same series kernel 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 21 24 you can just chroot. If you aren't running the same series kernel, or are 22 25 wanting to run a different ABI, you will need to use the boot option.</para> 23 26 24 <para>For the chroot method, follow to <xref linkend="chapter-chroot"/>.</para> 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> 25 30 26 31 </sect1>
Note:
See TracChangeset
for help on using the changeset viewer.