Changeset 9389c82


Ignore:
Timestamp:
May 29, 2014, 12:53:22 AM (10 years ago)
Author:
Chris Staub <chris@…>
Branches:
clfs-3.0.0-sysvinit, sysvinit
Children:
6cb444f
Parents:
704452b1
git-author:
Chris Staub <chris@…> (05/29/14 00:40:16)
git-committer:
Chris Staub <chris@…> (05/29/14 00:53:22)
Message:

Moved details about booting/chrooting from how.xml to choose.xml

Conflicts:

BOOK/introduction/common/how.xml

Location:
BOOK
Files:
6 edited

Legend:

Unmodified
Added
Removed

  • BOOK/introduction/common/changelog.xml

    r704452b1 r9389c82  
    3838
    3939    <listitem>
     40      <para>29 May 2014</para>
     41      <itemizedlist>
     42        <listitem>
     43          <para>[Chris] - Edited "how" page - removed details about
     44          booting/chrooting and moved them to the "choose" page for temp-system.</para>
     45        </listitem>
     46      </itemizedlist>
     47    </listitem>
     48
     49    <listitem>
    4050      <para>25 May 2014</para>
    4151      <itemizedlist>

  • BOOK/introduction/common/how.xml

    r704452b1 r9389c82  
    2222  your machine, you may wish to use a livecd. Most distributions provide
    2323  a livecd, which provides an environment to which you can add the required
    24   tools onto, allowing you to
    25   successfully follow the instructions in this book. Remember that if you
    26   reboot the livecd you will need to reconfigure the host environment before
    27   continuing with your build.</para>
     24  tools onto, allowing you to successfully follow the instructions in this
     25  book. Remember that if you reboot the livecd you will need to reconfigure
     26  the host environment before continuing with your build.</para>
    2827
    2928  <para><xref linkend="chapter-partitioning"/> of this book describes how
    … …  
    5453  <para>After we build our <quote>Cross-Tools</quote>, we start building
    5554  a very minimal working system in
    56   <filename class="directory">/tools</filename>. This minimal system will be
    57   built using the cross-toolchain in
    58   <filename class="directory">/cross-tools</filename>.</para>
     55  <filename class="directory">/tools</filename>, using the cross-toolchain in
     56  <filename class="directory">/cross-tools</filename>. Once the temporary
     57  system is finished, we perform a few additional tasks to prepare to
     58  enter this temporary build environment, either by booting or chrooting into
     59  it. For more details about the difference between these methods, see
     60  <xref linkend="ch-temp-system-choose"/>.</para>
    5961
    60   <para>In <xref linkend="chapter-building-system"/>, the full CLFS system is
    61   built. Depending on the system you are cross-compiling for, you will either
    62   boot the minimal temp-system on the target machine, or chroot into it.</para>
     62  <para>In <xref linkend="chapter-building-system"/>, after having booted
     63  or chrooted into the temporary build environment, the full CLFS system is
     64  built.</para>
    6365
    64   <para>The <command>chroot</command> (change root) program is used to enter
    65   a virtual environment and start a new shell whose root directory will be set
    66   to the CLFS partition. This is very similar to rebooting and instructing the
    67   kernel to mount the CLFS partition as the root partition.
    68   The major advantage is that <quote>chrooting</quote> allows the builder to
    69   continue using the host while CLFS is being built. While waiting for package
    70   compilation to complete, a user can switch to a different virtual console
    71   (VC) or X desktop and continue using the computer as normal.</para>
    72 
    73   <para>Some systems cannot be built by chrooting so they must be
    74   booted instead. Generally, if you building for a different arch than
    75   the host system, you must reboot because the kernel will likely not
    76   support the target machine. Booting involves installing a few
    77   additional packages that are needed for bootup, installing
    78   bootscripts, and building a miminal kernel.<!-- We also describe some
    79   alternative booting methods in <xref linkend="ch-boot-whatnext"/> --></para>
    80 
    81   <para> To finish the installation, the CLFS-Bootscripts are set up in
    82   <xref linkend="chapter-system-config"/>, and the kernel and boot loader are set
    83   up in <xref linkend="chapter-bootable"/>. <xref linkend="chapter-finalizing"/>
     66  <para>To finish the installation, several configuration files are created in
     67  <xref linkend="chapter-system-config"/>, and the kernel and boot loader are
     68  set up in <xref linkend="chapter-bootable"/>.
     69  <xref linkend="chapter-finalizing"/>
    8470  contains information on furthering the CLFS experience beyond this book.
    8571  After the steps in this book have been implemented, the computer will be

  • BOOK/temp-system/common/choose.xml

    r704452b1 r9389c82  
    1616  rest there. Alternatively, you can chroot into the temporary system.</para>
    1717
    18   <para os="b">The boot method is needed when you are building on a different
     18  <para os="b">The <command>chroot</command> (change root) program is used to enter
     19  a virtual environment and start a new shell whose root directory will be set
     20  to the CLFS partition. This is very similar to rebooting and instructing the
     21  kernel to mount the CLFS partition as the root partition.
     22  The major advantage is that <quote>chrooting</quote> allows the builder to
     23  continue using the host while CLFS is being built. While waiting for package
     24  compilation to complete, a user can switch to a different virtual console
     25  (VC) or X desktop and continue using the computer as normal.</para>
     26
     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
    1935  architecture. For example, if you are building a PowerPC system from
    2036  an x86, you can't chroot. The chroot method is for when you are
    … …  
    2541  wanting to run a different ABI, you will need to use the boot option.</para>
    2642
    27   <para os="c">If you are in any doubt about this, you can try the following
     43  <para os="d">If you are in any doubt about this, you can try the following
    2844 commands to see if you can chroot:</para>
    2945
    30 <screen ><userinput>/tools/lib/libc.so.6
     46<screen os="e"><userinput>/tools/lib/libc.so.6
    3147/tools/bin/gcc -v</userinput></screen>
    3248
    33   <para>If either of these commands fail, you will have to follow the boot
     49  <para os="f">If either of these commands fail, you will have to follow the boot
    3450  method.</para>
    3551
    36   <para>To chroot, you will also need a Linux Kernel-2.6.32 or greater
     52  <para os="g">To chroot, you will also need a Linux Kernel-2.6.32 or greater
    3753  (having been compiled with GCC-4.1.2 or greater). The reason for the
    3854  kernel version requirement is that Glibc is built to generate the library
    3955  for the smallest version of the Linux kernel expected to be supported.</para>
    4056
    41   <para>To check your kernel version, run <command>cat /proc/version</command>
     57  <para os="h">To check your kernel version, run <command>cat /proc/version</command>
    4258  - if it does not say that you are running a 2.6.32 or later Linux kernel,
    4359  compiled with GCC 4.1.2 or later, you cannot chroot.</para>
    4460
    45   <para os="e">For the boot method, follow <xref linkend="chapter-boot"/>.</para>
     61  <para os="i">For the boot method, follow <xref linkend="chapter-boot"/>.</para>
    4662
    47   <para os="f">For the chroot method, follow <xref linkend="chapter-chroot"/>.</para>
     63  <para os="j">For the chroot method, follow <xref linkend="chapter-chroot"/>.</para>
    4864
    4965</sect1>

  • BOOK/temp-system/mips64/choose.xml

    r704452b1 r9389c82  
    2323    xpointer="xpointer(//*[@os='c'])"/>
    2424
    25 <screen ><userinput>/tools/lib/libc.so.6
     25    <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
     26    href="../common/choose.xml"
     27    xpointer="xpointer(//*[@os='d'])"/>
     28
     29<screen os="e"><userinput>/tools/lib/libc.so.6
    2630/tools/lib32/libc.so.6
    2731/tools/lib64/libc.so.6
    … …  
    3034    <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
    3135    href="../multilib/choose.xml"
    32     xpointer="xpointer(//*[@os='d'])"/>
    33 
    34   <para>To chroot, you will also need a Linux Kernel-2.6.32 or greater (having been compiled with GCC-4.1.2 or greater). The reason for the kernel version requirement is that Glibc is built to generate the library for the smallest version of the Linux kernel expected to be supported.</para>
    35 
    36   <para>To check your kernel version, run <command>cat /proc/version</command> - if it does not say that you are running a 2.6.32 or later Linux kernel, compiled with GCC 4.1.2 or later, you cannot chroot.</para>
     36    xpointer="xpointer(//*[@os='f'])"/>
    3737
    3838    <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
    3939    href="../common/choose.xml"
    40     xpointer="xpointer(//*[@os='e'])"/>
     40    xpointer="xpointer(//*[@os='g'])"/>
    4141
    4242    <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
    4343    href="../common/choose.xml"
    44     xpointer="xpointer(//*[@os='f'])"/>
     44    xpointer="xpointer(//*[@os='h'])"/>
     45
     46    <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
     47    href="../common/choose.xml"
     48    xpointer="xpointer(//*[@os='i'])"/>
     49
     50    <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
     51    href="../common/choose.xml"
     52    xpointer="xpointer(//*[@os='j'])"/>
    4553
    4654</sect1>

  • BOOK/temp-system/multilib/choose.xml

    r704452b1 r9389c82  
    2323    xpointer="xpointer(//*[@os='c'])"/>
    2424
    25 <screen ><userinput>/tools/lib/libc.so.6
     25    <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
     26    href="../common/choose.xml"
     27    xpointer="xpointer(//*[@os='d'])"/>
     28
     29<screen os="e"><userinput>/tools/lib/libc.so.6
    2630/tools/lib64/libc.so.6
    2731/tools/bin/gcc -v</userinput></screen>
    2832
    29   <para os="d">If any of these commands fail, you will have to follow the boot
     33  <para os="f">If any of these commands fail, you will have to follow the boot
    3034  method.</para>
    31 
    32   <para>To chroot, you will also need a Linux Kernel-2.6.32 or greater
    33   (having been compiled with GCC-4.1.2 or greater). The reason for the
    34   kernel version requirement is that Glibc is built to generate the library
    35   for the smallest version of the Linux kernel expected to be supported.</para>
    36 
    37   <para>To check your kernel version, run <command>cat /proc/version</command>
    38   - if it does not say that you are running a 2.6.32 or later Linux kernel,
    39   compiled with GCC 4.1.2 or later, you cannot chroot.</para>
    4035
    4136    <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
    4237    href="../common/choose.xml"
    43     xpointer="xpointer(//*[@os='e'])"/>
     38    xpointer="xpointer(//*[@os='g'])"/>
    4439
    4540    <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
    4641    href="../common/choose.xml"
    47     xpointer="xpointer(//*[@os='f'])"/>
     42    xpointer="xpointer(//*[@os='h'])"/>
     43
     44    <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
     45    href="../common/choose.xml"
     46    xpointer="xpointer(//*[@os='i'])"/>
     47
     48    <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
     49    href="../common/choose.xml"
     50    xpointer="xpointer(//*[@os='j'])"/>
    4851
    4952</sect1>

  • BOOK/temp-system/ppc64/choose.xml

    r704452b1 r9389c82  
    1919    xpointer="xpointer(//*[@os='b'])"/>
    2020
     21    <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
     22    href="../common/choose.xml"
     23    xpointer="xpointer(//*[@os='c'])"/>
     24
    2125  <para>Powerpc64 is slightly different from some of the other
    2226  architectures, because a 64-bit kernel running 32-bit userspace can
    … …  
    3640    <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
    3741    href="../common/choose.xml"
    38     xpointer="xpointer(//*[@os='e'])"/>
     42    xpointer="xpointer(//*[@os='i'])"/>
    3943
    4044    <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
    4145    href="../common/choose.xml"
    42     xpointer="xpointer(//*[@os='f'])"/>
     46    xpointer="xpointer(//*[@os='j'])"/>
    4347
    4448</sect1>
Note: See TracChangeset for help on using the changeset viewer.