Changeset cbadf6b for introduction/important
- Timestamp:
- 07/21/2005 11:12:09 PM (19 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 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, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- 443eee56
- Parents:
- 4382a36
- File:
-
- 1 edited
-
introduction/important/unpacking.xml (modified) (8 diffs)
Legend:
- Unmodified
- Added
- Removed
-
introduction/important/unpacking.xml
r4382a36 rcbadf6b 23 23 <para>Each set of installation instructions contains a URL from which you 24 24 can download the package. We do however keep a selection of patches 25 available via http. These are referenced as needed in the installation25 available via HTTP. These are referenced as needed in the installation 26 26 instructions.</para> 27 27 … … 34 34 you have had an error, it's usually best to delete the source tree and 35 35 re-unpack it <emphasis>before</emphasis> trying again. This obviously 36 doesn't apply if you're an advanced user used to hacking Makefiles and C 37 code, but if in doubt, start from a clean tree.</para> 36 doesn't apply if you're an advanced user used to hacking 37 <filename>Makefile</filename>s and C code, but if in doubt, start from a 38 clean tree.</para> 38 39 39 40 <sect2> … … 41 42 42 43 <para>The golden rule of Unix System Administration is to use your 43 superpowers only when neccessary. Hence, BLFS recommends that you 44 build software as an unprivileged user and only "become root" 45 when installing the software. This philosophy is followed in all the 46 packages in this book. Unless otherwise specified, all instructions 47 should be executed as an unprivileged user. The book will advise you 48 on instructions that need root privileges.</para> 44 superpowers only when neccessary. Hence, BLFS recommends that you 45 build software as an unprivileged user and only become the 46 <systemitem class='username'>root</systemitem> user when installing the 47 software. This philosophy is followed in all the packages in this book. 48 Unless otherwise specified, all instructions should be executed as an 49 unprivileged user. The book will advise you on instructions that need 50 <systemitem class='username'>root</systemitem> privileges.</para> 49 51 50 52 </sect2> … … 53 55 <title>Unpacking the Software</title> 54 56 55 <para>If a file is tar'ed and compressed, it is unpacked by running one of 56 the following commands:</para> 57 <para>If a file is in <filename class='extension'>.tar</filename> format 58 and compressed, it is unpacked by running one of the following 59 commands:</para> 57 60 58 <screen><userinput>tar -xvzf filename.tar.gz 59 tar -xvzf filename.tgz 60 tar -xvzf filename.tar.Z 61 tar -xvjf filename.tar.bz2</userinput></screen> 61 <screen><userinput>tar -xvf filename.tar.gz 62 tar -xvf filename.tgz 63 tar -xvf filename.tar.Z 64 tar -xvf filename.tar.bz2</userinput></screen> 65 66 <note> 67 <para>You may omit using the <option>v</option> parameter in the commands 68 shown above and below if you wish to suppress the verbose listing of all 69 the files in the archive as they are extracted. This can help speed up the 70 extraction as well as make any errors produced during the extraction 71 more obvious to you.</para> 72 </note> 62 73 63 74 <para>You can also use a slightly different method:</para> … … 66 77 67 78 <para>Finally, you sometimes need to be able to unpack patches which are 68 generally not tar'ed. The best way to do this is to copy the patch file to 69 <filename>/usr/src</filename> and then to run one of the following commands 70 depending on whether the file is <filename>.gz</filename> or 71 <filename>.bz2</filename>:</para> 79 generally not in <filename class='extension'>.tar</filename> format. The 80 best way to do this is to copy the patch file to 81 <filename class='directory'>/usr/src</filename> and then run one of the 82 following commands depending on whether the file is a 83 <filename class='extension'>.gz</filename> or 84 <filename class='extension'>.bz2</filename> file:</para> 72 85 73 86 <screen><userinput>gunzip -v patchname.gz … … 80 93 81 94 <para>Generally, to verify that the downloaded file is genuine and complete, 82 m ost package maintainers also distribute md5sums of the files.83 To verify themd5sum of the downloaded files, download both the file and the95 many package maintainers also distribute md5sums of the files. To verify the 96 md5sum of the downloaded files, download both the file and the 84 97 corresponding md5sum file to the same directory (preferably from different 85 on-line locations), and (assuming file.md5sum is the md5sum file downloaded)86 run the following command:</para>98 on-line locations), and (assuming <filename>file.md5sum</filename> is the 99 md5sum file downloaded) run the following command:</para> 87 100 88 101 <screen><userinput>md5sum -c file.md5sum</userinput></screen> 89 102 90 <para>If there are any errors, they will be reported.</para> 103 <para>If there are any errors, they will be reported. Note that the BLFS 104 book includes md5sums for all the source files also. To use the BLFS 105 supplied md5sums, you can create a <filename>file.md5sum</filename> (place 106 the md5sum data and the exact name of the downloaded file on the same 107 line of a file, separated by white space) and run the command shown above. 108 Alternately, simply run the command shown below and compare the output 109 to the md5sum data shown in the BLFS book.</para> 110 111 <screen><userinput>md5sum <replaceable>[name_of_downloaded_file]</replaceable></userinput></screen> 91 112 92 113 </sect2> … … 96 117 97 118 <para>For larger packages, it is convenient to create log files instead of 98 staring at the screen hoping to catch a particular error or warning. Log files99 are also useful for debugging and keeping records. The following command100 allows you to create an installation log. Replace <command> with the101 command you intend to execute.</para>119 staring at the screen hoping to catch a particular error or warning. Log 120 files are also useful for debugging and keeping records. The following 121 command allows you to create an installation log. Replace 122 <replaceable>[command]</replaceable> with the command you intend to execute.</para> 102 123 103 <screen><userinput>( <command>2>&1 | tee compile.log && exit $PIPESTATUS )</userinput></screen>124 <screen><userinput>( <replaceable>[command]</replaceable> 2>&1 | tee compile.log && exit $PIPESTATUS )</userinput></screen> 104 125 105 126 <para><option>2>&1</option> redirects error messages to the same … … 107 128 viewing of the output while logging the results to a file. The parentheses 108 129 around the command run the entire command in a subshell and finally the 109 <command>exit $PIPESTATUS</command> ensures the result of the110 <command> is returned as the result and not the result ofthe111 <command>tee</command> command.</para>130 <command>exit $PIPESTATUS</command> command ensures the result of the 131 <replaceable>[command]</replaceable> is returned as the result and not the 132 result of the <command>tee</command> command.</para> 112 133 113 134 </sect2>
Note:
See TracChangeset
for help on using the changeset viewer.
