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.
OK i think it really worthed to wait for this big update.
and now it's worthed to check the ChangeLog before updating all those packages just to make sure it doesn't miss any new packages
On purpose? I don't know. Stopping to provide patches/inform about security problems on the security mailing list without any notice at all may be on purpose, it may be not, how would we know, there is no communication. But that doesn't change a thing. What is the point in a security mailing list when it stops being maintained without any notice?
As I said, I won't recommend Slackware anymore until this has changed and will stop using it for any purpose I would normally use it for from now on. I wouldn't tolerate this from any other distro and I don't see why I should for Slackware.
@ReaperX7: This is not about being bleeding edge, this is about security patches.
@anyone/everyone ... I like slackware more than anything, I recommend it to everyone. But no one ever listens to me. I agree that the slackware mailing list should never stop being maintained, I have always assumed it has automation when it comes to subscriptions, when trying to subscribe that is. I have recently found this an issue to re-subscribe ... wow!!! Talk about crazy stress of an extinction burst in sending majordomo@slackware.com subscription emails!
As for no communication for security or announcements very recently, that is not satisfactory. I do pay for all my slackware products! And will continue to. Slackware is the bomb! But maybe it is more than unsatisfactory of an assumption to expect that the slackware mailing list should always be maintained. After all, there is only a small group maintaining things, with that said, it is easy to understand that there is a lot of work to be done, and we have no idea what is going on behind the scenes. ... Still "I" would prefer that the mailing lists are always stable. As I said no one listens to me! I'll slack till I die!
Since I started this .... and boy, was I surprised at the number of contributions to the thread ... I marked it solved.
The humungous update certainly let us now that Patrick (and the gang) are alive, well and kicking butt !
I agree that the slackware mailing list should never stop being maintained, I have always assumed it has automation when it comes to subscriptions, when trying to subscribe that is. I have recently found this an issue to re-subscribe ... wow!!! Talk about crazy stress of an extinction burst in sending majordomo@slackware.com subscription emails!
The mailing list subscribe/unsubscribe bug has been fixed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.