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.
For those running old hardware 14.2 is not old. I've always run the stable version, since 13.37 and have never needed the newest of any application other than CA-Certs, SeaMonkey, and the security fixes that Pat has always provided in a timely manner. I'm sure when 15.0 is released there will be a few months of breaking in for older hardware issues, like my old NVIDIA card and old P4 based CPU. Maybe I'll be on 14.2 forever now. Basically, if it isn't broken and there isn't a security issue for upgrading, then why break what works simply to say you're using the latest, is that vanity?
Objectively, 14.2 is old, but, at the end of the day, it comes down to the user. The applications he uses. Which desktop environment or window manager he prefers. So, my previous comment was merely a (kind of a) feedback and a remind to this.
After last python upgrade, i have left 14.2 in a tiny netbook which i use it for writing (libreoffice), mostly when i am outdoors. Do not care if it is old or new - though i ll upgrade it to 15 when is the time.
Donate some money to Slackware; become a Patreon supporter. Run Slackware64-current
Now that is good advise! I was not aware of the option to donate to Pat via Patreon and I have just started doing that!
I've been a Slackware user from my first Linux installation (a shoe box full of 3.5" floppies!) in the 1990's and have run Slackware in production ever since.
My guess is we're waiting for stable of 5.14.x. Which according to LTS arithmetic should be next LTS kernel. Despite division among users there is no sign our BDFL will resign from LTS kernel in stable release.
My guess is we're waiting for stable of 5.14.x. Which according to LTS arithmetic should be next LTS kernel. Despite division among users there is no sign our BDFL will resign from LTS kernel in stable release.
As usually LTS kernels are released at the end of the year (oct., nov. or december)
I bet more on 5.15 or 5.16
If my bet on LTS kernel is correct it can't be 5.15.x or 5.16.x Or LTS kernels arithmetic would change: it is just previous LTS + 4 = next LTS. So 10 + 4 = 14. And 5.10.x is last LTS kernel. Or our BDFL will change its policy about kernels shipped with stable release.
If my bet on LTS kernel is correct it can't be 5.15.x or 5.16.x Or LTS kernels arithmetic would change: it is just previous LTS + 4 = next LTS. So 10 + 4 = 14. And 5.10.x is last LTS kernel. Or our BDFL will change its policy about kernels shipped with stable release.
Before that
5.4 + 4 = .... 5.10 :-)
LTS kernel release date :
5.10 2020-12-13
5.4 2019-11-24
4.19 2018-10-22
4.14 2017-11-12
4.9 2016-12-11
4.4 2016-01-10
Yeah you right. It is not such simple. There are other factor: amount added - changed code - how matured is kernel. On top of my list of kernels are: 4.19.x and 5.4.x
Edit: Particularly users of 14.2 may consider to update to 4.19.x. But I think there is no gain to update higher than 4.19.x
Yeah you right. It is not such simple. There are other factor: amount added - changed code - how matured is kernel. On top of my list of kernels are: 4.19.x and 5.4.x
Sorry, I know this is traditionally not a cool question to ask about Slackware, but I havn't been reading software news for years so I thought maybe someone can share some rumours.
Does anyone have any idea when the next Slackware version is coming? Or is it never?
Looking at some recent history, it's usually not been more than a few months from Alpha/beta release until final release. And Slackware 15 was beta in April. So, I'm hoping it's right around the corner. But it seems the window for a summer release has passed. But I'm personally quite hopeful for August/September.
Even if Slackware 15 stable came out right now, it would only be, for a possibly short period of time, be 'cutting edge' for stable and the whole cycle would continue.
With Slackware 16 being wanted, etc.
I mean, I get it, but, if you want a Slackware installation that is quite 'current', why not use the 'current' branch?
Some people are update hysterics, and don't seem to understand you can keep using old software as long as it works (at your own risk and work). You can update it yourself, that's the freedom you are given!
To others, your idea of using "current" is probably the best solution. Browsing around this forum, I've come by plenty of people who just stick to current and don't even bother with the releases.
Whining and complaining doesn't help. It is what YOU make it, so all you really do is whine about your own lack of doing X or Y. There are other ways of doing things as well, for security for example, not only "updating", which in some cases might be uncecessary and can be solved in other ways. You could perhaps, eh, install SELinux (maybe, PITA)
I skipped 14.2 (for main) because it didn't fit me at the time, but I could have made it work, I chose not to. Instead of whining about it, I'm extremely thrilled that Slackware 15 looks like it will be a perfect match for me. And if it isn't, I can make it so if I chose. The base is there, and it is good. If I don't use it, that's my own choice/problem and doing.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.