[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
slackware:current [2012/09/11 13:47 (UTC)] – [Overview] made a point clearer vharishankarslackware:current [2012/09/25 05:01 (UTC)] (current) – [Tracking the Current Branch] updated internal link mfillpot
Line 14: Line 14:
   - read the ChangeLog file present in ''/var/lib/slackpkg/ChangeLog.txt'' for what applications and libraries are upgraded and which new packages are included.   - read the ChangeLog file present in ''/var/lib/slackpkg/ChangeLog.txt'' for what applications and libraries are upgraded and which new packages are included.
   - upgrade to the current branch in the normal fashion. See [[slackware:slackpkg#full_system_upgrade|full system upgrade]] for more information.   - upgrade to the current branch in the normal fashion. See [[slackware:slackpkg#full_system_upgrade|full system upgrade]] for more information.
-  - keep the current branch up-to-date by following steps 3 to 5 above (you could also automate the update-checking with a [[howtos:task_scheduling|cron]] job.)+  - keep the current branch up-to-date by following steps 3 to 5 above (you could also automate the update-checking with a [[howtos:general_admin:task_scheduling|cron]] job.)
  
 <note warning>Do not track the Current branch on production systems as it is a test-bed for upcoming releases. It is recommended that you use the latest stable release with the security updates instead.</note> <note warning>Do not track the Current branch on production systems as it is a test-bed for upcoming releases. It is recommended that you use the latest stable release with the security updates instead.</note>

Trace:

slackware:current ()