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 found the upgrade.txt but it's talking about this : Slackware 13.1 to 13.37 Upgrade HOWTO <email@example.com>
So not talking about 13.37 to current.
Can I then take the same steps as described in the upgrade.txt
There is no official documentation for "upgradeing" to slackware-current, since that is the development tree. By installing/upgrading to slackware-current you implicitly accept that you are a Slackware "beta tester". If you need your computer for daily production use, think twice about upgradeing to slackware-current unless you are confident enough that you can cope with any issues that may arise at any point when a buggy package gets added.
Having said that, using slackpkg for this upgrade is a fairly painless and straight-forward process even for the move 13.37 -> current.
So I have to work with a old KDE and stay stable or choose for a new KDE and accept that my box which I want to use daily is unstable.
Difficult choice then.
It will not necessarily be unstable (Slackware's development tree is usually more stable than other distro's stable releases...). I have slackware-current plus KDE 4.7.1 on the laptop I use many hours a day without big issues. But my server is equipped with Slackware 13.37 because I want a server to run a well-tested OS.
Or can i better take the steps in the upgrade.txt ?
Keeping UPGRADE.TXT as a reference is always good. Also, check CHANGES_AND_HINTS.TXT for every issue you might encounter after the upgrade - perhaps your issue is covered there.
Between 13.37 and -current, the kernel was updated. You do best by using "installpkg" to install the new packages for kernel-firmware, kernel-modules*, kernel-huge* and kernel-generic* . You use "upgradepkg" to upgrade the kernel-source and kernel-headers packages. Add the new kernel to "/etc/lilo.conf" without removing the old kernel, so that you can test it first. When the new kernel boots fine, you can remove the old kernel packages and also remove the old kernel lines from "/etc/lilo.conf". Do not forget to run "lilo" every time you have edited "/etc/lilo.conf" !
About your slackpkg command sequence, it is almost correct. First, open "/etc/slackpkg/mirrors" in an editor and un-comment exactly ONE mirror URL, for slackware-current in the ARCH version that you are running (either 32-bit or 64-bit). Then run:
That final command will present a list of applications that are not or no longer part of Slackware. Read through that list very carefully, and DE-SELECT all the packages that you do not want to lose. When you click "OK", slackpkg will remove all the packages that are still checked in that list.
You have to upgrade that kernel (more precise, you have to install the new kernel packages in parallel to the running kernel), make sure that lilo has been updated with the new kernel configuration and you can use slackpkg to upgrade all the rest of Slackware. The order in which you o this is not important. At the end you reboot, and should then be running slackware-current.