Changeset 2484938 for final-preps


Ignore:
Timestamp:
Sep 15, 2006, 7:06:38 AM (18 years ago)
Author:
Chris Staub <chris@…>
Children:
6ec9929
Parents:
142e52c5
Message:

Change occurences of $VARIABLE to $\{VARIABLE\} for consistency

Location:
final-preps
Files:
5 edited

Legend:

Unmodified
Added
Removed
  • final-preps/aboutclfs.xml

    r142e52c5 r2484938  
    99  <?dbhtml filename="aboutclfs.html"?>
    1010
    11   <title>About $CLFS</title>
     11  <title>About ${CLFS}</title>
    1212
    1313  <para>Throughout this book, the environment variable <envar>CLFS</envar> will
     
    1616  Check that the <envar>CLFS</envar> variable is set up properly with:</para>
    1717
    18 <screen><userinput>echo $CLFS</userinput></screen>
     18<screen><userinput>echo ${CLFS}</userinput></screen>
    1919
    2020  <para>Make sure the output shows the path to the CLFS partition's mount
     
    2626
    2727  <para>Having this variable set is beneficial in that commands such as
    28   <command>install -dv $CLFS/tools</command> can be typed literally. The shell
    29   will automatically replace <quote>$CLFS</quote> with
     28  <command>install -dv ${CLFS}/tools</command> can be typed literally. The shell
     29  will automatically replace <quote>${CLFS}</quote> with
    3030  <quote>/mnt/clfs</quote> (or whatever the variable was set to) when it
    3131  processes the command line.</para>
    3232
    33   <para>If you haven't created the <filename class="directory">$CLFS</filename>
     33  <para>If you haven't created the <filename class="directory">${CLFS}</filename>
    3434  directory, do so at this time by issuing the following commands:</para>
    3535
    36 <screen><userinput>install -dv $CLFS</userinput></screen>
     36<screen><userinput>install -dv ${CLFS}</userinput></screen>
    3737
    38   <para>Do not forget to check that <envar>$CLFS</envar> is set whenever
     38  <para>Do not forget to check that <envar>${CLFS}</envar> is set whenever
    3939  you leave and reenter the current working environment (as when doing a
    4040  <quote>su</quote> to <systemitem class="username">root</systemitem> or
  • final-preps/addinguser.xml

    r142e52c5 r2484938  
    7979
    8080  <para>Grant <systemitem class="username">clfs</systemitem> full access to
    81   <filename class="directory">$CLFS/cross-tools</filename> and
    82   <filename class="directory">$CLFS/tools</filename> by making <systemitem
     81  <filename class="directory">${CLFS}/cross-tools</filename> and
     82  <filename class="directory">${CLFS}/tools</filename> by making <systemitem
    8383  class="username">clfs</systemitem> the directorys' owner:</para>
    8484
    85 <screen><userinput>chown -v clfs $CLFS/tools
    86 chown -v clfs $CLFS/cross-tools</userinput></screen>
     85<screen><userinput>chown -v clfs ${CLFS}/tools
     86chown -v clfs ${CLFS}/cross-tools</userinput></screen>
    8787
    8888  <para>If a separate working directory was created as suggested,
    8989  give user <systemitem class="username">clfs</systemitem> ownership of this directory:</para>
    9090
    91 <screen><userinput>chown -v clfs $CLFS/sources</userinput></screen>
     91<screen><userinput>chown -v clfs ${CLFS}/sources</userinput></screen>
    9292
    9393  <para>Next, login as user <systemitem class="username">clfs</systemitem>.
  • final-preps/creatingcrossdir.xml

    r142e52c5 r2484938  
    99  <?dbhtml filename="creatingcrossdir.html"?>
    1010
    11   <title>Creating the $CLFS/cross-tools Directory</title>
     11  <title>Creating the ${CLFS}/cross-tools Directory</title>
    1212
    1313  <para>The cross-binutils and cross-compiler built in
    1414  <xref linkend="chapter-cross-tools"/> will be installed under
    15   <filename class="directory">$CLFS/cross-tools</filename> to keep them
     15  <filename class="directory">${CLFS}/cross-tools</filename> to keep them
    1616  separate from the host programs. The programs compiled here are
    1717  cross-tools and will not be a part of the final CLFS system or the
     
    2222  <systemitem class="username">root</systemitem>:</para>
    2323
    24 <screen><userinput>install -dv $CLFS/cross-tools</userinput></screen>
     24<screen><userinput>install -dv ${CLFS}/cross-tools</userinput></screen>
    2525
    2626  <para>The next step is to create a <filename
     
    2929  Run this command as  <systemitem class="username">root</systemitem> as well:</para>
    3030
    31 <screen><userinput>ln -sv $CLFS/cross-tools /</userinput></screen>
     31<screen><userinput>ln -sv ${CLFS}/cross-tools /</userinput></screen>
    3232
    3333  <para>The symlink isn't technically necessary (though the book's
    3434  instructions do assume its existence), but is there mainly for
    35   consistency (because /tools is also symlinked to $CLFS/tools) and to
     35  consistency (because /tools is also symlinked to ${CLFS}/tools) and to
    3636  simplify the installation of the cross-compile tools.</para>
    3737
  • final-preps/creatingtoolsdir.xml

    r142e52c5 r2484938  
    99  <?dbhtml filename="creatingtoolsdir.html"?>
    1010
    11   <title>Creating the $CLFS/tools Directory</title>
     11  <title>Creating the ${CLFS}/tools Directory</title>
    1212
    1313  <para>All programs compiled in <xref linkend="chapter-temp-system"/>
    14   will be installed under <filename class="directory">$CLFS/tools</filename>
     14  will be installed under <filename class="directory">${CLFS}/tools</filename>
    1515  to keep them separate from the programs compiled in <xref
    1616  linkend="chapter-building-system"/>. The programs compiled here are
     
    2424  <systemitem class="username">root</systemitem>:</para>
    2525
    26 <screen><userinput>install -dv $CLFS/tools</userinput></screen>
     26<screen><userinput>install -dv ${CLFS}/tools</userinput></screen>
    2727
    2828  <para>The next step is to create a <filename class="symlink">/tools</filename>
     
    3131  class="username">root</systemitem> as well:</para>
    3232
    33 <screen><userinput>ln -sv $CLFS/tools /</userinput></screen>
     33<screen><userinput>ln -sv ${CLFS}/tools /</userinput></screen>
    3434
    3535  <note>
  • final-preps/settingenviron.xml

    r142e52c5 r2484938  
    1717
    1818<screen os="b"><userinput>cat &gt; ~/.bash_profile &lt;&lt; "EOF"
    19 <literal>exec env -i HOME=$HOME TERM=$TERM PS1='\u:\w\$ ' /bin/bash</literal>
     19<literal>exec env -i HOME=${HOME} TERM=${TERM} PS1='\u:\w\$ ' /bin/bash</literal>
    2020EOF</userinput></screen>
    2121
     
    5656  the shell will always search the <envar>PATH</envar> when a program is to
    5757  be run. As such, the shell will find the newly compiled tools in
    58   <filename class="directory">$CLFS/cross-tools</filename> as soon as they are
     58  <filename class="directory">/cross-tools</filename> as soon as they are
    5959  available without remembering a previous version of the same program in a
    6060  different location.</para>
Note: See TracChangeset for help on using the changeset viewer.