SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I am writing out this very quick procedure on how to update Slackware because I've seen far too many people in this forum blindly update using tools like swaret and slapt-get and getting bit in the ass for it with broken software. This is for tracking development in -current. Because only security fixes are applied to stable releases, it is perfectly fine to blindly update with swaret or slapt-get if you don't run -current.
Here is the procedure I use to update to -current:
1) Check the ChangeLog on Slackware.com. Note any packages removed, retired to /pasture, renamed, or added. Also a good place for the latest news on future plans for the distribution including releases, etc.
2) Use an automatic package management tool to upgrade packages on your system. Slackpkg, swaret, slapt-get....it's your choice. Or manually download the packages and use upgradepkg.
3) Run removepkg on any removed/retired packages.
4) Use an automatic package management tool to install any new packages that you want, or manually download and install them. Note that sometimes libraries necessary for some of your upgraded software to run will be added. If anything is added to /l, you're probably better off installing it just in case. Similarly, the same is true for anything added to /gnome if you use GNOME.
5) cd /etc && find . -name "*.new" and merge in any appropriate changes.
6) Test things out to make sure it all works.
If you have any comments, suggestions, or additions, feel free to add them!
Most of the problems I've seen with updates on this forums could have been avoided had this procedure been followed.
Excellent advice. That's pretty much what I do, and I've never had any problems.
Remember people, swaret and its ilk can be great timesaving tools, but they can't be relied on to do everything for you. They will not automatically detect any new or renamed packages, and they will not remove retired packages. Always read the changelog before updating.