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 have used 14.2 for years but when I got a new laptop early this year, I had to move over to openSUSE because of the newer hardware, but I have a partition all laid out and ready for the next stable version of Slackware. Now if we can just convince Pat to put it out.
No need to go to SUSE, -current is very solid if you want something for newer hardware. Update it at your convenience.
As much as I would like to keep with Slackware as my distro of choice, I really don't want to be running current. I'll keep checking in the hopes that something happens, but I'm about done. I hope there's something important that is holding up the next release. It would be a shame to see another year or 2 go by, all for the sake of perfection. I will keep checking in, but I'm not hopeful.
Yeah, I'm the least risk-adverse person ever when it comes to operating systems, and I hated Arch for the 3 months I used it. I've been on Slackware current for a few weeks, and it's not bad, all things considered. At this point in time I'd recommend it, if you've got newer hardware. (Although it really does need to ship with qt5...)
As much as I would like to keep with Slackware as my distro of choice, I really don't want to be running current. I'll keep checking in the hopes that something happens, but I'm about done. I hope there's something important that is holding up the next release. It would be a shame to see another year or 2 go by, all for the sake of perfection. I will keep checking in, but I'm not hopeful.
Quote:
Originally Posted by hitest
I feel the same way. I will be evaluating Debian 10 on Saturday. This is a change of heart for me.
Come on, guys. We all know that Pat and Team are working hard on the next release (just look at the -current change log) and we all know that it won't be just 14.3. It's going to be 15.0, when it's ready. Let's not forget that 2018 was a difficult year for Pat and his family, so let's be patient: he deserves it.
For the record, I've been running -current for more than one year now, with no issues.
Last edited by Philip Lacroix; 07-03-2019 at 04:11 PM.
I’m thinking of moving some of my 5 current work stations to Debian 10.
Surely this is shiny new stuff syndrome. What can you not do on Slackware -current which you feel you can do, and do better, on Debian 10?
I think part of the problem, I'll admit, is the fact that this is the longest gap between releases ever and comms have been absent from the main tent of the Slackware camp. At least some kind of roadmap would be interesting to know of, Slackware core team.
That said, I can literally see no reason for moving to Debian, let alone any systemd distro. And I dare say you won't get much in the way of quality support from the mediocre Debian community.
Distribution: Slackware/Salix while testing others
Posts: 1,718
Rep:
Quote:
Originally Posted by Lysander666
Surely this is shiny new stuff syndrome. What can you not do on Slackware -current which you feel you can do, and do better, on Debian 10?
I think part of the problem, I'll admit, is the fact that this is the longest gap between releases ever and comms have been absent from the main tent of the Slackware camp. At least some kind of roadmap would be interesting to know of, Slackware core team.
That said, I can literally see no reason for moving to Debian, let alone any systemd distro. And I dare say you won't get much in the way of quality support from the mediocre Debian community.
For what its worth the autotools build is gone now in the mesa git master, moving forward meson will be the only choice.
Yes I've seen this, that's why I've mentioned it. Meson in 14.2 does work, but there some circular dependencies.
Not in a rush to do this on 14.2, maybe in few years.
Quote:
Originally Posted by bassmadrigal
Many times you won't even need to get the new hwdb rules (this was the first I'd even heard of it, but thanks for the info!) for that hardware to work. You can also update your PCI ID list using update-pciids to most likely fix any items that don't have proper names in lspci.
It's just old eudev with new rule set, I didn't know either but was forced to do something because of some new ssd (sata, no pci).
It'd show in dmesg with an error, it was not in the database until I bumped the 14.2 rules from -current eudev rule set.
Quote:
Originally Posted by bassmadrigal
While just updating the kernel will provide support for most hardware, video cards can be a little different. To fully benefit from newer graphics hardware, you usually need an updated X driver along with an updated mesa and any dependencies for those that might need to be upgraded (mesa typically requires fairly new libdrm).
X driver is no problem, I've used a template SlackBuild to compile only libdrm and xf86-video-nouveau-1.0.16 without recompiling all of /x/ so that's settled.
I use the 32bit legacy binary driver too, but on another x86 system which never gets any new features or updates. It works fine, but I would not recommend it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
