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.
Mon Apr 12 20:07:12 UTC 2021
I'm going to go ahead and call this a beta even though there's still no fix
for the illegal instruction issue with 32-bit mariadb. But there should be
soon (thanks ponce!) No build regressions noted with the official gcc-10.3
release. Please report any new (or old) issues on the LQ Slackware forum.
Enjoy! :-)
I did that too a while back and ran Arch on this box for several days. Reverted back to Slackware64-current. I'm running Arch with MATE in a VM. I like Arch, but, not as much as Slackware.
At what point will pat make the 15.0 branch split from current and release ISO files?
Nobody knows. It all depends on how fast Pat feels the system is stable enough for a release. Back with 13.0 in 2010, it was only a matter of a few weeks from beta to stable. But with 14.2 in 2016, it took over 5 months.
However, 14.2's beta was pretty disruptive as that's when Pat added pulseaudio to the system, switched to the 4.4.x series kernel, and had a total of 15 programs added to the main tree. These abrupt changes could've led to a longer testing period. For 15.0, it seems that all the major disruptions have already been added and ironed out, so hopefully it won't take too long.
If you want to see how long previous releases took, marav put together this post to cover it.
I did that too a while back and ran Arch on this box for several days. Reverted back to Slackware64-current. I'm running Arch with MATE in a VM. I like Arch, but, not as much as Slackware.
Slackware by far is my first choice, looking forward getting it up and running.
To me Slackware is -current, so I won't be changing my mirrors file. There's never been more than rather momentary issues with slackware64--current in recent years . Why should i settle for anything less?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.