Context Navigation

rc288d97	r90e3cb3
31	31	identifiers that the package uses in C preprocessor conditionals. If a package
32	32	has already been set up to have some portability, this program can help to
33		determine what <~~userinput>configure</userinput~~> needs to check. It can fill
	33	determine what <command>configure</command> needs to check. It can fill
34	34	in some gaps in a <filename>configure.in</filename> file generated by
35	35	autoscan.</para>

appendixa/bzip2-desc.xml

rc288d97	r90e3cb3
14	14	block sorting text compression algorithm with Huffman coding. The compression
15	15	rate is generally considerably better than that achieved by more conventional
16		compressors using LZ77/LZ78, like <~~userinput>gzip</userinput~~>.</para>
	16	compressors using LZ77/LZ78, like <command>gzip</command>.</para>
17	17
18	18	<para><command>bzip2recover</command> tries to recover data from damaged

appendixa/lfs-utils-desc.xml

-              rc288d97
+              r90e3cb3
 <para><command>tempfile</command> creates temporary files in a less secure
 manner than <userinput>mktemp</userinput>. It is installed for
+manner than <command>mktemp</command>. It is installed for
 backwards-compatibility.</para>
 <para>The <command>http-get</command> script takes advantage of a little known
 feature of <userinput>bash</userinput> called "net redirection". It is used to
+feature of <command>bash</command> called "net redirection". It is used to
 download from websites without using any other programs.</para>
 <para><command>iana-net</command> uses the <userinput>http-get</userinput>
+<para><command>iana-net</command> uses the <command>http-get</command>
 script to simplify the process of procuring IANA's services and protocols
 configuration files.</para>

appendixa/perl-desc.xml

rc288d97	r90e3cb3
35	35
36	36	<para><command>piconv</command> is a Perl version of the character encoding
37		converter <~~userinput>iconv</userinput~~>.</para>
	37	converter <command>iconv</command>.</para>
38	38
39	39	<para><command>pl2pm</command> is a rough tool for converting Perl4 .pl

chapter03/chapter03.xml

-              rc288d97
+              r90e3cb3
 a swap partition.</para>
 <para>Start a disk partitioning program such as <userinput>cfdisk</userinput>
 or <userinput>fdisk</userinput> with an argument naming the hard disk upon
+<para>Start a disk partitioning program such as <command>cfdisk</command>
+or <command>fdisk</command> with an argument naming the hard disk upon
 which the new partition must be created -- for example
 <filename>/dev/hda</filename> for the primary IDE disk. Create a Linux native
 partition and a swap partition, if needed. Please refer to the man pages of
 <userinput>cfdisk</userinput> or <userinput>fdisk</userinput> if you don't yet
+<command>cfdisk</command> or <command>fdisk</command> if you don't yet
 know how to use the programs.</para>
 …
 <para>You should also ensure that this new partition is not mounted with
 permissions that are too restrictive (such as the nosuid, nodev or noatime
 options). You can run the <userinput>mount</userinput> command without any
+options). You can run the <command>mount</command> command without any
 parameters to see with what options the LFS partition is mounted. If
 you see nosuid, nodev or noatime, you will need to remount it.</para>

chapter04/chapter04.xml

rc288d97	r90e3cb3
50	50	<para>For your convenience the top of the list contains a link to a file
51	51	you can use with the <ulink url="http://wget.sunsite.dk">wget</ulink>
52		program. Using this file and the <~~userinput>wget</userinput~~> program will
	52	program. Using this file and the <command>wget</command> program will
53	53	make it easy to download all the files at once, rather than downloading each
54	54	and every individual file manually.</para>

chapter05/bash.xml

rc288d97	r90e3cb3
37	37	<screen><userinput>make install</userinput></screen>
38	38
39		<para>And make a link for the programs that use <~~userinput>sh</userinput~~>
	39	<para>And make a link for the programs that use <command>sh</command>
40	40	for a shell:</para>
41	41

chapter05/binutils-pass1.xml

-              rc288d97
+              r90e3cb3
 <listitem><para><userinput>LDFLAGS="-all-static"</userinput>: This tells the
 linker that all the Binutils programs should be linked statically. However,
 strictly speaking, <userinput>"-all-static"</userinput> is first passed to the
 <emphasis>libtool</emphasis> program which then passes
 <userinput>"-static"</userinput> on to the linker.</para></listitem>
+strictly speaking, <emphasis>"-all-static"</emphasis> is first passed to the
+<command>libtool</command> program which then passes
+<emphasis>"-static"</emphasis> on to the linker.</para></listitem>
 </itemizedlist>

chapter05/bzip2.xml

rc288d97	r90e3cb3
14	14	<title>Installation of Bzip2</title>
15	15
16		<para>The Bzip2 package doesn't contain a <~~userinput>configure</userinput~~>
	16	<para>The Bzip2 package doesn't contain a <command>configure</command>
17	17	script. Compile and install it with a straightforward:</para>
18	18

chapter05/chapter05.xml

-              rc288d97
+              r90e3cb3
 <para>The build instructions assume that you are using the
 <userinput>bash</userinput> shell. It is also expected that you have already
+<command>bash</command> shell. It is also expected that you have already
 unpacked a source package (while logged in as user <emphasis>lfs</emphasis> --
 explained shortly) and performed a <userinput>cd</userinput> into the source
 …
 <filename class="directory">/lib</filename> directory on your host system. A
 surefire way is to inspect a random binary from your host system by running:
 <userinput>'readelf -l &lt;name of binary&gt; | grep interpreter'</userinput>
+<userinput>readelf -l &lt;name of binary&gt; | grep interpreter</userinput>
 and noting the output. The authoritative reference covering all platforms is in
 the <filename>shlib-versions</filename> file in the root of the Glibc source
 …
 choose.</para></listitem>
 <listitem><para>Careful manipulation of <userinput>gcc</userinput>'s
+<listitem><para>Careful manipulation of <command>gcc</command>'s
 <emphasis>specs</emphasis> file to tell the compiler which target dynamic
 linker will be used.</para></listitem>
 …
 <para>Binutils is installed first because both GCC and Glibc perform various
 feature tests on the assembler and linker during their respective runs of
 <userinput>./configure</userinput> to determine which software features to enable
+<command>./configure</command> to determine which software features to enable
 or disable. This is more important than one might first realize. An incorrectly
 configured GCC or Glibc can result in a subtly broken toolchain where the impact
 …
 the tools in one location are hard linked to the other. An important facet of
 the linker is its library search order. Detailed information can be obtained
 from <userinput>ld</userinput> by passing it the <emphasis>--verbose</emphasis>
 flag. For example: <userinput>'ld --verbose | grep SEARCH'</userinput> will
+from <command>ld</command> by passing it the <emphasis>--verbose</emphasis>
+flag. For example: <command>ld --verbose | grep SEARCH</command> will
 show you the current search paths and their order. You can see what files are
 actually linked by <userinput>ld</userinput> by compiling a dummy program and
 passing the <emphasis>--verbose</emphasis> switch. For example:
 <userinput>'gcc dummy.c -Wl,--verbose 2>&amp;1 | grep succeeded'</userinput>
 will show you all the files successfully opened during the link.</para>
+actually linked by <command>ld</command> by compiling a dummy program and
+passing the <emphasis>--verbose</emphasis> switch to the linker. For example:
+<command>gcc dummy.c -Wl,--verbose 2>&amp;1 | grep succeeded</command>
+will show you all the files successfully opened during the linking.</para>
 <para>The next package installed is GCC and during its run of
 <userinput>./configure</userinput> you'll see, for example:</para>
+<command>./configure</command> you'll see, for example:</para>
 <blockquote><screen>checking what assembler to use... /tools/i686-pc-linux-gnu/bin/as
 …
 <para>This is important for the reasons mentioned above. It also demonstrates
 that GCC's configure script does not search the $PATH directories to find which
 tools to use. However, during the actual operation of <userinput>gcc</userinput>
+tools to use. However, during the actual operation of <command>gcc</command>
 itself, the same search paths are not necessarily used. You can find out which
 standard linker <userinput>gcc</userinput> will use by running:
 <userinput>'gcc -print-prog-name=ld'</userinput>.
 Detailed information can be obtained from <userinput>gcc</userinput> by passing
+standard linker <command>gcc</command> will use by running:
+<command>gcc -print-prog-name=ld</command>.
+Detailed information can be obtained from <command>gcc</command> by passing
 it the <emphasis>-v</emphasis> flag while compiling a dummy program. For
 example: <userinput>'gcc -v dummy.c'</userinput> will show you detailed
+example: <command>gcc -v dummy.c</command> will show you detailed
 information about the preprocessor, compilation and assembly stages, including
 <userinput>gcc</userinput>'s include search paths and their order.</para>
+<command>gcc</command>'s include search paths and their order.</para>
 <para>The next package installed is Glibc. The most important considerations for
 building Glibc are the compiler, binary tools and kernel headers. The compiler
 is generally no problem as Glibc will always use the <userinput>gcc</userinput>
+is generally no problem as Glibc will always use the <command>gcc</command>
 found in a $PATH directory. The binary tools and kernel headers can be a little
 more troublesome. Therefore we take no risks and use the available configure
 switches to enforce the correct selections. After the run of
 <userinput>./configure</userinput> you can check the contents of the
+<command>./configure</command> you can check the contents of the
 <filename>config.make</filename> file in the
 <filename class="directory">glibc-build</filename> directory for all the
 important details. You'll note some interesting items like the use of
 <userinput>CC="gcc -B/tools/bin/"</userinput> to control which binary tools are
+<emphasis>CC="gcc -B/tools/bin/"</emphasis> to control which binary tools are
 used, and also the use of the <emphasis>-nostdinc</emphasis> and
 <emphasis>-isystem</emphasis> flags to control the compiler's include search
 …
 <para>After the Glibc installation, we make some adjustments to ensure that
 searching and linking take place only within our <filename>/tools</filename>
 prefix. We install an adjusted <userinput>ld</userinput>, which has a hard-wired
+prefix. We install an adjusted <command>ld</command>, which has a hard-wired
 search path limited to <filename class="directory">/tools/lib</filename>. Then
 we amend <userinput>gcc</userinput>'s specs file to point to our new dynamic
+we amend <command>gcc</command>'s specs file to point to our new dynamic
 linker in <filename class="directory">/tools/lib</filename>. This last step is
 <emphasis>vital</emphasis> to the whole process. As mentioned above, a
 hard-wired path to a dynamic linker is embedded into every ELF shared
 executable. You can inspect this by running:
+<userinput>'readelf -l &lt;name of binary&gt; | grep interpreter'</userinput>.
+By amending <userinput>gcc</userinput>'s specs file, we are ensuring that every
+program compiled from here through the end of <xref linkend="chapter05"/> will
+use our new dynamic linker in
+<filename class="directory">/tools/lib</filename>.</para>
+<command>readelf -l &lt;name of binary&gt; | grep interpreter</command>.
+By amending <command>gcc</command>'s specs file, we are ensuring that every
+program compiled from here through the end of this chapter will use our new
+dynamic linker in <filename class="directory">/tools/lib</filename>.</para>
 <para>The need to use the new dynamic linker is also the reason why we apply the
 …
 <para>During the second pass of Binutils, we are able to utilize the
 <emphasis>--with-lib-path</emphasis> configure switch to control
 <userinput>ld</userinput>'s library search path. From this point onwards, the
+<command>ld</command>'s library search path. From this point onwards, the
 core toolchain is self-contained and self-hosted. The remainder of the
 <xref linkend="chapter05"/> packages all build against the new Glibc in
 …
 <filename class="directory">/usr</filename>, we perform a quick changeover of
 the toolchain defaults, then proceed for real in building the rest of the
 target <xref linkend="chapter06"/> LFS system.</para>
+target LFS system.</para>
 <sect2>
 …
 <screen><userinput>ln -s $LFS/tools /</userinput></screen>
 <note><para>The above command is correct. The <userinput>ln</userinput> command
+<note><para>The above command is correct. The <command>ln</command> command
 has a few syntactic variations, so be sure to check the info page before
 reporting what you may think is an error.</para></note>
 …
 <screen><userinput>su - lfs</userinput></screen>
 <para>The "<userinput>-</userinput>" instructs <userinput>su</userinput> to
 start a <emphasis>login</emphasis> shell.</para>
+<para>The "<command>-</command>" instructs <command>su</command> to start a
+<emphasis>login</emphasis> shell.</para>
 </sect1>
 …
 <para>We're going to set up a good working environment by creating two new
 startup files for the <userinput>bash</userinput> shell. While logged in as
+startup files for the <command>bash</command> shell. While logged in as
 user <emphasis>lfs</emphasis>, issue the following command to create a new
 <filename>.bash_profile</filename>:</para>
 …
 <filename>/etc/profile</filename> of your host (probably containing some
 settings of environment variables) and then <filename>.bash_profile</filename>.
 The <userinput>exec env -i ... /bin/bash</userinput> command in the latter file
+The <command>exec env -i ... /bin/bash</command> command in the latter file
 replaces the running shell with a new one with a completely empty environment,
 except for the HOME, TERM and PS1 variables. This ensures that no unwanted and
 …
 <userinput>EOF</userinput></screen>
 <para>The <userinput>set +h</userinput> command turns off
 <userinput>bash</userinput>'s hash function. Normally hashing is a useful
 feature: <userinput>bash</userinput> uses a hash table to remember the
+<para>The <command>set +h</command> command turns off
+<command>bash</command>'s hash function. Normally hashing is a useful
+feature: <command>bash</command> uses a hash table to remember the
 full pathnames of executable files to avoid searching the PATH time and time
 again to find the same executable. However, we'd like the new tools to be
 used as soon as they are installed. By switching off the hash function, our
 "interactive" commands (<userinput>make</userinput>,
 <userinput>patch</userinput>, <userinput>sed</userinput>,
 <userinput>cp</userinput> and so forth) will always use
+"interactive" commands (<command>make</command>,
+<command>patch</command>, <command>sed</command>,
+<command>cp</command> and so forth) will always use
 the newest available version during the build process.</para>
 …
 You will need to investigate and retrace your steps to find out where the
 problem is and correct it. There is no point in continuing until this is done.
 First, redo the sanity check using <userinput>gcc</userinput> instead of
 <userinput>cc</userinput>. If this works it means the
+First, redo the sanity check using <command>gcc</command> instead of
+<command>cc</command>. If this works it means the
 <filename class="symlink">/tools/bin/cc</filename> symlink is missing. Revisit
 <xref linkend="ch-tools-gcc-pass1"/> and fix the symlink. Second, ensure your $PATH
 …
 <para>Take care <emphasis>not</emphasis> to use
 <userinput>--strip-unneeded</userinput> on the libraries -- they would be
+<emphasis>--strip-unneeded</emphasis> on the libraries -- they would be
 destroyed and you would have to build Glibc all over again.</para>

chapter05/gcc-pass1.xml

-              rc288d97
+              r90e3cb3
 <listitem><para><userinput>--with-local-prefix=/tools</userinput>: The
 purpose of this switch is to remove <filename>/usr/local/include</filename>
 from <userinput>gcc</userinput>'s include search path. This is not absolutely
+from <command>gcc</command>'s include search path. This is not absolutely
 essential; however, we want to try to minimize the influence of the host
 system, thus making this a sensible thing to do.</para></listitem>
 …
 having <filename>libgcc_eh.a</filename> available ensures that the configure
 script for Glibc (the next package we compile) produces the proper results.
 Note that the <userinput>gcc</userinput> binaries will still be linked
 statically, as this is controlled by the <userinput>-static</userinput>
+Note that the <command>gcc</command> binaries will still be linked
+statically, as this is controlled by the <command>-static</command>
 value of BOOT_LDFLAGS further on.</para></listitem>
 …
 <para>As a finishing touch we'll create the <filename
 class="symlink">/tools/bin/cc</filename> symlink. Many programs and
 scripts run <userinput>cc</userinput> instead of <userinput>gcc</userinput>,
+scripts run <command>cc</command> instead of <command>gcc</command>,
 a thing meant to keep programs generic and therefore usable on all kinds of
 Unix systems. Not everybody has the GNU C compiler installed. Simply running
 <userinput>cc</userinput> leaves the system administrator free to decide what
+<command>cc</command> leaves the system administrator free to decide what
 C compiler to install, as long as there's a symlink pointing to it:</para>

chapter05/gcc-pass2.xml

-              rc288d97
+              r90e3cb3
 <screen><userinput>make</userinput></screen>
 <para>There is no need to use the <userinput>bootstrap</userinput> target now,
+<para>There is no need to use the <emphasis>bootstrap</emphasis> target now,
 as the compiler we're using to compile this GCC was built from the exact same
 version of the GCC sources we used earlier.</para>
 …
 <screen><userinput>make -k check</userinput></screen>
 <para>The <userinput>-k</userinput> flag is used to make the test suite run
+<para>The <emphasis>-k</emphasis> flag is used to make the test suite run
 through to completion and not stop at the first failure. The GCC test suite is
 very comprehensive and is almost guaranteed to generate a few failures. To get
 …
 <para>The unexpected pass for g++ is due to the use of
 <userinput>--enable-__cxa_atexit</userinput>. Apparently not all platforms
+<emphasis>--enable-__cxa_atexit</emphasis>. Apparently not all platforms
 supported by GCC have support for "__cxa_atexit" in their C libraries, so this
 test is not always expected to pass.</para>
 <para>The 24 unexpected passes for libstdc++ are due to the use of
 <userinput>--enable-clocale=gnu</userinput>, which is the correct choice on
+<emphasis>--enable-clocale=gnu</emphasis>, which is the correct choice on
 Glibc-based systems of versions 2.2.5 and above. The underlying locale support
 in the GNU C library is superior to that of the otherwise selected "generic"

chapter05/glibc.xml

-              rc288d97
+              r90e3cb3
 <listitem><para><userinput>--without-gd</userinput>: This switch ensures
 that we don't build the <userinput>memusagestat</userinput> program, which
+that we don't build the <command>memusagestat</command> program, which
 strangely enough insists on linking against the host's libraries (libgd,
 libpng, libz, and so forth).</para></listitem>
 …
 could still occur -- the <emphasis>math</emphasis>
 tests for example. When experiencing a failure, make a note of it, then
 continue by reissuing the <userinput>make check</userinput>. The test suite
+continue by reissuing the <command>make check</command>. The test suite
 should pick up where it left off and continue on. You can circumvent this
 stop-start sequence by issuing a <userinput>make -k check</userinput>. But if
+stop-start sequence by issuing a <command>make -k check</command>. But if
 you do that, be sure to log the output so that you can later peruse the log
 file and examine the total number of failures.</para>
 …
 <para>An alternative to running the previous command is to install only those
 locales which you need or want. This can be achieved by using the
 <userinput>localedef</userinput> command. Information on this can be found in
+<command>localedef</command> command. Information on this can be found in
 the <filename>INSTALL</filename> file in the Glibc source. However, there are
 a number of locales that are essential for the tests of future packages to

chapter05/grep.xml

rc288d97	r90e3cb3
23	23	<itemizedlist>
24	24	<listitem><para><userinput>--disable-perl-regexp</userinput>: This makes sure
25		that <~~userinput>grep</userinput~~> does not get linked against a PCRE library
	25	that <command>grep</command> does not get linked against a PCRE library
26	26	that may be present on the host and would not be available once we enter the
27	27	chroot environment.</para></listitem>

chapter05/kernelheaders.xml

rc288d97	r90e3cb3
13	13	<para>As some packages need to refer to the kernel header files, we're going
14	14	to unpack the kernel archive now, set it up, and copy the required files to a
15		place where <~~userinput>gcc</userinput~~> can later find them.</para>
	15	place where <command>gcc</command> can later find them.</para>
16	16
17	17	<para>Prepare for the header installation with:</para>

chapter05/patch.xml

rc288d97	r90e3cb3
18	18	<screen><userinput>CPPFLAGS=-D_GNU_SOURCE ./configure --prefix=/tools</userinput></screen>
19	19
20		<para>The preprocessor flag <~~userinput>-D_GNU_SOURCE</userinput~~> is only needed
	20	<para>The preprocessor flag <emphasis>-D_GNU_SOURCE</emphasis> is only needed
21	21	on the PowerPC platform. On other architectures you can leave it out.</para>
22	22

chapter06/aboutdebug.xml

rc288d97	r90e3cb3
38	38
39	39	<para>To remove debugging symbols from a binary (which must be an a.out
40		or ELF binary), run <~~userinput>strip --strip-debug filename</userinput~~>.
	40	or ELF binary), run <command>strip --strip-debug filename</command>.
41	41	Wildcards can be used to treat multiple files (use something like
42	42	<userinput>strip --strip-debug $LFS/tools/bin/*</userinput>).</para>

chapter06/bash.xml

rc288d97	r90e3cb3
40	40	<screen><userinput>make install</userinput></screen>
41	41
42		<para>And reload the newly compiled <~~userinput>bash</userinput~~> program:</para>
	42	<para>And reload the newly compiled <command>bash</command> program:</para>
43	43
44	44	<screen><userinput>exec /bin/bash --login +h</userinput></screen>

chapter06/bzip2.xml

-              rc288d97
+              r90e3cb3
 <para>The Bzip2 package contains programs for compressing and decompressing
 files. On text files they achieve a much better compression than the
 traditional <userinput>gzip</userinput>.</para>
+traditional <command>gzip</command>.</para>
 <screen>&buildtime; &bzip2-time;
 …
 <para>If you are reinstalling Bzip2, you will now first have to do
 <userinput>rm -f /usr/bin/bz*</userinput>, otherwise the following
 <userinput>make install</userinput> will fail.</para>
+<command>make install</command> will fail.</para>
 <para>Install the programs:</para>
 …
 <screen><userinput>make install</userinput></screen>
 <para>And install the shared <userinput>bzip2</userinput> binary into the
+<para>And install the shared <command>bzip2</command> binary into the
 <filename class="directory">/bin</filename> directory, then make some
 necessary symbolic links, and clean up:</para>

chapter06/chapter06.xml

-              rc288d97
+              r90e3cb3
 the packages we need. Before you can chroot, however, you need to become
 <emphasis>root</emphasis>, since only <emphasis>root</emphasis>
 can execute the <userinput>chroot</userinput> command.</para>
+can execute the <command>chroot</command> command.</para>
 <para>Just like earlier, ensure the LFS environment variable is set up properly
 by running <userinput>echo $LFS</userinput> and ensuring it shows the path to
 your LFS partition's mount point, which is
+<filename class="directory">/mnt/lfs</filename> if you followed our
+example.</para>
+<filename class="directory">/mnt/lfs</filename> if you followed our example.</para>
 <para>Become <emphasis>root</emphasis> and run the following command
 …
 &nbsp;&nbsp;&nbsp;&nbsp;/tools/bin/bash --login +h</userinput></screen>
 <para>The <userinput>-i</userinput> option given to the
 <userinput>env</userinput> command will clear all variables of the chroot
+<para>The <emphasis>-i</emphasis> option given to the
+<command>env</command> command will clear all variables of the chroot
 environment. After that, only the HOME, TERM, PS1 and PATH variables are
 set again. The TERM=$TERM construct will set the TERM variable inside chroot
 to the same value as outside chroot; this variable is needed for programs
 like <userinput>vim</userinput> and <userinput>less</userinput> to operate
+like <command>vim</command> and <command>less</command> to operate
 properly. If you need other variables present, such as CFLAGS or CXXFLAGS,
 this is a good place to set them again.</para>
 …
 as soon as its final version is installed. Well, at least when the shell
 doesn't remember the locations of executed binaries -- for this reason hashing
 is switched off by passing the <userinput>+h</userinput> option to
 <userinput>bash</userinput>.</para>
+is switched off by passing the <emphasis>+h</emphasis> option to
+<command>bash</command>.</para>
 <para>You have to make sure all the commands in the rest of this chapter and
 …
 <screen><userinput>exec /tools/bin/bash --login +h</userinput></screen>
 <para>Note the use of the <userinput>+h</userinput> directive. This tells
 <userinput>bash</userinput> not to use its internal path hashing. Without this
 directive, <userinput>bash</userinput> would remember the paths to binaries it
+<para>Note the use of the <emphasis>+h</emphasis> directive. This tells
+<command>bash</command> not to use its internal path hashing. Without this
+directive, <command>bash</command> would remember the paths to binaries it
 has executed. Since we want to use our newly compiled binaries as soon as
 they are installed, we turn off this function for the duration of this
 chapter.</para>
 <para>The <userinput>login</userinput>, <userinput>agetty</userinput> and
 <userinput>init</userinput> programs (and some others) use a number of log
+<para>The <command>login</command>, <command>agetty</command> and
+<command>init</command> programs (and some others) use a number of log
 files to record information such as who was logged into the system and when.
 These programs, however, won't write to the log files if they don't already
 …
 against the libraries in <filename>/usr/lib</filename> and
 <filename>/lib</filename>. The extra
 <userinput>INSTALL=/tools/bin/install</userinput> is needed because the Makefile
+<emphasis>INSTALL=/tools/bin/install</emphasis> is needed because the Makefile
 created during the second pass still contains the reference to
 <filename>/usr/bin/install</filename>, which we obviously haven't installed yet.

chapter06/config-glibc.xml

rc288d97	r90e3cb3
55	55
56	56	<para>Of course, instead of <emphasis>Canada/Eastern</emphasis>, fill in
57		the name of the time zone that the <~~userinput>tzselect</userinput~~> script
	57	the name of the time zone that the <command>tzselect</command> script
58	58	gave you.</para>
59	59

chapter06/config-shadowpwd.xml

-              rc288d97
+              r90e3cb3
 <para>Under normal circumstances, you won't have created any passwords yet.
 However, if returning to this section to enable shadowing, you should reset any
 current user passwords with the <userinput>passwd</userinput> command or any
 group passwords with the <userinput>gpasswd</userinput> command.</para>
+current user passwords with the <command>passwd</command> command or any
+group passwords with the <command>gpasswd</command> command.</para>
 </sect2>

chapter06/config-vim.xml

-              rc288d97
+              r90e3cb3
 <sect2><title>Configuring Vim</title>
 <para>By default, <userinput>vim</userinput> runs in vi-compatible mode. Some
 people might like this, but we prefer to run <userinput>vim</userinput> in its
+<para>By default, <command>vim</command> runs in vi-compatible mode. Some
+people might like this, but we prefer to run <command>vim</command> in its
 own mode (else we wouldn't have included it in this book, but the original
 <userinput>vi</userinput>). Create a default vim configuration file by running
+<command>vi</command>). Create a default vim configuration file by running
 the following:</para>
 …
 <userinput>EOF</userinput></screen>
 <para>The <userinput>set nocompatible</userinput> will make
 <userinput>vim</userinput> behave in a more useful way than the default
 vi-compatible manner. The <userinput>set backspace=2</userinput> allows
+<para>The <emphasis>set nocompatible</emphasis> will make
+<command>vim</command> behave in a more useful way than the default
+vi-compatible manner. The <emphasis>set backspace=2</emphasis> allows
 backspacing over line breaks, autoindent and the start of insert. And the
 <userinput>syntax on</userinput> switches on <userinput>vim</userinput>'s
+<emphasis>syntax on</emphasis> switches on <command>vim</command>'s
 semantic colouring.</para>

chapter06/coreutils.xml

-              rc288d97
+              r90e3cb3
 <screen><userinput>patch -Np1 -i ../&coreutils-posixver-patch;</userinput></screen>
 <para>Normally the functionality of <userinput>uname</userinput> is somewhat
 broken, in that the <userinput>-p</userinput> switch always returns "unknown".
+<para>Normally the functionality of <command>uname</command> is somewhat
+broken, in that the <emphasis>-p</emphasis> switch always returns "unknown".
 The following patch fixes this behaviour for Intel architectures:</para>
 …
 <para>We do not want Coreutils to install its version of the
 <userinput>hostname</userinput> program, because it is inferior to the version
+<command>hostname</command> program, because it is inferior to the version
 provided by Net-tools. Prevent its installation by applying a patch:</para>
 …
 <screen><userinput>make</userinput></screen>
 <para>The <userinput>su</userinput> program from Coreutils wasn't installed in
+<para>The <command>su</command> program from Coreutils wasn't installed in
 Chapter 5 because it needed <emphasis>root</emphasis> privilege to do so. We're
 going to need it in a few moments for the test suite. Therefore we work around

chapter06/flex.xml

-              rc288d97
+              r90e3cb3
 <screen><userinput>ln -s libfl.a /usr/lib/libl.a</userinput></screen>
 <para>A few programs don't know about <userinput>flex</userinput> yet and try
 to run its predecessor <userinput>lex</userinput>. To support those programs,
+<para>A few programs don't know about <command>flex</command> yet and try
+to run its predecessor <command>lex</command>. To support those programs,
 create a shell script named <filename>lex</filename> that calls
 <userinput>flex</userinput> in Lex emulation mode:</para>
+<command>flex</command> in Lex emulation mode:</para>
 <screen><userinput>cat &gt; /usr/bin/lex &lt;&lt; "EOF"</userinput>

chapter06/gcc.xml

rc288d97	r90e3cb3
87	87	<screen><userinput>ln -s ../usr/bin/cpp /lib</userinput></screen>
88	88
89		<para>Many packages use the name <~~userinput>cc</userinput~~> to call the C
	89	<para>Many packages use the name <command>cc</command> to call the C
90	90	compiler. To satisfy those packages, create a symlink:</para>
91	91

chapter06/glibc.xml

rc288d97	r90e3cb3
92	92	<para>An alternative to running the previous command is to install only those
93	93	locales which you need or want. This can be achieved by using the
94		<~~userinput>localedef</userinput~~> command. Information on this can be found in
	94	<command>localedef</command> command. Information on this can be found in
95	95	the <filename>INSTALL</filename> file in the Glibc source. However, there are
96	96	a number of locales that are essential for the tests of future packages to

chapter06/groff.xml

rc288d97	r90e3cb3
33	33	<screen><userinput>make install</userinput></screen>
34	34
35		<para>Some documentation programs, such as <~~userinput>xman</userinput~~>,
	35	<para>Some documentation programs, such as <command>xman</command>,
36	36	will not work properly without the following symlinks:</para>
37	37

chapter06/gzip.xml

-              rc288d97
+              r90e3cb3
 <screen><userinput>./configure --prefix=/usr</userinput></screen>
 <para>The <userinput>gzexe</userinput> script has the location of the
 <userinput>gzip</userinput> binary hard-wired into it. Because we later change
+<para>The <command>gzexe</command> script has the location of the
+<command>gzip</command> binary hard-wired into it. Because we later change
 the location of the binary, the following command assures that the new
 location gets placed into the script:</para>

chapter06/inetutils.xml

rc288d97	r90e3cb3
62	62	<screen><userinput>make install</userinput></screen>
63	63
64		<para>And move the <~~userinput>ping</userinput~~> program to its proper place:</para>
	64	<para>And move the <command>ping</command> program to its proper place:</para>
65	65
66	66	<screen><userinput>mv /usr/bin/ping /bin</userinput></screen>

chapter06/kbd.xml

-              rc288d97
+              r90e3cb3
 <title>Installation of Kbd</title>
 <para>By default some of Kbd's utilities (<userinput>setlogcons</userinput>,
 <userinput>setvesablank</userinput> and <userinput>getunimap</userinput>) are
+<para>By default some of Kbd's utilities (<command>setlogcons</command>,
+<command>setvesablank</command> and <command>getunimap</command>) are
 not installed. First enable the compilation of these utilities:</para>

chapter06/lfs-utils.xml

rc288d97	r90e3cb3
24	24	<itemizedlist>
25	25	<listitem><para><userinput>--with-libc</userinput>: This causes the
26		<~~userinput>mktemp</userinput~~> program to use the <emphasis>mkstemp</emphasis>
	26	<command>mktemp</command> program to use the <emphasis>mkstemp</emphasis>
27	27	and <emphasis>mkdtemp</emphasis> functions from the system C
28	28	library.</para></listitem>

chapter06/makedev.xml

-              rc288d97
+              r90e3cb3
 <para>Note that unpacking the <filename>MAKEDEV-&makedev-version;.bz2</filename>
 file doesn't create a directory for you to <userinput>cd</userinput> into, as
+file doesn't create a directory for you to <command>cd</command> into, as
 the file contains only a shell script.</para>
 <para>Install the <userinput>MAKEDEV</userinput> script:</para>
+<para>Install the <command>MAKEDEV</command> script:</para>
 <screen><userinput>bzcat MAKEDEV-&makedev-version;.bz2 &gt; /dev/MAKEDEV
 …
 <listitem><para><userinput>generic-nopty</userinput>: This instructs
 <userinput>MAKEDEV</userinput> to create a generic selection of commonly used
+<command>MAKEDEV</command> to create a generic selection of commonly used
 device special files, except for the ptyXX and ttyXX range of files. We don't
 need those files because we are going to use Unix98 PTYs via the
 …
 <para>If it turns out that some special device <filename>zzz</filename> that
 you need is missing, try running <userinput>./MAKEDEV -v zzz</userinput>.
 Alternatively, you may create devices via the <userinput>mknod</userinput>
+Alternatively, you may create devices via the <command>mknod</command>
 program. Please refer to its man and info pages if you need more
 information.</para>

chapter06/man.xml

-              rc288d97
+              r90e3cb3
 <para>The third is also a sed substitution to comment out the "MANPATH
 /usr/man" line in the <filename>man.conf</filename> file to prevent redundant
 results when using programs such as <userinput>whatis</userinput>:</para>
+results when using programs such as <command>whatis</command>:</para>
 <screen><userinput>sed -i 's%MANPATH./usr/man%#&amp;%' src/man.conf.in</userinput></screen>
 …
 <listitem><para><userinput>-confdir=/etc</userinput>: This tells the
 <userinput>man</userinput> program to look for the <filename>man.conf</filename>
+<command>man</command> program to look for the <filename>man.conf</filename>
 configuration file in the <filename>/etc</filename> directory.</para></listitem>
 </itemizedlist>
 …
 <screen><userinput>make install</userinput></screen>
 <note><para>If you wish to disable SGR escape sequences, you should
+edit the man.conf file and add the <userinput>-c</userinput> argument
 to nroff.</para></note>
+<note><para>If you wish to disable SGR escape sequences, you should edit the
+<filename>man.conf</filename> file and add the <emphasis>-c</emphasis> switch
+to NROFF.</para></note>
 <para>You may want to also take a look at the BLFS page at

chapter06/mountproc.xml

rc288d97	r90e3cb3
45	45	without support for the devpts file system. You can check which file systems
46	46	your kernel supports by peeking into its internals with a command such as
47		<~~userinput>cat /proc/filesystems</userinput~~>. If a file system type named
	47	<command>cat /proc/filesystems</command>. If a file system type named
48	48	<emphasis>devfs</emphasis> is listed there, then we'll be able to work around
49	49	the problem by mounting the host's devfs file system on top of the new

chapter06/nettools.xml

-              rc288d97
+              r90e3cb3
 <para>If you don't know what to answer to all the questions asked during the
 <userinput>make config</userinput> phase below, then just accept the defaults.
+<command>make config</command> phase below, then just accept the defaults.
 This will be just fine in the majority of cases. What you're asked here is a
 bunch of questions about which network protocols you've enabled in your
 …
 <para>If you intend to accept the default settings, you may skip the
 questions generated by <emphasis>make config</emphasis> by running
+questions generated by <command>make config</command> by running
 <userinput>yes "" | make config</userinput> instead.</para>

chapter06/patch.xml

rc288d97	r90e3cb3
20	20	<screen><userinput>CPPFLAGS=-D_GNU_SOURCE ./configure --prefix=/usr</userinput></screen>
21	21
22		<para>Again, the preprocessor flag <~~userinput>-D_GNU_SOURCE</userinput~~> is only
	22	<para>Again, the preprocessor flag <emphasis>-D_GNU_SOURCE</emphasis> is only
23	23	needed on the PowerPC platform. On other architectures you can leave it out.</para>
24	24

chapter06/perl.xml

rc288d97	r90e3cb3
23	23
24	24	<para>If you want more control over the way Perl sets itself up to be
25		built, you can run the interactive <~~userinput>Configure</userinput~~> script
	25	built, you can run the interactive <command>Configure</command> script
26	26	instead and modify the way Perl is built. If you think you can live with the
27	27	(sensible) defaults Perl auto-detects, then just use the command listed

chapter06/psmisc.xml

-              rc288d97
+              r90e3cb3
 ln -sf pstree /usr/bin/pstree.x11</userinput></screen>
 <para>By default Psmisc's <userinput>pidof</userinput> program isn't installed.
+<para>By default Psmisc's <command>pidof</command> program isn't installed.
 Generally, this isn't a problem because we later install the Sysvinit package,
 which provides a better <userinput>pidof</userinput> program. But if you're not
+which provides a better <command>pidof</command> program. But if you're not
 going to use Sysvinit, you should complete the installation of Psmisc by
 creating the following symlink:</para>

chapter06/shadowpwd.xml

-              rc288d97
+              r90e3cb3
 <title>Installation of Shadow</title>
 <para>Shadow hard-wires the path to the <userinput>passwd</userinput> binary
+<para>Shadow hard-wires the path to the <command>passwd</command> binary
 within the binary itself, but does this the wrong way. If a
 <userinput>passwd</userinput> binary is not present before installing Shadow,
+<command>passwd</command> binary is not present before installing Shadow,
 the package incorrectly assumes it is going to be located at
 <filename>/bin/passwd</filename>, but then installs it in
 …
 <screen><userinput>mkdir /etc/default</userinput></screen>
 <para>Coreutils has already installed a better <userinput>groups</userinput>
+<para>Coreutils has already installed a better <command>groups</command>
 program in <filename>/usr/bin</filename>. Remove the one installed by
 Shadow:</para>

chapter06/utillinux.xml

-              rc288d97
+              r90e3cb3
 <para>The FHS recommends that we use <filename>/var/lib/hwclock</filename>,
 instead of the usual <filename>/etc</filename>, as the location for the
 <filename>adjtime</filename> file. To make the <userinput>hwclock</userinput>
+<filename>adjtime</filename> file. To make the <command>hwclock</command>
 program FHS-compliant, run the following:</para>
 …
 <itemizedlist>
 <listitem><para><userinput>HAVE_KILL=yes</userinput>: This prevents the
 <userinput>kill</userinput> program (already installed by Procps) from being
+<command>kill</command> program (already installed by Procps) from being
 built and installed again.</para></listitem>
 <listitem><para><userinput>HAVE_SLN=yes</userinput>: This prevents the
 <userinput>sln</userinput> program (a statically linked
 <userinput>ln</userinput>, already installed by Glibc) from being built and
+<command>sln</command> program (a statically linked
+<command>ln</command>, already installed by Glibc) from being built and
 installed again.</para></listitem>
 </itemizedlist>

chapter06/vim.xml

rc288d97	r90e3cb3
53	53	<screen><userinput>make install</userinput></screen>
54	54
55		<para>When called as <~~userinput>vi</userinput>, <userinput>vim</userinput~~>
	55	<para>When called as <command>vi</command>, <command>vim</command>
56	56	will run in old-fashioned vi-mode. To allow this, create a symlink:</para>
57	57

chapter07/sysklogd.xml

-              rc288d97
+              r90e3cb3
 <para>The <filename>sysklogd</filename> script invokes the
 <userinput>syslogd</userinput> program with the <emphasis>-m 0</emphasis>
+option. This option turns off the periodic timestamp mark that syslogd
+writes to the log files every 20 minutes by default. If you want to turn
+on this periodic timestamp mark, edit the <filename>sysklogd</filename>
+script and make the changes accordingly. See <userinput>man
 syslogd</userinput> for more information.</para>
+<command>syslogd</command> program with the <emphasis>-m 0</emphasis> option.
+This option turns off the periodic timestamp mark that
+<command>syslogd</command> writes to the log files every 20 minutes by default.
+If you want to turn on this periodic timestamp mark, edit the
+<filename>sysklogd</filename> script and make the changes accordingly. See
+<userinput>man syslogd</userinput> for more information.</para>
 </sect1>

chapter07/usage.xml

-              rc288d97
+              r90e3cb3
 : reboot the computer</literallayout>
+<para>The command used to change runlevels is <userinput>init
+&lt;runlevel&gt;</userinput> where &lt;runlevel&gt; is
+the target runlevel. For example, to reboot the computer, a user would issue
+the init 6 command. The reboot command is just an alias, as is the halt
+command an alias to init 0.</para>
+<para>The command used to change runlevels is <command>init
+&lt;runlevel&gt;</command> where &lt;runlevel&gt; is the target runlevel. For
+example, to reboot the computer, a user would issue the <command>init
+</command> command. The <command>reboot</command> command is just an alias for
+it, as is the <command>halt</command> command an alias for <command>init
+</command>.</para>
+<para>There are a number of directories under /etc/rc.d that look like
+like rc?.d where ? is the number of the runlevel and rcsysinit.d which
+contain a number of symbolic links. Some begin with a K, the others
+begin with an S, and all of them have two numbers following the initial
+letter. The K means to stop (kill) a service, and the S means to start a
+service. The numbers determine the order in which the scripts are run,
+from 00 to 99; the lower the number the sooner it gets executed. When init
+switches to another runlevel, the appropriate services get killed and
+others get started.</para>
+<para>There are a number of directories under <filename>/etc/rc.d</filename>
+that look like like rc?.d where ? is the number of the runlevel and rcsysinit.d
+which contain a number of symbolic links. Some begin with a K, the others begin
+with an S, and all of them have two numbers following the initial letter. The K
+means to stop (kill) a service, and the S means to start a service. The numbers
+determine the order in which the scripts are run, from 00 to 99; the lower the
+number the sooner it gets executed. When init switches to another runlevel, the
+appropriate services get killed and others get started.</para>
 <para>The real scripts are in /etc/rc.d/init.d. They do all the work, and the

chapter08/fstab.xml

rc288d97	r90e3cb3
26	26	for example <filename>hda2</filename>, <filename>hda5</filename> and
27	27	<filename>reiserfs</filename>. For all the details on the six fields in this
28		table, see <~~userinput>man 5 fstab</userinput~~>.</para>
	28	table, see <command>man 5 fstab</command>.</para>
29	29
30	30	<para>When using a reiserfs partition, the <emphasis>1 1</emphasis> at the

chapter08/grub.xml

rc288d97	r90e3cb3
117	117	<userinput>EOF</userinput></screen>
118	118
119		<para>If <~~userinput>info grub</userinput~~> doesn't tell you all you want to
	119	<para>If <command>info grub</command> doesn't tell you all you want to
120	120	know, you can find more information regarding Grub on its website, located at:
121	121	<ulink url="http://www.gnu.org/software/grub"/>.</para>

chapter08/kernel-inst.xml

rc288d97	r90e3cb3
89	89
90	90	<para><filename>.config</filename> is the kernel configuration file that was
91		produced by the <~~userinput>make menuconfig</userinput~~> step above. It contains
	91	produced by the <command>make menuconfig</command> step above. It contains
92	92	all the config selections for the kernel that was just compiled. It's a good
93	93	idea to keep this file for future reference:</para>

Note: See TracChangeset for help on using the changeset viewer.

Context Navigation

Changeset 90e3cb3

Legend:

Download in other formats: