[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

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 revisionPrevious revision
Next revisionBoth sides next revision
slackbook:tracking_updates [2012/09/12 21:25 (UTC)] – [Sources] sycamorexslackbook:tracking_updates [2012/09/17 03:17 (UTC)] – [The -stable Branch] Added original text and formatting mfillpot
Line 4: Line 4:
 ===== The -stable Branch ===== ===== The -stable Branch =====
  
-After a new version of Slackware is released, the Slackware team will, as needed, release updated packages to fix serious security vulnerabilities and particularly nasty bugs. Therefore, it's important to keep up with all of the patches for your version of Slackware, which is referred to as the -stable branch. There is also a -current branch, which is where we do our development work toward the next stable release (and as such, there are often intrusive changes there), but unless you're willing to work with a possibly broken system and are able to fix things on your own, we strongly recommend that you stick with the -stable branch.+After a new version of Slackware is released, the Slackware team will, 
 +as needed, release updated packages to fix serious security 
 +vulnerabilities and particularly nasty bugs.  Therefore, it's 
 +important to keep up with all of the patches for your version of 
 +Slackware, which is referred to as the **-stable** 
 +branch.  There is also a **-current** branch, which 
 +is where we do our development work toward the next stable release 
 +(and as such, there are often intrusive changes there), but unless 
 +you're willing to work with a possibly broken system and are able to 
 +fix things on your own, we strongly recommend that you stick with the 
 +-stable branch.
  
-Since -stable updates aren't distributed on the disks, you'll need to obtain them from the Internet. Many people and organizations offer mirrors from which you can download the entire Slackware tree (or only the patches/ directory) in any number of ways. While some mirrors offer web access, the most common ways of obtaining updates are via ftp and/or rsync servers. The Slackware project maintains a small list (organized by country) of known mirrors. If you're unsure which mirror to use, simply consult [[http://www.slackware.com/getslack/]] for suggestions. If you have a major university near you, there's a good chance that they offer a mirror of numerous open source projects, and Slackware may be among them. The only real requirement for a mirror is that it be complete; usually it's best to use a mirror near where you live in order to achieve the fastest transfer times and use the least amount of Internet resources. 
  
-So how do you know when there are updates? The best way is to consult the ChangeLog.txt on any up-to-date mirror. You can always find the latest changelogs for the -current and most recent -stable branch on the Slackware Project's web page, but if you're running an older version of Slackware, you'll need to check a mirror.+Since -stable updates aren't distributed on the disks, you'll need to 
 +obtain them from the Internet.  Many people and organizations offer 
 +mirrors from which you can download the entire Slackware tree (or only 
 +the ''patches/'' directory) in any number of 
 +ways.  While some mirrors offer web access, the most common ways of 
 +obtaining updates are via ftp and/or rsync servers.  The Slackware 
 +project maintains a small list (organized by country) of known 
 +mirrors.  If you're unsure which mirror to use, simply consult [[ 
 +http://www.slackware.com/getslack/|http://www.slackware.com/getslack/]] 
 +for suggestions.  If you have a major university near you, there's a 
 +good chance that they offer a mirror of numerous open source projects, 
 +and Slackware may be among them.  The only real requirement for a 
 +mirror is that it be complete; usually it's best to use a mirror near 
 +where you live in order to achieve the fastest transfer times and use 
 +the least amount of Internet resources. 
 + 
 +So how do you know when there are updates?  The best way is to consult the  
 +''ChangeLog.txt'' on any up-to-date mirror.  You can always  
 +find the latest changelogs for the -current and most recent -stable  
 +branch on the Slackware Project's web page, but if you're running an older  
 +version of Slackware, you'll need to check a mirror. 
  
 <code> <code>
Line 23: Line 53:
   Remove mention of HAL in the initial welcome email (mention udisks2   Remove mention of HAL in the initial welcome email (mention udisks2
   instead).  Thanks to Dave Margell.   instead).  Thanks to Dave Margell.
-a/bash-4.2.037-x86_64-1.txz:  Upgraded. +a/bash-4.2.037-x86_64-1.txz:  Upgraded.</code>
-</code> +
 ===== Security Update Mailing List ===== ===== Security Update Mailing List =====
  

Trace:

slackbook:tracking_updates ()