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.
KDE 3.5.2 was recently added to Slack-Current, and upon upgrading, I found myself with a non-functional KDE. When trying to startx, I was getting an error (something to the effect of "kdeinit failed to start" or somesuch).
Did you upgrade your entire system to -current?
Both of those apps are in -current since Feb. 28
Tue Feb 28 20:50:44 CST 2006
a/bash-3.1-i486-3.tgz: Patched with additional official patches
bash31-008 through bash31-011.
a/util-linux-2.12r-i486-1.tgz: Upgraded to util-linux-2.12r.
a/xfsprogs-2.7.11-i486-1.tgz: Upgraded to xfsprogs-2.7.11.
Split acl, attr, dmapi, and xfsdump into separate packages and
moved them into the AP series. This location was a bit of a judgement
call since acl, attr, and dmapi contain libraries, but so do some other
packages outside L. Anyway, it does seem to me that xfsdump should go
in AP, and that these packages should all be found in the same place.
ap/acl-2.2.34-i486-1.tgz: Upgraded to acl-2.2.34, split out of xfsprogs
ap/attr-2.4.28-i486-1.tgz: Upgraded to attr-2.4.28, split out of xfsprogs
You need to check the ChangeLog before you upgrade less than everything.
The cmplete picture: upgrading packages is not all there is to it... you need to scan the ChangeLog.txt for new packages too. You'll find that only with official Slackware releases it is enough to "upgrade packages", because after an official release no new packages will be added, only patched packages to fix bugs will be released.
Other packages that were added in slackware-current and thus do not become available using "upgradepkg" or tools like swaret and slapt-get if you let them "upgrade" your computer (from the top of my mind, there can be more that I forget):
I have to agree with Alien Bob.
New dependencies may surprise you only in Slackware-current(ie. testing/development branch). Upgrading only is safe just for releases. So use Current when you know what you are doing, wish to help with testing and don't use it on production boxes.