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.
Is there a specific order to do the upgrade? Basically, I used to compile Qt, KDE, mplayer and other applications from source but I want to make use of the latest packages under Slackware current.
In one of the posts mianve suggested me to read the ChangeLog but there is no specific order for which packages to start with. In another post Keefaz suggested to upgrade glibc, gcc, coreutils and binutils.
I'd recommend that you take a look at the instructions for upgrading to SLackware 10.1 and follow the order listed there. The instructions can be found here:
ftp.slackware.com/slackware-10.1/UPGRADE.TXT
(Of course, you can use a mirror).
The advice there is similar to what Keefaz suggested - upgrade glibc related libraries first, and then pkgtools and sed if necessary - but there are additional instructions about how to boot into single-user mode for the upgrade and so on.
Basically, you'd need to begin by deciding which of the packages in current you will use (based on what you have installed, maybe all of the packages but it depends on your system) and then downloading them to your machine. Then you could follow the UPGRADE.TXT instructions.
swaret --upgade -a does it all for me.
You can get swaret from swaret.sourceforge.net, as someone suggested above. It might not be the best way but it works :P
The only caveat is that sometimes, once in a great while, you WILL run into problems using current. For instance, the "current" version of udev is know to break alsa.
I'd like to add a warning about blindly using swaret (or any other tool like it) with current. You REALLY need to read the changelogs in current because packages are put in there that WILL break your system unless you take specific action. Swaret is a decent tool, but you need to understand what it is doing and how it can cause trouble.
I have followed the instructions in UPGRADE.TXT to upgrade from 10.1 to current. I have printed the change log as well and I am planning to go through it today.
MMYoung - the udev problem is with the /testing 2.6 kernel, no problem with the 2.4.31 kernel of "current"
Basel - Swaret does not normally update the kernel, alsa is built for specific kernel versions, so you must be careful to stay in sync.
KDE seems to leave remnants of older versions around causing console error messages about mime types. It might be worth waiting a little while for 10.2 to come out and do a clean install.
One thing I have noticed after upgrading to current and also under SuSE 9.3 is that:
The crash warrning window appears when I try to shutdown or reboot my machine BUT the system goes directly to the console and display the shutdown commands. This happens in fraction of seconds and I cann't click on close or view the stacl trace of the error. Why do you think this happens?
Is there a way to revert a package to an older version?
I have just went through the change log and I should have done that earlier before the upgrade. In fact there are only few packages that I need to upgrade instead of upgrading all packages.
But I am using the shutdown button not using calling shutdown from the console as root. BTW, is it possible to get the list of messages for system shutdown and reboot?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.