gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-06-18 19:29:21 +01:00
Code Issues Packages Projects Releases Wiki Activity

Add -v to commands that accept it

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@6913 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Matthew Burgess 2005-09-29 20:55:40 +00:00
parent 8c68addc8e
commit 59988921eb
46 changed files with 162 additions and 159 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
chapter01/changelog.xml
View File

@ -122,6 +122,9 @@ First a summary, then a detailed log.</para>
</itemizedlist>
</listitem>
<listitem><para>September 29, 2005 [matt]: Add <option>-v</option> to commands
that accept it (fixes bug 1612).</para></listitem>
<listitem><para>September 26, 2005 [matt]: Upgrade to man-pages-2.08.</para>
</listitem>

12
chapter02/creatingfilesystem.xml
View File

@ -17,7 +17,7 @@ url="&blfs-root;view/svn/postlfs/filesystems.html"/>.</para>
<para>To create an ext2 file system on the LFS partition, run the following:</para>
<screen role="nodump"><userinput>mke2fs /dev/<replaceable>[xxx]</replaceable></userinput></screen>
<screen role="nodump"><userinput>mke2fs -v /dev/<replaceable>[xxx]</replaceable></userinput></screen>
<para>Replace <replaceable>[xxx]</replaceable> with the name of the LFS
partition (<filename class="devicefile">hda5</filename> in our previous example).</para>
@ -38,22 +38,22 @@ stock e2fsprogs package and use the resulting binaries to re-create the
filesystem on your LFS partition:</para>
<screen role="nodump"><userinput>cd /tmp
tar xjf /path/to/sources/e2fsprogs-&e2fsprogs-version;.tar.bz2
tar -xjvf /path/to/sources/e2fsprogs-&e2fsprogs-version;.tar.bz2
cd e2fsprogs-&e2fsprogs-version;
mkdir build
mkdir -v build
cd build
../configure
make #note that we intentionally don't 'make install' here!
./misc/mke2fs /dev/<replaceable>[xxx]</replaceable>
./misc/mke2fs -v /dev/<replaceable>[xxx]</replaceable>
cd /tmp
rm -rf e2fsprogs-&e2fsprogs-version;</userinput></screen>
rm -rfv e2fsprogs-&e2fsprogs-version;</userinput></screen>
</note>
<para>If a swap partition was created, it will need to be initialized for use by
issuing the command below. If you are using an existing swap partition, there is
no need to format it.</para>
<screen role="nodump"><userinput>mkswap /dev/<replaceable>[yyy]</replaceable></userinput></screen>
<screen role="nodump"><userinput>mkswap -v /dev/<replaceable>[yyy]</replaceable></userinput></screen>
<para>Replace <replaceable>[yyy]</replaceable> with the name of the swap
partition.</para>

12
chapter02/mounting.xml
View File

@ -22,8 +22,8 @@ environment variable by running:</para>
<para>Next, create the mount point and mount the LFS file system by
running:</para>
<screen role="nodump"><userinput>mkdir -p $LFS
mount /dev/<replaceable>[xxx]</replaceable> $LFS</userinput></screen>
<screen role="nodump"><userinput>mkdir -pv $LFS
mount -v /dev/<replaceable>[xxx]</replaceable> $LFS</userinput></screen>
<para>Replace <replaceable>[xxx]</replaceable> with the designation of the LFS
partition.</para>
@ -32,10 +32,10 @@ partition.</para>
class="directory">/</filename> and another for <filename
class="directory">/usr</filename>), mount them using:</para>
<screen role="nodump"><userinput>mkdir -p $LFS
mount /dev/<replaceable>[xxx]</replaceable> $LFS
mkdir $LFS/usr
mount /dev/<replaceable>[yyy]</replaceable> $LFS/usr</userinput></screen>
<screen role="nodump"><userinput>mkdir -pv $LFS
mount -v /dev/<replaceable>[xxx]</replaceable> $LFS
mkdir -v $LFS/usr
mount -v /dev/<replaceable>[yyy]</replaceable> $LFS/usr</userinput></screen>
<para>Replace <replaceable>[xxx]</replaceable> and
<replaceable>[yyy]</replaceable> with the appropriate partition

4
chapter03/introduction.xml
View File

@ -35,7 +35,7 @@ of the building process.</para>
<emphasis>root</emphasis>, the following command before starting the
download session:</para>
<screen role="nodump"><userinput>mkdir $LFS/sources</userinput></screen>
<screen role="nodump"><userinput>mkdir -v $LFS/sources</userinput></screen>
<para>Make this directory writable and sticky. <quote>Sticky</quote>
means that even if multiple users have write permission on a
@ -43,7 +43,7 @@ directory, only the owner of a file can delete the file within a
sticky directory. The following command will enable the write and
sticky modes:</para>
<screen role="nodump"><userinput>chmod a+wt $LFS/sources</userinput></screen>
<screen role="nodump"><userinput>chmod -v a+wt $LFS/sources</userinput></screen>
</sect1>

4
chapter04/addinguser.xml
View File

@ -68,12 +68,12 @@ password), give <emphasis>lfs</emphasis> a password:</para>
<filename class="directory">$LFS/tools</filename> by making
<emphasis>lfs</emphasis> the directory owner:</para>
<screen><userinput>chown lfs $LFS/tools</userinput></screen>
<screen><userinput>chown -v lfs $LFS/tools</userinput></screen>
<para>If a separate working directory was created as suggested, give
user <emphasis>lfs</emphasis> ownership of this directory:</para>
<screen><userinput>chown lfs $LFS/sources</userinput></screen>
<screen><userinput>chown -v lfs $LFS/sources</userinput></screen>
<para>Next, login as user <emphasis>lfs</emphasis>. This can be done
via a virtual console, through a display manager, or with the

4
chapter04/creatingtoolsdir.xml
View File

@ -21,14 +21,14 @@ linkend="chapter-temporary-tools"/>).</para>
<para>Create the required directory by running the following as
<emphasis>root</emphasis>:</para>
<screen><userinput>mkdir $LFS/tools</userinput></screen>
<screen><userinput>mkdir -v $LFS/tools</userinput></screen>
<para>The next step is to create a <filename class="symlink">/tools</filename>
symlink on the host system. This will point to the newly-created directory on
the LFS partition. Run this command as <emphasis>root</emphasis> as
well:</para>
<screen><userinput>ln -s $LFS/tools /</userinput></screen>
<screen><userinput>ln -sv $LFS/tools /</userinput></screen>
<note><para>The above command is correct. The <command>ln</command> command has
a few syntactic variations, so be sure to check <command>info coreutils ln</command> and

6
chapter05/adjusting.xml
View File

@ -41,7 +41,7 @@ dynamic linker that GCC will use:</para>
<screen><userinput>SPECFILE=`dirname $(gcc -print-libgcc-file-name)`/specs &amp;&amp;
gcc -dumpspecs > $SPECFILE &amp;&amp;
sed 's@^/lib/ld-linux.so.2@/tools&amp;@g' $SPECFILE &gt; tempspecfile &amp;&amp;
mv -f tempspecfile $SPECFILE &amp;&amp;
mv -vf tempspecfile $SPECFILE &amp;&amp;
unset SPECFILE</userinput></screen>
<para>It is recommended that the above
@ -69,7 +69,7 @@ This is explained in more detail later in this chapter. Run the following comman
<!-- && used to ease copy and pasting -->
<screen><userinput>GCC_INCLUDEDIR=`dirname $(gcc -print-libgcc-file-name)`/include &amp;&amp;
find ${GCC_INCLUDEDIR}/* -maxdepth 0 -xtype d -exec rm -rf '{}' \; &amp;&amp;
rm -f `grep -l "DO NOT EDIT THIS FILE" ${GCC_INCLUDEDIR}/*` &amp;&amp;
rm -vf `grep -l "DO NOT EDIT THIS FILE" ${GCC_INCLUDEDIR}/*` &amp;&amp;
unset GCC_INCLUDEDIR</userinput></screen>
<caution><para>At this point, it is imperative to stop and ensure that
@ -109,7 +109,7 @@ commands.</para>
<para>Once all is well, clean up the test files:</para>
<screen><userinput>rm dummy.c a.out</userinput></screen>
<screen><userinput>rm -v dummy.c a.out</userinput></screen>
</caution>
</sect1>

2
chapter05/bash.xml
View File

@ -64,7 +64,7 @@ from Glibc which are more stable.</para></listitem>
<para>Make a link for the programs that use <command>sh</command> for
a shell:</para>
<screen><userinput>ln -s bash /tools/bin/sh</userinput></screen>
<screen><userinput>ln -vs bash /tools/bin/sh</userinput></screen>
</sect2>

2
chapter05/binutils-pass1.xml
View File

@ -44,7 +44,7 @@ unset them when building Binutils.</para>
<para>The Binutils documentation recommends building Binutils outside of the
source directory in a dedicated build directory:</para>
<screen><userinput>mkdir ../binutils-build
<screen><userinput>mkdir -v ../binutils-build
cd ../binutils-build</userinput></screen>
<note><para>In order for the SBU values listed in the rest of the book

4
chapter05/gcc-pass1.xml
View File

@ -39,7 +39,7 @@ unset them when building GCC.</para>
<para>The GCC documentation recommends building GCC outside of the
source directory in a dedicated build directory:</para>
<screen><userinput>mkdir ../gcc-build
<screen><userinput>mkdir -v ../gcc-build
cd ../gcc-build</userinput></screen>
<para>Prepare GCC for compilation:</para>
@ -111,7 +111,7 @@ and therefore usable on all kinds of UNIX systems where the GNU C compiler
is not always installed. Running <command>cc</command> leaves the system administrator
free to decide which C compiler to install.</para>
<screen><userinput>ln -s gcc /tools/bin/cc</userinput></screen>
<screen><userinput>ln -vs gcc /tools/bin/cc</userinput></screen>
</sect2>

6
chapter05/gcc-pass2.xml
View File

@ -73,7 +73,7 @@ script searches for headers, so that it fixes only the new headers under
<filename class="directory">/tools</filename>, not the ones from your host
system.</para>
<screen><userinput>cp gcc/Makefile.in{,.orig} &amp;&amp;
<screen><userinput>cp -v gcc/Makefile.in{,.orig} &amp;&amp;
sed 's@\(^NATIVE_SYSTEM_HEADER_DIR =\).*@\1 /tools/include@g' \
gcc/Makefile.in.orig &gt; gcc/Makefile.in</userinput></screen>
@ -83,7 +83,7 @@ Non-bootstrap builds omit this flag by default, so apply the following
<command>sed</command> to use it in order to ensure consistent compiler builds.
</para>
<screen><userinput>cp gcc/Makefile.in{,.tmp} &amp;&amp;
<screen><userinput>cp -v gcc/Makefile.in{,.tmp} &amp;&amp;
sed 's/^XCFLAGS =$/&amp; -fomit-frame-pointer/' gcc/Makefile.in.tmp \
&gt; gcc/Makefile.in</userinput></screen>
@ -105,7 +105,7 @@ it.</para></important>
<para>Create a separate build directory again:</para>
<screen><userinput>mkdir ../gcc-build
<screen><userinput>mkdir -v ../gcc-build
cd ../gcc-build</userinput></screen>
<para>Before starting to build GCC, remember to unset any environment

4
chapter05/glibc.xml
View File

@ -169,7 +169,7 @@ output so that the log file can be examined for failures later.</para>
end about the absence of <filename>/tools/etc/ld.so.conf</filename>.
Prevent this warning with:</para>
<screen><userinput>mkdir /tools/etc
<screen><userinput>mkdir -v /tools/etc
touch /tools/etc/ld.so.conf</userinput></screen>
<para>Install the package:</para>
@ -205,7 +205,7 @@ instructions, instead of the <parameter>install-locales</parameter>
target used above, will install the minimum set of locales necessary
for the tests to run successfully:</para>
<screen><userinput>mkdir -p /tools/lib/locale
<screen><userinput>mkdir -pv /tools/lib/locale
localedef -i de_DE -f ISO-8859-1 de_DE
localedef -i de_DE@euro -f ISO-8859-15 de_DE@euro
localedef -i en_HK -f ISO-8859-1 en_HK

6
chapter05/perl.xml
View File

@ -63,9 +63,9 @@ be run in the next chapter if desired.</para>
<para>Install these tools and their libraries:</para>
<screen><userinput>cp perl pod/pod2man /tools/bin
mkdir -p /tools/lib/perl5/&perl-version;
cp -R lib/* /tools/lib/perl5/&perl-version;</userinput></screen>
<screen><userinput>cp -v perl pod/pod2man /tools/bin
mkdir -pv /tools/lib/perl5/&perl-version;
cp -Rv lib/* /tools/lib/perl5/&perl-version;</userinput></screen>
</sect2>

2
chapter05/tcl.xml
View File

@ -76,7 +76,7 @@ export TCLPATH=`pwd`</userinput></screen>
<para>Now make a necessary symbolic link:</para>
<screen><userinput>ln -s tclsh8.4 /tools/bin/tclsh</userinput></screen>
<screen><userinput>ln -sv tclsh8.4 /tools/bin/tclsh</userinput></screen>
</sect2>

2
chapter06/bash.xml
View File

@ -33,7 +33,7 @@ GCC, Glibc, Grep, Make, Ncurses, and Sed.</seg></seglistitem>
<para>If you downloaded the Bash documentation tarball and wish to install HTML
documentation, issue the following commands:</para>
<screen><userinput>tar -xf ../bash-doc-&bash-doc-version;.tar.gz &amp;&amp;
<screen><userinput>tar -xvf ../bash-doc-&bash-doc-version;.tar.gz &amp;&amp;
sed -i "s|htmldir = @htmldir@|htmldir = /usr/share/doc/bash-&bash-version;|" \
Makefile.in</userinput></screen>

4
chapter06/binutils.xml
View File

@ -56,7 +56,7 @@ for Binutils and GCC.</para>
<para>The Binutils documentation recommends building Binutils outside of the
source directory in a dedicated build directory:</para>
<screen><userinput>mkdir ../binutils-build
<screen><userinput>mkdir -v ../binutils-build
cd ../binutils-build</userinput></screen>
<para>Prepare Binutils for compilation:</para>
@ -94,7 +94,7 @@ circumstances.</para></important>
<para>Install the <filename class="headerfile">libiberty</filename> header file that is needed by
some packages:</para>
<screen><userinput>cp ../binutils-&binutils-version;/include/libiberty.h /usr/include</userinput></screen>
<screen><userinput>cp -v ../binutils-&binutils-version;/include/libiberty.h /usr/include</userinput></screen>
</sect2>

14
chapter06/bzip2.xml
View File

@ -62,7 +62,7 @@ utilities against it.</para>
<userinput>make test</userinput>.</para>
<para>If reinstalling Bzip2, perform
<userinput>rm -f /usr/bin/bz*</userinput> first, otherwise the following
<userinput>rm -vf /usr/bin/bz*</userinput> first, otherwise the following
<command>make install</command> will fail.</para>
<para>Install the programs:</para>
@ -73,12 +73,12 @@ utilities against it.</para>
<filename class="directory">/bin</filename> directory, make
some necessary symbolic links, and clean up:</para>
<screen><userinput>cp bzip2-shared /bin/bzip2
cp -a libbz2.so* /lib
ln -s ../../lib/libbz2.so.1.0 /usr/lib/libbz2.so
rm /usr/bin/{bunzip2,bzcat,bzip2}
ln -s bzip2 /bin/bunzip2
ln -s bzip2 /bin/bzcat</userinput></screen>
<screen><userinput>cp -v bzip2-shared /bin/bzip2
cp -av libbz2.so* /lib
ln -sv ../../lib/libbz2.so.1.0 /usr/lib/libbz2.so
rm -v /usr/bin/{bunzip2,bzcat,bzip2}
ln -sv bzip2 /bin/bunzip2
ln -sv bzip2 /bin/bzcat</userinput></screen>
</sect2>

10
chapter06/coreutils.xml
View File

@ -89,17 +89,17 @@ groups:</para>
<para>Move programs to the locations specified by the FHS:</para>
<screen><userinput>mv /usr/bin/{cat,chgrp,chmod,chown,cp,date,dd,df,echo} /bin
mv /usr/bin/{false,hostname,ln,ls,mkdir,mknod,mv,pwd,rm} /bin
mv /usr/bin/{rmdir,stty,sync,true,uname} /bin
mv /usr/bin/chroot /usr/sbin</userinput></screen>
<screen><userinput>mv -v /usr/bin/{cat,chgrp,chmod,chown,cp,date,dd,df,echo} /bin
mv -v /usr/bin/{false,hostname,ln,ls,mkdir,mknod,mv,pwd,rm} /bin
mv -v /usr/bin/{rmdir,stty,sync,true,uname} /bin
mv -v /usr/bin/chroot /usr/sbin</userinput></screen>
<para>Some of the scripts in the LFS-Bootscripts package depend on
<command>head</command> and <command>sleep</command>. As
<filename class="directory">/usr</filename> may not be available during the
early stages of booting, those binaries need to be on the root partition:</para>
<screen><userinput>mv /usr/bin/{head,sleep} /bin</userinput></screen>
<screen><userinput>mv -v /usr/bin/{head,sleep} /bin</userinput></screen>
</sect2>

8
chapter06/createfiles.xml
View File

@ -12,10 +12,10 @@ order to satisfy these programs, create a number of symbolic links which will be
replaced by real files throughout the course of this chapter after the software
has been installed.</para>
<screen><userinput>ln -s /tools/bin/{bash,cat,pwd,stty} /bin
ln -s /tools/bin/perl /usr/bin
ln -s /tools/lib/libgcc_s.so{,.1} /usr/lib
ln -s bash /bin/sh</userinput></screen>
<screen><userinput>ln -sv /tools/bin/{bash,cat,pwd,stty} /bin
ln -sv /tools/bin/perl /usr/bin
ln -sv /tools/lib/libgcc_s.so{,.1} /usr/lib
ln -sv bash /bin/sh</userinput></screen>
</sect1>

38
chapter06/creatingdirs.xml
View File

@ -10,25 +10,25 @@
<para>It is time to create some structure in the LFS file system. Create a
standard directory tree by issuing the following commands:</para>
<screen><userinput>install -d /{bin,boot,dev,etc/opt,home,lib,mnt}
install -d /{sbin,srv,usr/local,var,opt}
install -d /root -m 0750
install -d /tmp /var/tmp -m 1777
install -d /media/{floppy,cdrom}
install -d /usr/{bin,include,lib,sbin,share,src}
ln -s share/{man,doc,info} /usr
install -d /usr/share/{doc,info,locale,man}
install -d /usr/share/{misc,terminfo,zoneinfo}
install -d /usr/share/man/man{1..8}
install -d /usr/local/{bin,etc,include,lib,sbin,share,src}
ln -s share/{man,doc,info} /usr/local
install -d /usr/local/share/{doc,info,locale,man}
install -d /usr/local/share/{misc,terminfo,zoneinfo}
install -d /usr/local/share/man/man{1,2,3,4,5,6,7,8}
install -d /var/{lock,log,mail,run,spool}
install -d /var/{opt,cache,lib/{misc,locate},local}
install -d /opt/{bin,doc,include,info}
install -d /opt/{lib,man/man{1,2,3,4,5,6,7,8}}</userinput></screen>
<screen><userinput>install -dv /{bin,boot,dev,etc/opt,home,lib,mnt}
install -dv /{sbin,srv,usr/local,var,opt}
install -dv /root -m 0750
install -dv /tmp /var/tmp -m 1777
install -dv /media/{floppy,cdrom}
install -dv /usr/{bin,include,lib,sbin,share,src}
ln -sv share/{man,doc,info} /usr
install -dv /usr/share/{doc,info,locale,man}
install -dv /usr/share/{misc,terminfo,zoneinfo}
install -dv /usr/share/man/man{1..8}
install -dv /usr/local/{bin,etc,include,lib,sbin,share,src}
ln -sv share/{man,doc,info} /usr/local
install -dv /usr/local/share/{doc,info,locale,man}
install -dv /usr/local/share/{misc,terminfo,zoneinfo}
install -dv /usr/local/share/man/man{1,2,3,4,5,6,7,8}
install -dv /var/{lock,log,mail,run,spool}
install -dv /var/{opt,cache,lib/{misc,locate},local}
install -dv /opt/{bin,doc,include,info}
install -dv /opt/{lib,man/man{1,2,3,4,5,6,7,8}}</userinput></screen>
<para>Directories are, by default, created with permission mode 755,
but this is not desirable for all directories. In the commands above,

22
chapter06/devices.xml
View File

@ -37,7 +37,7 @@ accessed. This is generally done during the boot process. Since this new system
has not been booted, it is necessary to do what the LFS-Bootscripts package would
otherwise do by mounting <filename class="directory">/dev</filename>:</para>
<screen><userinput>mount -n -t tmpfs none /dev</userinput></screen>
<screen><userinput>mount -nvt tmpfs none /dev</userinput></screen>
<para>The Udev package is what actually creates the devices in the <filename
class="directory">/dev</filename> directory. Since it will not be installed
@ -51,26 +51,26 @@ mknod -m 666 /dev/ptmx c 5 2
mknod -m 666 /dev/tty c 5 0
mknod -m 444 /dev/random c 1 8
mknod -m 444 /dev/urandom c 1 9
chown root:tty /dev/{console,ptmx,tty}</userinput></screen>
chown -v root:tty /dev/{console,ptmx,tty}</userinput></screen>
<para>There are some symlinks and directories required by LFS that are created
during system startup by the LFS-Bootscripts package. Since this is a chroot
environment and not a booted environment, those symlinks and directories need to
be created here:</para>
<screen><userinput>ln -s /proc/self/fd /dev/fd
ln -s /proc/self/fd/0 /dev/stdin
ln -s /proc/self/fd/1 /dev/stdout
ln -s /proc/self/fd/2 /dev/stderr
ln -s /proc/kcore /dev/core
mkdir /dev/pts
mkdir /dev/shm</userinput></screen>
<screen><userinput>ln -sv /proc/self/fd /dev/fd
ln -sv /proc/self/fd/0 /dev/stdin
ln -sv /proc/self/fd/1 /dev/stdout
ln -sv /proc/self/fd/2 /dev/stderr
ln -sv /proc/kcore /dev/core
mkdir -v /dev/pts
mkdir -v /dev/shm</userinput></screen>
<para>Finally, mount the proper virtual (kernel) file systems on the
newly-created directories:</para>
<screen><userinput>mount -t devpts -o gid=4,mode=620 none /dev/pts
mount -t tmpfs none /dev/shm</userinput></screen>
<screen><userinput>mount -vt devpts -o gid=4,mode=620 none /dev/pts
mount -vt tmpfs none /dev/shm</userinput></screen>
<para>The <command>mount</command> commands executed above may result
in the following warning message:</para>

2
chapter06/e2fsprogs.xml
View File

@ -35,7 +35,7 @@ Diffutils, Gawk, GCC, Gettext, Glibc, Grep, Make, Sed, and Texinfo</seg></seglis
<para>It is recommended that E2fsprogs be built in a subdirectory of the source tree:
</para>
<screen><userinput>mkdir build
<screen><userinput>mkdir -v build
cd build</userinput></screen>
<para>Prepare E2fsprogs for compilation:</para>

4
chapter06/flex.xml
View File

@ -62,7 +62,7 @@ default page is fine, so make sure it does not get regenerated:</para>
class="directory">/usr/lib</filename>. Create a symlink to account for
this:</para>
<screen><userinput>ln -s libfl.a /usr/lib/libl.a</userinput></screen>
<screen><userinput>ln -sv libfl.a /usr/lib/libl.a</userinput></screen>
<para>A few programs do not know about <command>flex</command> yet and
try to run its predecessor, <command>lex</command>. To support those
@ -77,7 +77,7 @@ exec /usr/bin/flex -l "$@"
# End /usr/bin/lex</literal>
EOF
chmod 755 /usr/bin/lex</userinput></screen>
chmod -v 755 /usr/bin/lex</userinput></screen>
</sect2>

6
chapter06/gcc.xml
View File

@ -56,7 +56,7 @@ Non-bootstrap builds omit this flag by default, so apply the following
<para>The GCC documentation recommends building GCC outside of the source
directory in a dedicated build directory:</para>
<screen><userinput>mkdir ../gcc-build
<screen><userinput>mkdir -v ../gcc-build
cd ../gcc-build</userinput></screen>
<para>Prepare GCC for compilation:</para>
@ -90,12 +90,12 @@ refer back to them as necessary.</para>
<filename class="directory">/lib</filename> directory.
To support those packages, create this symlink:</para>
<screen><userinput>ln -s ../usr/bin/cpp /lib</userinput></screen>
<screen><userinput>ln -sv ../usr/bin/cpp /lib</userinput></screen>
<para>Many packages use the name <command>cc</command> to call the C
compiler. To satisfy those packages, create a symlink:</para>
<screen><userinput>ln -s gcc /usr/bin/cc</userinput></screen>
<screen><userinput>ln -sv gcc /usr/bin/cc</userinput></screen>
<note><para>At this point, it is strongly recommended to repeat the
sanity check performed earlier in this chapter. Refer back to <xref

8
chapter06/glibc.xml
View File

@ -60,7 +60,7 @@ of achieving a clean build.</para>
threading libraries installed by Glibc. Unpack the tarball from
within the Glibc source directory:</para>
<screen><userinput>tar -xf ../glibc-linuxthreads-&glibc-version;.tar.bz2</userinput></screen>
<screen><userinput>tar -xvf ../glibc-linuxthreads-&glibc-version;.tar.bz2</userinput></screen>
<para>Glibc has two tests which fail when the running kernel is 2.6.11 or later.
The problem has been determined to be with the tests themselves, not with the
@ -84,7 +84,7 @@ tests on x86 processors when compiled with GCC-&gcc-version;:</para>
<para>The Glibc documentation recommends building Glibc outside of the source
directory in a dedicated build directory:</para>
<screen><userinput>mkdir ../glibc-build
<screen><userinput>mkdir -v ../glibc-build
cd ../glibc-build</userinput></screen>
<para>Prepare Glibc for compilation:</para>
@ -177,7 +177,7 @@ instructions, instead of the <parameter>install-locales</parameter>
target used above, will install the minimum set of locales necessary
for the tests to run successfully:</para>
<screen><userinput>mkdir -p /usr/lib/locale
<screen><userinput>mkdir -pv /usr/lib/locale
localedef -i de_DE -f ISO-8859-1 de_DE
localedef -i de_DE@euro -f ISO-8859-15 de_DE@euro
localedef -i en_HK -f ISO-8859-1 en_HK
@ -256,7 +256,7 @@ will output the name of the time zone (e.g.,
Then create the <filename>/etc/localtime</filename> file by
running:</para>
<screen><userinput>cp --remove-destination /usr/share/zoneinfo/<replaceable>[xxx]</replaceable> \
<screen><userinput>cp -v --remove-destination /usr/share/zoneinfo/<replaceable>[xxx]</replaceable> \
/etc/localtime</userinput></screen>
<para>Replace <replaceable>[xxx]</replaceable> with the name of the time zone

6
chapter06/groff.xml
View File

@ -50,9 +50,9 @@ to contain the default paper size. For users in the United States,
<para>Some documentation programs, such as <command>xman</command>,
will not work properly without the following symlinks:</para>
<screen><userinput>ln -s soelim /usr/bin/zsoelim
ln -s eqn /usr/bin/geqn
ln -s tbl /usr/bin/gtbl</userinput></screen>
<screen><userinput>ln -sv soelim /usr/bin/zsoelim
ln -sv eqn /usr/bin/geqn
ln -sv tbl /usr/bin/gtbl</userinput></screen>
</sect2>

4
chapter06/grub.xml
View File

@ -51,8 +51,8 @@ unset them when building GRUB.</para>
<para>Install the package:</para>
<screen><userinput>make install
mkdir /boot/grub
cp /usr/lib/grub/i386-pc/stage{1,2} /boot/grub</userinput></screen>
mkdir -v /boot/grub
cp -v /usr/lib/grub/i386-pc/stage{1,2} /boot/grub</userinput></screen>
<para>Replace <filename class="directory">i386-pc</filename> with whatever
directory is appropriate for the hardware in use.</para>

12
chapter06/gzip.xml
View File

@ -59,12 +59,12 @@ that the new location gets placed into the script:</para>
class="directory">/bin</filename> directory and create some commonly used
symlinks to it:</para>
<screen><userinput>mv /usr/bin/gzip /bin
rm /usr/bin/{gunzip,zcat}
ln -s gzip /bin/gunzip
ln -s gzip /bin/zcat
ln -s gzip /bin/compress
ln -s gunzip /bin/uncompress</userinput></screen>
<screen><userinput>mv -v /usr/bin/gzip /bin
rm -v /usr/bin/{gunzip,zcat}
ln -sv gzip /bin/gunzip
ln -sv gzip /bin/zcat
ln -sv gzip /bin/compress
ln -sv gunzip /bin/uncompress</userinput></screen>
</sect2>

8
chapter06/hotplug.xml
View File

@ -40,22 +40,22 @@ running kernel.</para>
<para>Copy a file that the <quote>install</quote> target omits.</para>
<screen><userinput>cp etc/hotplug/pnp.distmap /etc/hotplug</userinput></screen>
<screen><userinput>cp -v etc/hotplug/pnp.distmap /etc/hotplug</userinput></screen>
<para>Remove the init script that Hotplug installs since we are going to be
using the script included in the LFS-Bootscripts package:</para>
<screen><userinput>rm -rf /etc/init.d</userinput></screen>
<screen><userinput>rm -rfv /etc/init.d</userinput></screen>
<para>Network device hotplugging is not yet supported by the LFS-Bootscripts
package. For that reason, remove the network hotplug agent:</para>
<screen><userinput>rm -f /etc/hotplug/net.agent</userinput></screen>
<screen><userinput>rm -fv /etc/hotplug/net.agent</userinput></screen>
<para>Create a directory for storing firmware that can be loaded by
<command>hotplug</command>:</para>
<screen><userinput>mkdir /lib/firmware</userinput></screen>
<screen><userinput>mkdir -v /lib/firmware</userinput></screen>
</sect2>

2
chapter06/inetutils.xml
View File

@ -97,7 +97,7 @@ servers.</para></listitem>
<para>Move the <command>ping</command> program to its FHS-compliant
place:</para>
<screen><userinput>mv /usr/bin/ping /bin</userinput></screen>
<screen><userinput>mv -v /usr/bin/ping /bin</userinput></screen>
</sect2>

12
chapter06/kernfs.xml
View File

@ -13,12 +13,12 @@ used for them. The content of the file systems resides in memory.</para>
<para>Begin by creating directories onto which the file systems will be mounted:</para>
<screen><userinput>mkdir -p $LFS/{proc,sys}</userinput></screen>
<screen><userinput>mkdir -pv $LFS/{proc,sys}</userinput></screen>
<para>Now mount the file systems:</para>
<screen><userinput>mount -t proc proc $LFS/proc
mount -t sysfs sysfs $LFS/sys</userinput></screen>
<screen><userinput>mount -vt proc proc $LFS/proc
mount -vt sysfs sysfs $LFS/sys</userinput></screen>
<para>Remember that if for any reason you stop working on the LFS
system and start again later, it is important to check that these file
@ -29,9 +29,9 @@ environment.</para>
chroot environment. To keep the host up to date, perform a <quote>fake
mount</quote> for each of these now:</para>
<screen><userinput>mount -f -t tmpfs tmpfs $LFS/dev
mount -f -t tmpfs tmpfs $LFS/dev/shm
mount -f -t devpts -o gid=4,mode=620 devpts $LFS/dev/pts</userinput></screen>
<screen><userinput>mount -vft tmpfs tmpfs $LFS/dev
mount -vft tmpfs tmpfs $LFS/dev/shm
mount -vft devpts -o gid=4,mode=620 devpts $LFS/dev/pts</userinput></screen>
</sect1>

10
chapter06/ncurses.xml
View File

@ -47,22 +47,22 @@ Gawk, GCC, Glibc, Grep, Make, and Sed</seg></seglistitem>
<para>Give the Ncurses libraries execute permissions:</para>
<screen><userinput>chmod 755 /usr/lib/*.&ncurses-version;</userinput></screen>
<screen><userinput>chmod -v 755 /usr/lib/*.&ncurses-version;</userinput></screen>
<para>Fix a library that should not be executable:</para>
<screen><userinput>chmod 644 /usr/lib/libncurses++.a</userinput></screen>
<screen><userinput>chmod -v 644 /usr/lib/libncurses++.a</userinput></screen>
<para>Move the libraries to the <filename class="directory">/lib</filename> directory,
where they are expected to reside:</para>
<screen><userinput>mv /usr/lib/libncurses.so.5* /lib</userinput></screen>
<screen><userinput>mv -v /usr/lib/libncurses.so.5* /lib</userinput></screen>
<para>Because the libraries have been moved, a few symlinks point to
non-existent files. Recreate those symlinks:</para>
<screen><userinput>ln -sf ../../lib/libncurses.so.5 /usr/lib/libncurses.so
ln -sf libncurses.so /usr/lib/libcurses.so</userinput></screen>
<screen><userinput>ln -sfv ../../lib/libncurses.so.5 /usr/lib/libncurses.so
ln -sfv libncurses.so /usr/lib/libcurses.so</userinput></screen>
</sect2>

4
chapter06/psmisc.xml
View File

@ -61,7 +61,7 @@ package.</para></listitem>
class="directory">/bin</filename>. Therefore, move them to <filename
class="directory">/usr/bin</filename>:</para>
<screen><userinput>mv /bin/pstree* /usr/bin</userinput></screen>
<screen><userinput>mv -v /bin/pstree* /usr/bin</userinput></screen>
<para>By default, Psmisc's <command>pidof</command> program is not
installed. This usually is not a problem because it is installed later
@ -70,7 +70,7 @@ in the Sysvinit package, which provides a better
particular system, complete the installation of Psmisc by creating the
following symlink:</para>
<screen><userinput>ln -s killall /bin/pidof</userinput></screen>
<screen><userinput>ln -sv killall /bin/pidof</userinput></screen>
</sect2>

4
chapter06/pwdgroup.xml
View File

@ -84,8 +84,8 @@ do not already exist. Initialize the log files and give them
proper permissions:</para>
<screen><userinput>touch /var/run/utmp /var/log/{btmp,lastlog,wtmp}
chgrp utmp /var/run/utmp /var/log/lastlog
chmod 664 /var/run/utmp /var/log/lastlog</userinput></screen>
chgrp -v utmp /var/run/utmp /var/log/lastlog
chmod -v 664 /var/run/utmp /var/log/lastlog</userinput></screen>
<para>The <filename>/var/run/utmp</filename> file records the users
that are currently logged in. The <filename>/var/log/wtmp</filename>

2
chapter06/readjusting.xml
View File

@ -97,7 +97,7 @@ the process.</para>
<para>Once everything is working correctly, clean up the test
files:</para>
<screen><userinput>rm dummy.c a.out</userinput></screen></caution>
<screen><userinput>rm -v dummy.c a.out</userinput></screen></caution>
</sect1>

10
chapter06/readline.xml
View File

@ -61,19 +61,19 @@ includes other fixes recommended by the Readline author.</para>
<para>Give Readline's dynamic libraries more appropriate permissions:</para>
<screen><userinput>chmod 755 /lib/lib{readline,history}.so*</userinput></screen>
<screen><userinput>chmod -v 755 /lib/lib{readline,history}.so*</userinput></screen>
<para>Now move the static libraries to a more appropriate location:</para>
<screen><userinput>mv /lib/lib{readline,history}.a /usr/lib</userinput></screen>
<screen><userinput>mv -v /lib/lib{readline,history}.a /usr/lib</userinput></screen>
<para>Next, remove the <filename class="extension">.so</filename> files in
<filename class="directory">/lib</filename> and relink them into <filename
class="directory">/usr/lib</filename>.</para>
<screen><userinput>rm /lib/lib{readline,history}.so
ln -sf ../../lib/libreadline.so.5 /usr/lib/libreadline.so
ln -sf ../../lib/libhistory.so.5 /usr/lib/libhistory.so</userinput></screen>
<screen><userinput>rm -v /lib/lib{readline,history}.so
ln -sfv ../../lib/libreadline.so.5 /usr/lib/libreadline.so
ln -sfv ../../lib/libhistory.so.5 /usr/lib/libhistory.so</userinput></screen>
</sect2>

12
chapter06/shadow.xml
View File

@ -60,7 +60,7 @@ files:</para>
<indexterm zone="shadow-limits-login_access"><primary sortas="e-/etc/limits">/etc/limits</primary></indexterm>
<indexterm zone="shadow-limits-login_access"><primary sortas="e-/etc/login.access">/etc/login.access</primary></indexterm>
<screen><userinput>cp etc/{limits,login.access} /etc</userinput></screen>
<screen><userinput>cp -v etc/{limits,login.access} /etc</userinput></screen>
<para id="shadow-login_defs">Instead of using the default <emphasis>crypt</emphasis> method,
use the more secure <emphasis>MD5</emphasis> method of password
@ -86,20 +86,20 @@ the <command>sed</command> given below:</para>
<para>Move a misplaced program to its proper location:</para>
<screen><userinput>mv /usr/bin/passwd /bin</userinput></screen>
<screen><userinput>mv -v /usr/bin/passwd /bin</userinput></screen>
<para>Move Shadow's libraries to more appropriate locations:</para>
<screen><userinput>mv /lib/libshadow.*a /usr/lib
rm /lib/libshadow.so
ln -sf ../../lib/libshadow.so.0 /usr/lib/libshadow.so</userinput></screen>
<screen><userinput>mv -v /lib/libshadow.*a /usr/lib
rm -v /lib/libshadow.so
ln -sfv ../../lib/libshadow.so.0 /usr/lib/libshadow.so</userinput></screen>
<para>The <parameter>-D</parameter> option of the
<command>useradd</command> program requires the <filename
class="directory">/etc/default</filename> directory for it to work
properly:</para>
<screen><userinput>mkdir /etc/default</userinput></screen>
<screen><userinput>mkdir -v /etc/default</userinput></screen>
</sect2>

4
chapter06/udev.xml
View File

@ -44,11 +44,11 @@
<para>Udev's configuration is far from ideal by default, so install
the configuration files here:</para>
<screen><userinput>cp ../udev-config-3.rules /etc/udev/rules.d/25-lfs.rules</userinput></screen>
<screen><userinput>cp -v ../udev-config-3.rules /etc/udev/rules.d/25-lfs.rules</userinput></screen>
<para>Install the documentation that explains how to create Udev rules:</para>
<screen><userinput>install -m644 -D docs/writing_udev_rules/index.html /usr/share/doc/udev-&udev-version;/index.html</userinput></screen>
<screen><userinput>install -m644 -D -v docs/writing_udev_rules/index.html /usr/share/doc/udev-&udev-version;/index.html</userinput></screen>
<!-- Edit Me -->
<para>Run the <command>udevstart</command> program to create our full

2
chapter06/vim.xml
View File

@ -87,7 +87,7 @@ redirecting the output to a log file.</para>
when users habitually enter <command>vi</command>, create a
symlink:</para>
<screen><userinput>ln -s vim /usr/bin/vi</userinput></screen>
<screen><userinput>ln -sv vim /usr/bin/vi</userinput></screen>
<para>If an X Window System is going to be installed on the LFS
system, it may be necessary to recompile Vim after installing X. Vim

6
chapter06/zlib.xml
View File

@ -57,8 +57,8 @@ class="extension">.so</filename> file in <filename
class="directory">/lib</filename>. We will remove it and relink it into
<filename class="directory">/usr/lib</filename>:</para>
<screen><userinput>rm /lib/libz.so
ln -sf ../../lib/libz.so.&zlib-version; /usr/lib/libz.so</userinput></screen>
<screen><userinput>rm -v /lib/libz.so
ln -sfv ../../lib/libz.so.&zlib-version; /usr/lib/libz.so</userinput></screen>
<para>Build the static library:</para>
@ -75,7 +75,7 @@ make</userinput></screen>
<para>Fix the permissions on the static library:</para>
<screen><userinput>chmod 644 /usr/lib/libz.a</userinput></screen>
<screen><userinput>chmod -v 644 /usr/lib/libz.a</userinput></screen>
</sect2>

2
chapter07/console.xml
View File

@ -66,7 +66,7 @@ in use is affected (this works only for i386 keymaps):</para>
<para>If the keycode 14 is Backspace instead of Delete, create the
following keymap snippet to fix this issue:</para>
<screen><userinput>mkdir -p /etc/kbd &amp;&amp; cat &gt; /etc/kbd/bs-sends-del &lt;&lt;"EOF"
<screen><userinput>mkdir -pv /etc/kbd &amp;&amp; cat &gt; /etc/kbd/bs-sends-del &lt;&lt;"EOF"
<literal> keycode 14 = Delete Delete Delete Delete
alt keycode 14 = Meta_Delete
altgr alt keycode 14 = Meta_Delete

2
chapter07/network.xml
View File

@ -37,7 +37,7 @@ masks, and so forth.</para>
the <emphasis>eth0</emphasis> device:</para>
<screen><userinput>cd /etc/sysconfig/network-devices &amp;&amp;
mkdir ifconfig.eth0 &amp;&amp;
mkdir -v ifconfig.eth0 &amp;&amp;
cat &gt; ifconfig.eth0/ipv4 &lt;&lt; "EOF"
<literal>ONBOOT=yes
SERVICE=ipv4-static

4
chapter08/grub.xml
View File

@ -129,8 +129,8 @@ information regarding GRUB is located on its website at:
<filename class="symlink">/etc/grub/menu.lst</filename>. To satisfy this requirement, issue the
following command:</para>
<screen><userinput>mkdir /etc/grub &amp;&amp;
ln -s /boot/grub/menu.lst /etc/grub</userinput></screen>
<screen><userinput>mkdir -v /etc/grub &amp;&amp;
ln -sv /boot/grub/menu.lst /etc/grub</userinput></screen>
</sect1>

6
chapter08/kernel.xml
View File

@ -113,14 +113,14 @@ the <filename class="directory">/boot</filename> directory.</para>
<para>The path to the kernel image may vary depending on the platform
being used. The following command assumes an x86 architecture:</para>
<screen><userinput>cp arch/i386/boot/bzImage /boot/lfskernel-&linux-version;</userinput></screen>
<screen><userinput>cp -v arch/i386/boot/bzImage /boot/lfskernel-&linux-version;</userinput></screen>
<para><filename>System.map</filename> is a symbol file for the kernel.
It maps the function entry points of every function in the kernel API,
as well as the addresses of the kernel data structures for the running
kernel. Issue the following command to install the map file:</para>
<screen><userinput>cp System.map /boot/System.map-&linux-version;</userinput></screen>
<screen><userinput>cp -v System.map /boot/System.map-&linux-version;</userinput></screen>
<para>The kernel configuration file <filename>.config</filename>
produced by the <command>make menuconfig</command> step
@ -128,7 +128,7 @@ above contains all the configuration selections for the kernel
that was just compiled. It is a good idea to keep this file for future
reference:</para>
<screen><userinput>cp .config /boot/config-&linux-version;</userinput></screen>
<screen><userinput>cp -v .config /boot/config-&linux-version;</userinput></screen>
<para>It is important to note that the files in the kernel source
directory are not owned by <emphasis>root</emphasis>. Whenever a

16
chapter09/reboot.xml
View File

@ -30,11 +30,11 @@ installation for the first time! First exit from the chroot environment:</para>
<para>Stop the <command>udevd</command> daemon that Udev started earlier, then unmount the virtual files systems:</para>
<screen><userinput>pkill udevd
umount $LFS/dev/pts
umount $LFS/dev/shm
umount $LFS/dev
umount $LFS/proc
umount $LFS/sys</userinput></screen>
umount -v $LFS/dev/pts
umount -v $LFS/dev/shm
umount -v $LFS/dev
umount -v $LFS/proc
umount -v $LFS/sys</userinput></screen>
<para>Unmount the LFS file system itself:</para>
@ -43,9 +43,9 @@ umount $LFS/sys</userinput></screen>
<para>If multiple partitions were created, unmount the other
partitions before unmounting the main one, like this:</para>
<screen role="nodump"><userinput>umount $LFS/usr
umount $LFS/home
umount $LFS</userinput></screen>
<screen role="nodump"><userinput>umount -v $LFS/usr
umount -v $LFS/home
umount -v $LFS</userinput></screen>
<para>Now, reboot the system with:</para>

4
general.ent
View File

@ -1,6 +1,6 @@
<?xml version="1.0" encoding="ISO-8859-1"?>
<!ENTITY version "SVN-20050926">
<!ENTITY releasedate "September 26, 2005">
<!ENTITY version "SVN-20050929">
<!ENTITY releasedate "September 29, 2005">
<!ENTITY milestone "6.2">
<!ENTITY generic-version "development"> <!-- Use "development", "testing", or "x.y[-pre{x}]" -->