Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
slackware:readmes [2014/12/22 23:27 (UTC)]
alienbob README_UEFI.TXT only exists in the 64-bit tree.
slackware:readmes [2014/12/23 23:42 (UTC)]
alienbob Fix an issue with the <note> syntax.
Line 3: Line 3:
 Did you know that a good source of information about Slackware is located right on the DVD (or the FTP server)? Did you know that a good source of information about Slackware is located right on the DVD (or the FTP server)?
  
-Lots pf people realize only later (sometimes years after starting with Slackware) that the root of the distribution tree contains several text files containing information about the distro, the layout of the DVD's content and instructions about installing and configuring the software?+Lots of people realize only later (sometimes years after starting with Slackware) that the root of the distribution tree contains several text files containing information about the distro, the layout of the DVD's content and instructions about installing and configuring the software. A shame, since they contain invaluable information for setting up a Slackware system.
  
 Let's start with a listing of these files as they appear on the Slackware 14.1 DVD: <​code>​ Let's start with a listing of these files as they appear on the Slackware 14.1 DVD: <​code>​
Line 46: Line 46:
   * [[http://​ftp.slackware.com/​pub/​slackware/​slackware-current/​CHECKSUMS.md5|CHECKSUMS.md5]]\\ MD5 message digests for the files in the distribution. To test all files, use this command: <​code>​   * [[http://​ftp.slackware.com/​pub/​slackware/​slackware-current/​CHECKSUMS.md5|CHECKSUMS.md5]]\\ MD5 message digests for the files in the distribution. To test all files, use this command: <​code>​
 tail +13 CHECKSUMS.md5 | md5sum -c --quiet - | less tail +13 CHECKSUMS.md5 | md5sum -c --quiet - | less
-</​code>​Every line that does not say "​OK"​ indicates a corrupted file.+</​code>​ Every line that does not say "​OK"​ indicates a corrupted file.
  
   * [[http://​ftp.slackware.com/​pub/​slackware/​slackware-current/​CHECKSUMS.md5.asc|CHECKSUMS.md5.asc]]\\ The GPG signature of the CHECKSUMS.md5 file (signed with the [[http://​ftp.slackware.com/​pub/​slackware/​slackware-current/​GPG-KEY|GPG key of the Slackware Linux Project]]). It allows you to verify that the checksum values in CHECKSUMS.md5 are not manipulated by malicious 3rd parties. The following command: <​code>​   * [[http://​ftp.slackware.com/​pub/​slackware/​slackware-current/​CHECKSUMS.md5.asc|CHECKSUMS.md5.asc]]\\ The GPG signature of the CHECKSUMS.md5 file (signed with the [[http://​ftp.slackware.com/​pub/​slackware/​slackware-current/​GPG-KEY|GPG key of the Slackware Linux Project]]). It allows you to verify that the checksum values in CHECKSUMS.md5 are not manipulated by malicious 3rd parties. The following command: <​code>​
Line 61: Line 61:
   * [[http://​ftp.slackware.com/​pub/​slackware/​slackware-current/​COPYRIGHT.TXT|COPYRIGHT.TXT]]\\ This is the Slackware COPYRIGHT file.  This file provides documentation about many of the licenses used by components included in Slackware, as well as some acknowledgements (some required, some freely given). Some packages will have their license file in the respective subdirectory of ''/​usr/​doc''​.   * [[http://​ftp.slackware.com/​pub/​slackware/​slackware-current/​COPYRIGHT.TXT|COPYRIGHT.TXT]]\\ This is the Slackware COPYRIGHT file.  This file provides documentation about many of the licenses used by components included in Slackware, as well as some acknowledgements (some required, some freely given). Some packages will have their license file in the respective subdirectory of ''/​usr/​doc''​.
  
-  * [[http://​ftp.slackware.com/​pub/​slackware/​slackware-current/​CRYPTO_NOTICE.TXT|CRYPTO_NOTICE.TXT]]\\ ​LEgal notice, due to U.S. Exports Regulations.+  * [[http://​ftp.slackware.com/​pub/​slackware/​slackware-current/​CRYPTO_NOTICE.TXT|CRYPTO_NOTICE.TXT]]\\ ​Legal notice, due to U.S. Exports Regulations.
  
   * [[http://​ftp.slackware.com/​pub/​slackware/​slackware-current/​ChangeLog.txt|ChangeLog.txt]]\\ The log of all updates to the release, made since the announcement of the previous release. Sort of Pat's own blog :-)   * [[http://​ftp.slackware.com/​pub/​slackware/​slackware-current/​ChangeLog.txt|ChangeLog.txt]]\\ The log of all updates to the release, made since the announcement of the previous release. Sort of Pat's own blog :-)
Line 97: Line 97:
   * [[http://​ftp.slackware.com/​pub/​slackware/​slackware-current/​Slackware-HOWTO|Slackware-HOWTO]]\\ Instructions for installing Slackware from CD/DVD. //If you're new to Slackware, start with this//.   * [[http://​ftp.slackware.com/​pub/​slackware/​slackware-current/​Slackware-HOWTO|Slackware-HOWTO]]\\ Instructions for installing Slackware from CD/DVD. //If you're new to Slackware, start with this//.
  
-  * [[http://​ftp.slackware.com/​pub/​slackware/​slackware-current/​UPGRADE.TXT|UPGRADE.TXT]]\\ Slackware Upgrade HOWTO explains how to upgrade from one stable Slackware release to the next. <note tip>You can use ''​[[slackware:​slackpkg|slackpkg]]''​ in order to largely automate this process</​note>​+  * [[http://​ftp.slackware.com/​pub/​slackware/​slackware-current/​UPGRADE.TXT|UPGRADE.TXT]]\\ Slackware Upgrade HOWTO explains how to upgrade from one stable Slackware release to the next. 
 +<note tip>You can use ''​[[slackware:​slackpkg|slackpkg]]''​ in order to largely automate this process</​note>​
  
   * [[http://​ftp.slackware.com/​pub/​slackware/​slackware-current/​isolinux/​README.TXT|isolinux/​README.TXT]]\\ How to burn a Bootable Slackware disc.   * [[http://​ftp.slackware.com/​pub/​slackware/​slackware-current/​isolinux/​README.TXT|isolinux/​README.TXT]]\\ How to burn a Bootable Slackware disc.

In Other Languages
QR Code
QR Code slackware:readmes (generated for current page)