Changeset bba53b5 for BOOK/chroot/x86


Ignore:
Timestamp:
Jul 19, 2008, 3:35:38 PM (16 years ago)
Author:
Joe Ciccone <jciccone@…>
Branches:
clfs-1.2, clfs-2.1, clfs-3.0.0-systemd, clfs-3.0.0-sysvinit, master, systemd, sysvinit
Children:
a7ad070
Parents:
3390ed6
Message:

Update Date and add an explanation to the option that determines the uts machine type when compiling the uname hack module.

File:
1 edited

Legend:

Unmodified
Added
Removed

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

    r3390ed6 rbba53b5  
    100100<screen os="uud"><userinput>make uname_hack_fake_machine=i486</userinput></screen>
    101101
    102     <para os="uue">In the top level directory of the Uname Hack pacakage you
     102    <variablelist os="uue">
     103      <title>The meaning of the make and install options:</title>
     104
     105      <varlistentry os="uue1">
     106        <term><parameter>uname_hack_fake_machine=i486</parameter></term>
     107        <listitem>
     108          <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>
     110        </listitem>
     111      </varlistentry>
     112
     113    </variablelist>
     114
     115    <para os="uuf">In the top level directory of the Uname Hack pacakage you
    103116    should see a file named uname_hack.ko. As soon as that module is loaded
    104117    into the running kernel the output of <command>uname -m</command> will be
    … …  
    106119    command:</para>
    107120
    108 <screen os="uuf"><userinput>insmod uname_hack.ko</userinput></screen>
     121<screen os="uug"><userinput>insmod uname_hack.ko</userinput></screen>
    109122
    110     <para os="uug">To test if the Uname Hack is working properly, execute the
     123    <para os="uuh">To test if the Uname Hack is working properly, execute the
    111124    following command from inside of the <xref linkend="ch-system-automake"/>
    112125    directory:</para>
    113126
    114 <screen os="uuh"><userinput>lib/config.guess</userinput></screen>
     127<screen os="uui"><userinput>lib/config.guess</userinput></screen>
    115128
    116     <para os="uui">The output of the above command should be the same as the
     129    <para os="uuj">The output of the above command should be the same as the
    117130    <envar>${CLFS_TARGET}</envar> enviornment variable. If this is not the
    118131    case, You can try and get help on the CLFS Support Mailing List or the
Note: See TracChangeset for help on using the changeset viewer.