Changeset 9d5337b for BOOK


Ignore:
Timestamp:
Oct 15, 2008, 11:47:17 AM (16 years ago)
Author:
Chris Staub <chris@…>
Branches:
clfs-1.2, clfs-2.1, clfs-3.0.0-systemd, clfs-3.0.0-sysvinit, master, systemd, sysvinit
Children:
b169dfe
Parents:
c5f3cf70
Message:

Text cleanup on the before-chroot page

File:
1 edited

Legend:

Unmodified
Added
Removed

  • BOOK/chroot/x86/before-chroot.xml

    rc5f3cf70 r9d5337b  
    1515    <para>Before we can enter the chroot we have to make sure that the system is
    1616    in the proper state. From this point on the <envar>${CLFS_TARGET}</envar>
    17     enviornment variable will no longer exist, so it will have no bearing on the
    18     rest of the book. From this point on, most packages will rely on
     17    environment variable will no longer exist, so it will have no bearing on the
     18    rest of the book - most packages will rely on
    1919    <command>config.guess</command> provided by
    2020    <xref linkend="ch-system-automake"/>. Packages that do not use autotools
    21     either do not care about the target triplet, or they have their own means
    22     of determining it's value.</para>
     21    either do not care about the target triplet, or have their own means
     22    of determining its value.</para>
    2323
    24     <para>In both cases, The information about the host cpu used to determine
     24    <para>In both cases, the information about the host cpu used to determine
    2525    the target triplet is gathered from the same place,
    2626    <command>uname -m</command>. Executing this command outside of the chroot
    27     aswell as inside the chroot will have the exact same output.</para>
     27    as well as inside the chroot will have the exact same output.</para>
    2828
    29    <para>If you're unsure if you're host and target have the same target
    30     triplet, you can use this test to determine what the hosts target triplet
     29   <para>If you're unsure if your host and target have the same target
     30    triplet, you can use this test to determine what the host's target triplet
    3131    is and if you need to take any steps to ensure that you don't build for the
    3232    wrong architecture. Extract the <xref linkend="ch-system-automake"/> tarball
    3333    and <command>cd</command> into the created directory. Then execute the
    34     following to see what they detected target triplet is by
    35     <command>config.guess</command>.</para>
     34    following to see what the detected target triplet is by
     35    <command>config.guess</command>:</para>
    3636
    3737<screen><userinput>lib/config.guess</userinput></screen>
    … …  
    5252
    5353    <para>To test if setarch does everything you need it to, execute the
    54     following command from inside of the <xref linkend="ch-system-automake"/>
     54    following command from inside the <xref linkend="ch-system-automake"/>
    5555    directory:</para>
    5656
    … …  
    9595    <para os="uuc">Extract the tarball and <command>cd</command> into the
    9696    created directory. To build the Uname Hack you must have the kernel sources
    97     for you currently running kernel available. Build the Uname Hack with the
     97    for your currently running kernel available. Build the Uname Hack with the
    9898    following or similar command:</para>
    9999
    … …  
    107107        <listitem>
    108108          <para>This parameter sets the value that the uts machine type will be
    109           changed to. Alternativley this could be set to i586 or i686.</para>
     109          changed to. Alternatively this could be set to i586 or i686.</para>
    110110        </listitem>
    111111      </varlistentry>
    … …  
    113113    </variablelist>
    114114
    115     <para os="uuf">In the top level directory of the Uname Hack pacakage you
    116     should see a file named uname_hack.ko. As soon as that module is loaded
    117     into the running kernel the output of <command>uname -m</command> will be
    118     affected immediately system-wide. Load the kernel module with the following
    119     command:</para>
     115    <para os="uuf">In the top level directory of the Uname Hack package you
     116    should see a file named <filename>uname_hack.ko</filename>. As soon as
     117    that module is loaded into the running kernel the output of
     118    <command>uname -m</command> will be affected immediately system-wide.
     119    Load the kernel module with the following command:</para>
    120120
    121121<screen os="uug"><userinput>insmod uname_hack.ko</userinput></screen>
    122122
    123123    <para os="uuh">To test if the Uname Hack is working properly, execute the
    124     following command from inside of the <xref linkend="ch-system-automake"/>
     124    following command from inside the <xref linkend="ch-system-automake"/>
    125125    directory:</para>
    126126
    … …  
    128128
    129129    <para os="uuj">The output of the above command should be the same as the
    130     <envar>${CLFS_TARGET}</envar> enviornment variable. If this is not the
    131     case, You can try and get help on the CLFS Support Mailing List or the
     130    <envar>${CLFS_TARGET}</envar> environment variable. If this is not the
     131    case, you can try and get help on the CLFS Support Mailing List or the
    132132    IRC Channel. See <xref linkend="ch-intro-askforhelp"/> for more
    133133    information.</para>
Note: See TracChangeset for help on using the changeset viewer.