Ignore:
Timestamp:
02/01/2004 09:49:10 PM (20 years ago)
Author:
Alex Gronenwoud <alex@…>
Branches:
10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
Children:
247acde
Parents:
c288d97
Message:

Replacing several <userinput> tags by <command>.

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3203 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:
1 edited

Legend:

Unmodified
Added
Removed

  • chapter06/chapter06.xml

    rc288d97 r90e3cb3  
    6969the packages we need. Before you can chroot, however, you need to become
    7070<emphasis>root</emphasis>, since only <emphasis>root</emphasis>
    71 can execute the <userinput>chroot</userinput> command.</para>
     71can execute the <command>chroot</command> command.</para>
    7272
    7373<para>Just like earlier, ensure the LFS environment variable is set up properly
    7474by running <userinput>echo $LFS</userinput> and ensuring it shows the path to
    7575your LFS partition's mount point, which is
    76 <filename class="directory">/mnt/lfs</filename> if you followed our
    77 example.</para>
     76<filename class="directory">/mnt/lfs</filename> if you followed our example.</para>
    7877
    7978<para>Become <emphasis>root</emphasis> and run the following command
    … …  
    8584&nbsp;&nbsp;&nbsp;&nbsp;/tools/bin/bash --login +h</userinput></screen>
    8685
    87 <para>The <userinput>-i</userinput> option given to the
    88 <userinput>env</userinput> command will clear all variables of the chroot
     86<para>The <emphasis>-i</emphasis> option given to the
     87<command>env</command> command will clear all variables of the chroot
    8988environment. After that, only the HOME, TERM, PS1 and PATH variables are
    9089set again. The TERM=$TERM construct will set the TERM variable inside chroot
    9190to the same value as outside chroot; this variable is needed for programs
    92 like <userinput>vim</userinput> and <userinput>less</userinput> to operate
     91like <command>vim</command> and <command>less</command> to operate
    9392properly. If you need other variables present, such as CFLAGS or CXXFLAGS,
    9493this is a good place to set them again.</para>
    … …  
    104103as soon as its final version is installed. Well, at least when the shell
    105104doesn't remember the locations of executed binaries -- for this reason hashing
    106 is switched off by passing the <userinput>+h</userinput> option to
    107 <userinput>bash</userinput>.</para>
     105is switched off by passing the <emphasis>+h</emphasis> option to
     106<command>bash</command>.</para>
    108107
    109108<para>You have to make sure all the commands in the rest of this chapter and
    … …  
    282281<screen><userinput>exec /tools/bin/bash --login +h</userinput></screen>
    283282
    284 <para>Note the use of the <userinput>+h</userinput> directive. This tells
    285 <userinput>bash</userinput> not to use its internal path hashing. Without this
    286 directive, <userinput>bash</userinput> would remember the paths to binaries it
     283<para>Note the use of the <emphasis>+h</emphasis> directive. This tells
     284<command>bash</command> not to use its internal path hashing. Without this
     285directive, <command>bash</command> would remember the paths to binaries it
    287286has executed. Since we want to use our newly compiled binaries as soon as
    288287they are installed, we turn off this function for the duration of this
    289288chapter.</para>
    290289
    291 <para>The <userinput>login</userinput>, <userinput>agetty</userinput> and
    292 <userinput>init</userinput> programs (and some others) use a number of log
     290<para>The <command>login</command>, <command>agetty</command> and
     291<command>init</command> programs (and some others) use a number of log
    293292files to record information such as who was logged into the system and when.
    294293These programs, however, won't write to the log files if they don't already
    … …  
    342341against the libraries in <filename>/usr/lib</filename> and
    343342<filename>/lib</filename>. The extra
    344 <userinput>INSTALL=/tools/bin/install</userinput> is needed because the Makefile
     343<emphasis>INSTALL=/tools/bin/install</emphasis> is needed because the Makefile
    345344created during the second pass still contains the reference to
    346345<filename>/usr/bin/install</filename>, which we obviously haven't installed yet.
Note: See TracChangeset for help on using the changeset viewer.