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.
Because I'm not experienced, let me ask some questions:
I have two pcs with slackware:
1 PC with slackware 13 -current
1 PC with slackware64 -current
Is it now the right way to point the mirrors to the stable directory and then to run slackpgk update | install-new | upgrade? Do I have then the same results as if I would install totally new from the new ISO's?
I would prefer this way because I have some customized apps installed which are blown away with a new installation...
Sorry to hijack the thread...
I havent been following - current. Just the 12.2 stable. I've spent ages getting slack 12.2 working, and i'm nearly there thanks to the help of some very nice people on this forum.
Does this mean i have to "start again" to get 13 working?? No offence, but the term "p1ssing into the wind" springs to mind
(I am gonna stick with slack though. It's ace.)
Cheers,
mute
mutexe, you don't have to abandon 12.2. It's not like ubuntu where the old version is instantly unsupported. Pat tends to support old versions for quite a time.
You'll find that the 'pissing into the wind' isn't as bad as you might expect. What takes you hours first time through you'll do in minutes (or even seconds once you've got the hang of it).
If you spent ages to get Slackware 12.2 working for you, I guess you have learned some valuable lessons that will come handy if/when you upgrade to 13.0. So don't be too afraid and as you said timely help is available in this forum.
First thing first, you have to decide if you want to upgrade your existing Slackware 12.2 into 13.0 or make a clean install of 13.0 in another partition or another computer (if you have one). I strongly suggest to make a clean install of 13.0 and keep your existing 12.2. If you are using KDE, the switch to KDE4 may be tricky as some functionalities in KDE4 are not yet at the level they were in KDE3 (I guess it's a personal thing to appreciate).
Then make sure to read the following files available at the root directory of installation DVD or first CD:
You will find useful information about changes from 12.2 and so you can estimate impact on what you'll need to fine-tune after the initial installation (ex: Xorg may require alternate intel drivers if you are using such a driver).
Cheers guys.
I think I'll make a new partition next to my existing 12.2. I use xfce so I dont I'm not too worried about the KDE stuff. I'm glad 12.2 won't be abandoned, that's the 2nd reason I dislike ubuntu (the first being i'm learning bugger all linux using ubuntu).
If you do want to just keep running Slack 12.2 you can do that as well. Patrick supports the distros for a long time.
Recently there was a security update for curl, and he posted updates clear back to Slack 9.1 which was released in 2003, so you definitely have LTS (to borrow from Ubuntu, Long Term Support) with Slackware.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.