Context Navigation

rbb0d842b	raa15d3e
17	17	<para>The blfs-bootscripts package will be used throughout the <acronym>BLFS</acronym>
18	18	book for startup scripts. Unlike <acronym>LFS</acronym>, each init script
19		has a seperate install target in the blfs-bootscripts package.
	19	has a separate install target in the blfs-bootscripts package.
20	20	It is recomended you keep the package
21	21	source directory around until completion of your

introduction/important/patches.xml

-              rbb0d842b
+              raa15d3e
 </itemizedlist>
 <para>In short, the book only includes patches that are either Required or
 Recommended. There is a <ulink url="http://www.linuxfromscratch.org/patches">Patches subproject</ulink>
 which hosts various patches (including the patches included in the books)
+<para>In short, the book only includes patches that are either required or
+recommended. There is a <ulink url="http://www.linuxfromscratch.org/patches">Patches subproject</ulink>
+which hosts various patches (including the patches referenced in the books)
 to enable you to configure your <acronym>LFS</acronym> the way you like it.</para>

-              rbb0d842b
+              raa15d3e
 mentioned in <xref linkend="intro-important-beyond"/> need to be expanded to
 include <filename>/usr/pkg/foo</filename>. For more than a few packages,
 this scheme becomes unmanagable.</para>
+this scheme becomes unmanageable.</para>
 </sect3>
 …
 to expand the environment variables. Though the symlinks can be created by the user,
 to automate the creation, many package managers have been written on this approach.
 Few of the popular ones are Stow, Epkg, Graft, and Depot.</para>
+A few of the popular ones are Stow, Epkg, Graft, and Depot.</para>
 <para>The installation needs to be faked, so that the package thinks that it is
 installed in <filename>/usr</filename> though in reality it is installed in
 <filename>/ust/pkg</filename> hierarchy. Installing in this manner is not usually a trivial
+installed in <filename class="directory">/usr</filename> though in reality it is installed in
+<filename class="directory">/usr/pkg</filename> hierarchy. Installing in this manner is not usually a trivial
 task. For example, consider that you are installing a package libfoo-1.1. The following
 instructions may not install the package properly:</para>

-              rbb0d842b
+              raa15d3e
 staring at the screen hoping to catch a particular error or warning. Log files
 are also useful for debugging and keeping records. The following command
 allows you to create a installation log. Replace &lt;command&gt; with the
+allows you to create an installation log. Replace &lt;command&gt; with the
 command you intend to execute.</para>
 …
 <para><parameter>2&gt;&amp;1</parameter> redirects error messages
 to the same location as normal output. The <command>tee</command> command
+to the same location as standard output. The <command>tee</command> command
 allows viewing of the output while logging the results to a file. The parentheses
 around the command run the entire command in a subshell and finally the

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