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.
View Poll Results: How are people keeping Slackware up to date
I voted Slackware Mirror but I seldom do updates between new releases. When I do, I prefer to download the updated packages and run upgradepkg myself.
I do something similar, but I do updates a little bit more, especially after last big update, when I elected to download the ISO of slackware64-current, and found that the proprietary AMD graphics drivers do not play well with x-server version 14. When I went back to the release of Slackware 14, and upgraded from there, it worked much better.
When a new release of Slackware is published, and early adopters have pounded on it for a while and Pat + friends have applied a few bugfixes, I assess its new capabilities and my current requirements, and decide whether it makes sense to upgrade.
If so, I choose a noncritical machine, put in a new disk, and make a fresh install of the new release. I mount the old disk to copy over its data, label it with the date, package it, and put it in a drawer as a backup (to be wiped and re-used later if the backup is not needed).
The new machine is stress-tested for a few months, to reveal any problems. I try to hit it with all of my use-cases.
If it passes the stress-test, I upgrade some or all of my other machines as well. If it does not, I may keep the new Slackware on that machine or revert it to the older version, which is known to work. Most of the time this is just a matter of pulling the old disk out of the drawer and putting it back in the machine.