Changeset 15bbf0e
- Timestamp:
- May 30, 2014, 8:22:50 AM (10 years ago)
- Branches:
- clfs-3.0.0-sysvinit, sysvinit
- Children:
- 452e11e
- Parents:
- 06f33c6
- git-author:
- Chris Staub <chris@…> (05/30/14 08:21:33)
- git-committer:
- Chris Staub <chris@…> (05/30/14 08:22:50)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
BOOK/temp-system/common/choose.xml
r06f33c6 r15bbf0e 14 14 to build the final system. You can build a kernel, a bootloader, and 15 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> 16 rest there. Alternatively, you can mount a few virtual filesystems and 17 chroot into the temporary system.</para> 17 18 18 <para os="b">The <command>chroot</command> (change root) program is used to enter19 a virtual environment and start a new shell whose root directory will be set20 to the CLFS partition. This is very similar to rebooting and instructing the21 kernel to mount the CLFS partition as the root partition.19 <para os="b">The <command>chroot</command> (change root) program is used to 20 enter a virtual environment and start a new shell whose root directory will 21 be set to the CLFS partition. This is very similar to rebooting and 22 instructing the kernel to mount the CLFS partition as the root partition. 22 23 The major advantage is that <quote>chrooting</quote> allows the builder to 23 24 continue using the host while CLFS is being built. While waiting for package … … 25 26 (VC) or X desktop and continue using the computer as normal.</para> 26 27 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> 28 <!-- We also describe some alternative booting methods in <xref linkend="ch-boot-whatnext"/> --> 29 30 <para os="c">The main downside to chrooting is that you are more limited in 31 when you can use it - booting will always work for any CLFS build, but the 32 chroot method can only be used when you are building on the same 33 architecture. For example, if you are building on, and for, an x86 system, 34 you can simply chroot. Booting is required when you are compiling for a 35 different architecture, such as building a PowerPC system from an x86. The 36 rule of thumb here is that if the architectures match and you are running 37 the same series kernel you can just chroot. If you aren't running the same 38 series kernel, or are wanting to run a different ABI, you will need to use 39 the boot option.</para> 42 40 43 41 <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>42 commands to see if you can chroot:</para> 45 43 46 44 <screen os="e"><userinput>/tools/lib/libc.so.6 47 45 /tools/bin/gcc -v</userinput></screen> 48 46 49 <para os="f">If either of these commands fail, you will have to follow the boot50 method.</para>47 <para os="f">If either of these commands fail, you will have to follow the 48 boot method.</para> 51 49 52 <para os="g">To chroot, you will also need a Linux Kernel -2.6.32 or greater53 (having been compiled with GCC-4.1.2 or greater). The reason for the54 kernel version requirement is that Glibc is built to generate the library55 for thesmallest version of the Linux kernel expected to be supported.</para>50 <para os="g">To chroot, you will also need a Linux Kernel, version 51 2.6.32 or higher, having been compiled with GCC-4.1.2 or greater. 52 This is required because Glibc was built to generate libraries for the 53 smallest version of the Linux kernel expected to be supported.</para> 56 54 57 55 <para os="h">To check your kernel version, run <command>cat /proc/version</command>
Note:
See TracChangeset
for help on using the changeset viewer.