SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
In short, I found slackpkg very useful during my upgrade, particularly for generating a list of non-slackware software installed on my system. It is very safe to use as long as you use the tool properly. As was previously said, read UPGRADE.TXT and CHANGES_AND_HINTS.TXT to guide you. My HowTo shows an example of this.
I had problems building nvidia drivers when I was using the huge kernel, too. It's because the nvidia drivers are building the kernel module using kernel sources and the default source package is for SMP kernel. Maybe that is the problem you are facing, but as Bruce Hill said, be more specific...
To answer your intial question, here's the latest entry in the Current change log:
Quote:
Wed May 14 17:22:14 CDT 2008
extra/slackpkg/slackpkg-2.70.4-noarch-1.tgz:
Upgraded to slackpkg 2.70.4-noarch-1. This fixes a bug where the "x86"
ARCH was not recognized in a package name, leading to the kernel-headers
package not getting properly upgraded. Thanks to Piter Punk! -
Oh guys.. I reinstalled all the box) Now I'm on 12.0 again, and pretty happy). Next time I'll be wiser, as it is said - don't touch the thing till it works)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.