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.
I've been running the stable version of Slackware 10.0 and 10.1 and I am thinking of trying to follow -current as of 10.2.
So far, I have no specific plan except that I want to follow the changelogs on a weekly basis and install the packages manually without any automatic tool. Of course I know that -current can break things and I guess that Pat appreciates feedback in that case.
I also have one concern - not to have security updates in time.
And one expectation - to get to know Slackware and Linux better than now.
So my 3 questions are:
-1- is there anything special to consider in order to follow -current?
-2- are security updates, if applicable, available in a reasonable time frame?
-3- does following -current actually help to get a better understanding?
1) No, just read the changelog and be prepared to sort out some changes.
2) Yes, they're pushed on -current or in -10.1 (stable) version under patches.
3) Mostly, it helps you to get a better understanding of some critical packages.
If you go to the -current directory on a Slack mirror site or in the directory you downloaded to -current to, there should be a file called upgrade.txt which gives pretty good instructions on how to manually upgrade your system with all the packages in that release. In fact that's what I did to get my system running -current now.
I use slackpkg to keep current. After installing the most recent stable release I used slackpkg to upgrade to current with a simple "slackpkg upgrade slackware".
After blacklisting everything I don't want, I then run "slackpkg install slackware" to get any additional packages added to current from previous version.
To remain current, just run slackpkg upgrade on occassion and see what's been changed ( as well as reading change logs)
It helps a lot to get on Pat's mailing list as well. You'll receive an email for security updates as they come out.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.