Help answer threads with 0 replies.
Go Back > Blogs > ReaperX7
User Name


Rate this Entry

Proper method to update a Slackware Release to Current.

Posted 06-10-2012 at 11:41 PM by ReaperX7
Updated 07-31-2012 at 11:35 PM by ReaperX7

There are a lot of old issues about performing an upgrade from a release version of Slackware to a current one, but the process is very easy, but you need to do some preparations beforehand.

The first tool you should use is simply a web browser. Navigate to the slackware website at:

Check first in the /Slackware(64)/A and check both the latest release and current to see if these three releases have been upgraded:

if they have, navigate to your /etc/slackpkg/blacklist and comment-in (remove the #) the packages to allow them to be updated to the latest copies. If they have not been upgraded, leave them alone. Often these packages are NEVER updated. Only touch these if absolutely necessary.

Now you're ready for the next step:

Navigate to /etc/slackpkg/mirrors and comment in the Slackware(64) current HTTP/FTP server of your choice.

Personally I recommend:
Now, as the root or su (super-user) run the following command to get the latest file listings:
slackpkg update
This next command will install any new files to the system that have been added since you're last update. This command will be required each update from now on. Often these new packages are additional dependencies that need to be added.
slackpkg install-new
This command will download and upgrade all packages that have been upgraded since the last versions were released. This will probably be the majority of your upgrades from now on, and will need to be ran each time you check for upgrades.
slackpkg upgrade-all
This command is often the last used as seldomly packages are removed from the distribution and will conflict with newer versions of files. It's also good for cleaning out older SlackBuilds (SBo packages) that may have issues.
slackpkg system-clean
As the checks finish you may be asked to update your configuration files and scripts. The best solution often is to just over write the old files, unless you absolutely need to reedit your scripts.

The last and rare check that will be made is to run lilo and update your boot loader to recognize the new kernel, configuration, and modules.

After this, if all is well, reboot and everything should be perfect.

Take notice: Often this will not work for everyone, and you do risk ending up with a non-working system, but often is the best recourse to keep your system up to date and functional. Remember, always treat Current more carefully than the main release. A lot of people treat Current as a rolling release, but it's really more of a system setup for advanced users, testers, and developers, so be careful.
Posted in Uncategorized
Views 4987 Comments 1
« Prev     Main     Next »
Total Comments 1


  1. Old Comment
    My preference is to just build a whole new system on either a separate machine (testing via a KVM switch) or on a separate drive (testing via a combination of virtual machines and dual booting). Then migrate myself to the new system, and migrate all my "stuff". Eventually decommission the old system or drive and repurpose it.
    Posted 08-17-2012 at 12:38 AM by Skaperen Skaperen is offline


All times are GMT -5. The time now is 11:41 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration