mirror of
https://git.linuxfromscratch.org/lfs.git
synced 2025-01-18 21:17:38 +00:00
Removed PDF specifics tags.
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@4664 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
parent
ecac2ad77c
commit
845846e02d
@ -3,7 +3,7 @@
|
||||
<!ENTITY % general-entities SYSTEM "../general.ent">
|
||||
%general-entities;
|
||||
]>
|
||||
<sect1 id="ch-scatter-changelog" condition="html">
|
||||
<sect1 id="ch-scatter-changelog">
|
||||
<title>Changelog</title>
|
||||
<?dbhtml filename="changelog.html"?>
|
||||
|
||||
|
@ -32,8 +32,7 @@ needed to build an LFS system:</para>
|
||||
<varlistentry>
|
||||
<term>Coreutils Suppress Uptime, Kill, Su Patch - 16 KB:</term>
|
||||
<listitem>
|
||||
<para condition="html"><ulink url="&patches-root;coreutils-&coreutils-version;-suppress_uptime_kill_su-1.patch"/></para>
|
||||
<para condition="pdf"><ulink url="&patches-root;coreutils-&coreutils-version;-suppress_uptime_ kill_su-1.patch"/></para>
|
||||
<para><ulink url="&patches-root;coreutils-&coreutils-version;-suppress_uptime_kill_su-1.patch"/></para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
@ -82,24 +81,21 @@ needed to build an LFS system:</para>
|
||||
<varlistentry>
|
||||
<term>Inetutils Kernel Headers Patch - 1 KB:</term>
|
||||
<listitem>
|
||||
<para condition="html"><ulink url="&patches-root;inetutils-&inetutils-version;-kernel_headers-1.patch"/></para>
|
||||
<para condition="pdf"><ulink url="&patches-root;inetutils-&inetutils-version;-kernel_headers- 1.patch"/></para>
|
||||
<para><ulink url="&patches-root;inetutils-&inetutils-version;-kernel_headers-1.patch"/></para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>Inetutils No-Server-Man-Pages Patch - 4 KB:</term>
|
||||
<listitem>
|
||||
<para condition="html"><ulink url="&patches-root;inetutils-&inetutils-version;-no_server_man_pages-1.patch"/></para>
|
||||
<para condition="pdf"><ulink url="&patches-root;inetutils-&inetutils-version;-no_server_man_ pages-1.patch"/></para>
|
||||
<para><ulink url="&patches-root;inetutils-&inetutils-version;-no_server_man_pages-1.patch"/></para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>IPRoute2 Disable DB Patch - 1 KB:</term>
|
||||
<listitem>
|
||||
<para condition="html"><ulink url="&patches-root;iproute2-&iproute2-patch-version;-remove_db-1.patch"/></para>
|
||||
<para condition="pdf"><ulink url="&patches-root;iproute2-&iproute2-patch-version;-remove_ db-1.patch"/></para>
|
||||
<para><ulink url="&patches-root;iproute2-&iproute2-patch-version;-remove_db-1.patch"/></para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
|
@ -42,8 +42,8 @@ sed 's@ /lib/ld-linux.so.2@ /tools/lib/ld-linux.so.2@g' \
|
||||
mv -f tempspecfile $SPECFILE &&
|
||||
unset SPECFILE</userinput></screen>
|
||||
|
||||
<para><phrase condition="html">It is recommended that the above
|
||||
command be copy-and-pasted in order to ensure accuracy.</phrase>
|
||||
<para>It is recommended that the above
|
||||
command be copy-and-pasted in order to ensure accuracy.
|
||||
Alternatively, the specs file can be edited by hand. This is done by
|
||||
replacing every occurrence of <quote>/lib/ld-linux.so.2</quote> with
|
||||
<quote>/tools/lib/ld-linux.so.2</quote></para>
|
||||
@ -100,8 +100,8 @@ the <envar>PATH</envar> is wrong it could mean that you are not logged in as use
|
||||
<emphasis>lfs</emphasis> or that something went wrong back in <xref
|
||||
linkend="ch-tools-settingenviron" role="."/> Another option is that something
|
||||
may have gone wrong with the specs file amendment above. In this case,
|
||||
redo the specs file amendment<phrase condition="html">, being careful to copy-and-paste the
|
||||
commands</phrase>.</para>
|
||||
redo the specs file amendment, being careful to copy-and-paste the
|
||||
commands.</para>
|
||||
|
||||
<para>Once all is well, clean up the test files:</para>
|
||||
|
||||
|
@ -44,8 +44,7 @@ five.</para>
|
||||
software, a lot of disk space can be regained by removing these
|
||||
symbols. The next section shows how to strip all debugging symbols
|
||||
from the programs and libraries. Additional information on system
|
||||
optimization can be found at <ulink url="&hints-root;optimization.txt"><phrase
|
||||
condition="pdf">&hints-root; optimization.txt</phrase></ulink>.</para>
|
||||
optimization can be found at <ulink url="&hints-root;optimization.txt"/>.</para>
|
||||
|
||||
</sect1>
|
||||
|
||||
|
@ -69,11 +69,8 @@ cd ../binutils-build</userinput></screen>
|
||||
<para>Normally, the tooldir (the directory where the executables will
|
||||
ultimately be located) is set to <filename
|
||||
class="directory">$(exec_prefix)/$(target_alias)</filename>, which
|
||||
expands into <phrase condition="html"><filename
|
||||
class="directory">/usr/i686-pc-linux-gnu</filename></phrase><phrase
|
||||
condition="pdf"><filename class="directory">/usr/i686-pc-
|
||||
linux-gnu</filename></phrase>. Because this is a custom system, this
|
||||
target-specific directory in <filename
|
||||
expands into <filename class="directory">/usr/i686-pc-linux-gnu</filename>.
|
||||
Because this is a custom system, this target-specific directory in <filename
|
||||
class="directory">/usr</filename> is not required. This setup would be
|
||||
used if the system was used to cross-compile (for example, compiling a
|
||||
package on an Intel machine that generates code that can be executed
|
||||
|
@ -78,9 +78,8 @@ Instructions for a better <command>whois</command> client are in the BLFS book.<
|
||||
servers included as part of the Inetutils package. These servers are
|
||||
deemed not appropriate in a basic LFS system. Some are insecure by
|
||||
nature and are only considered safe on trusted networks. More
|
||||
information can be found at <phrase condition="html"><ulink
|
||||
url="&blfs-root;view/svn/basicnet/inetutils.html"/></phrase><phrase
|
||||
condition="pdf"><ulink url="&blfs-root;view/svn/ basicnet/inetutils.html"/></phrase>. Note that
|
||||
information can be found at <ulink
|
||||
url="&blfs-root;view/svn/basicnet/inetutils.html"/>. Note that
|
||||
better replacements are available for many of these
|
||||
servers.</para></listitem>
|
||||
</varlistentry>
|
||||
|
@ -99,9 +99,7 @@ not support multibyte character sets.</para>
|
||||
|
||||
<para>Additional information with regards to the compression of
|
||||
man and info pages can be found in the BLFS book at
|
||||
<ulink url="&blfs-root;view/cvs/postlfs/compressdoc.html"><phrase
|
||||
condition="pdf">http://www.linuxfromscratch.org/blfs/view/cvs/postlfs/
|
||||
compressdoc.html</phrase></ulink>.</para>
|
||||
<ulink url="&blfs-root;view/cvs/postlfs/compressdoc.html"/>.</para>
|
||||
|
||||
</sect2>
|
||||
|
||||
|
@ -226,18 +226,14 @@ modules when any request is made to load the driver
|
||||
sites:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem><para remap="verbatim">A Userspace Implementation of devfs
|
||||
<ulink url="http://www.kroah.com/linux/talks/ols_2003_udev_paper/Reprint-Kroah-Hartman-OLS2003.pdf"><phrase
|
||||
condition="pdf">http://www.kroah.com/linux/talks/ols_2003_udev_paper/
|
||||
Reprint-Kroah-Hartman-OLS2003.pdf</phrase></ulink></para></listitem>
|
||||
<listitem><para>A Userspace Implementation of devfs
|
||||
<ulink url="http://www.kroah.com/linux/talks/ols_2003_udev_paper/Reprint-Kroah-Hartman-OLS2003.pdf"/></para></listitem>
|
||||
|
||||
<listitem><para remap="verbatim">udev FAQ
|
||||
<listitem><para>udev FAQ
|
||||
<ulink url="http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev-FAQ"/></para></listitem>
|
||||
|
||||
<listitem><para remap="verbatim">The Linux Kernel Driver Model
|
||||
<ulink url="http://public.planetmirror.com/pub/lca/2003/proceedings/papers/Patrick_Mochel/Patrick_Mochel.pdf"><phrase
|
||||
condition="pdf">http://public.planetmirror.com/pub/lca/2003/proceedings/papers/
|
||||
Patrick_Mochel/Patrick_Mochel.pdf</phrase></ulink></para></listitem>
|
||||
<listitem><para>The Linux Kernel Driver Model
|
||||
<ulink url="http://public.planetmirror.com/pub/lca/2003/proceedings/papers/Patrick_Mochel/Patrick_Mochel.pdf"/></para></listitem>
|
||||
</itemizedlist>
|
||||
</sect2>
|
||||
|
||||
|
@ -56,10 +56,7 @@ compile the keymap into the kernel, issue the command below:</para>
|
||||
drivers/char/defkeymap.c</userinput></screen>
|
||||
|
||||
<para>For example, if using a Dutch keyboard, use
|
||||
<phrase
|
||||
condition="html"><filename>/usr/share/kbd/keymaps/i386/qwerty/nl.map.gz</filename></phrase><phrase
|
||||
condition="pdf"><filename>/usr/share/kbd/keymaps/i386/
|
||||
qwerty/nl.map.gz</filename></phrase>.</para>
|
||||
<filename>/usr/share/kbd/keymaps/i386/qwerty/nl.map.gz</filename>.</para>
|
||||
|
||||
<para>Configure the kernel via a menu-driven interface BLFS has some
|
||||
information regarding particular kernel configuration requirements of
|
||||
|
@ -12,18 +12,18 @@ and installing Linux software. Before building an LFS system, we
|
||||
recommend reading the following HOWTOs:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem><para remap="verbatim">Software-Building-HOWTO
|
||||
<listitem><para>Software-Building-HOWTO
|
||||
<ulink url="http://www.tldp.org/HOWTO/Software-Building-HOWTO.html"/></para>
|
||||
|
||||
<para>This is a comprehensive guide to building and installing
|
||||
<quote>generic</quote> Unix software distributions under Linux.</para></listitem>
|
||||
|
||||
<listitem><para remap="verbatim">The Linux Users' Guide
|
||||
<listitem><para>The Linux Users' Guide
|
||||
<ulink url="http://espc22.murdoch.edu.au/~stewart/guide/guide.html"/></para>
|
||||
|
||||
<para>This guide covers the usage of assorted Linux software.</para></listitem>
|
||||
|
||||
<listitem><para remap="verbatim">The Essential Pre-Reading Hint
|
||||
<listitem><para>The Essential Pre-Reading Hint
|
||||
<ulink url="&hints-root;essential_prereading.txt"/></para>
|
||||
|
||||
<para>This is an LFS Hint written specifically for users new to Linux.
|
||||
|
@ -52,7 +52,7 @@ Therefore, this entire section is generally typed as seen.</para>
|
||||
<para><replaceable>[REPLACED TEXT]</replaceable></para>
|
||||
|
||||
<para>This format is used to encapsulate text that is not to be typed
|
||||
as seen<phrase condition="html"> or copy-and-pasted</phrase>.</para>
|
||||
as seen or copy-and-pasted.</para>
|
||||
|
||||
</sect1>
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user