Add a paragraph in Chapter 3.1 about obtaining and using md5sums

for the packages in the book.


git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@9624 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Bruce Dubbs 2011-10-10 17:56:39 +00:00
parent a7f0b27405
commit 74296e21af
3 changed files with 23 additions and 4 deletions

View File

@ -36,6 +36,16 @@
</listitem>
-->
<listitem>
<para>2011-10-10</para>
<itemizedlist>
<listitem>
<para>[bdubbs] - Add a paragraph in Chapter 3.1 about obtaining and
using md5sums for the packages in the book.</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>2011-10-08</para>
<itemizedlist>

View File

@ -24,7 +24,7 @@
url="http://www.google.com/"/>) provides a useful search engine for
most packages. If this search is unsuccessful, try one of the
alternative means of downloading discussed at <ulink
url="&lfs-root;lfs/packages.html#packages"/>.</para>
url="&lfs-root;lfs/packages.html#packages"/>. </para>
<para>Downloaded packages and patches will need to be stored somewhere
that is conveniently available throughout the entire build. A working
@ -53,6 +53,15 @@
<ulink url="../wget-list">wget-list</ulink> as an input to
<command>wget</command>. For example:</para>
<screen role="nodump"><userinput>wget -i wget-list -P $LFS/sources</userinput></screen>
<screen role="nodump"><userinput>wget -i wget-list -P $LFS/sources</userinput></screen>
<para>Additionally, starting with LFS-7.0, there is a separate file,
<ulink url="../md5sums">md5sums</ulink>, can be used to verify that all
the correct packages are available before proceeding. Place that file in
<filename class="directory">$LFS/sources</filename> and run:</para>
<screen role="nodump"><userinput>pushd $LFS/sources
md5sum -c md5sums
popd</userinput></screen>
</sect1>

View File

@ -1,5 +1,5 @@
<!ENTITY version "SVN-20111008">
<!ENTITY releasedate "Oct 8, 2011">
<!ENTITY version "SVN-20111010">
<!ENTITY releasedate "Oct 10, 2011">
<!ENTITY copyrightdate "1999-2011"><!-- jhalfs needs a literal dash, not &ndash; -->
<!ENTITY milestone "7.0">
<!ENTITY generic-version "development"> <!-- Use "development", "testing", or "x.y[-pre{x}]" -->