Changeset 0c603671 for introduction/important/unpacking.xml

Timestamp:

02/20/2004 05:16:24 AM (20 years ago)

Author:

Tushar Teredesai <tushar@…>

Branches:

10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 6.0, 6.1, 6.2, 6.2.0, 6.2.0-rc1, 6.2.0-rc2, 6.3, 6.3-rc1, 6.3-rc2, 6.3-rc3, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, v5_1, v5_1-pre1, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal

Children:

6387eb8

Parents:

7e4be43

Message:

Moved md5sum verification and log creation from xfree86 section to the introduction

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@1827 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:

• introduction/important/unpacking.xml (modified) (2 diffs)

introduction/important/unpacking.xml

@@ -1 +1 @@
 <sect1 id="intro-important-unpacking">
 <?dbhtml filename="unpacking.html" dir="introduction"?>
-<title>Getting and unpacking the software</title>
+<title>Notes on downloading, unpacking and compiling software</title>
 
 <para>Those people who have built a <acronym>LFS</acronym> system will be aware 
@@ -53 +53 @@
 </sect2>
 
+<sect2>
+<title>Verifying file integrity using md5sum</title>
+
+<para>Generally, to verify that the downloaded file is genuine and complete,
+most package maintainers also distribute md5sums of the files.
+To verify the md5sum of the downloaded files, download both the file and the
+corresponding md5sum file to the same directory (preferably from different
+on-line locations), and (assuming file.md5sum is the md5sum file downloaded)
+run the following command:</para>
+
+<screen><command>md5sum -c file.md5sum</command></screen>
+
+<para>If there are any errors, they will be reported.</para>
+
+</sect2>
+
+<sect2>
+<title>Creating Log files during installation</title>
+
+<para>For larger packages, it is convenient to create log files instead of
+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
+command you intend to execute.</para>
+
+<screen><command>( &lt;command&gt; 2&gt;&amp;1 | tee compile.log &amp;&amp; exit $PIPESTATUS )</command></screen>
+
+<para><parameter>2&gt;&amp;1</parameter> redirects error messages
+to the same location as normal 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
+<command>exit $PIPESTATUS</command> ensures the result of the &lt;command&gt;
+is returned as the result and not the result of the <command>tee</command> command.</para>
+
+</sect2>
+
 </sect1>