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.
Fire? Flames? I'm not seeing them. All I saw was one person overreacting, and that would have happened even without vtel57's blog entry.
This thread should be kept open for its original purpose, which is news.
I agree that vtel57's blog post did not cause distress for Slackware team members including Pat. There are some who ran away with twisted-around versions of that blog post and those are the ones causing damage if any. Eric's post was sincere and I have no issues at all with that, or his later comments.
As for this thread, it only serves as a means to let the discussion fester. All that should be said, has been said. There is no "news" to be had here.
It's time to congratulate Eric on maintaining such an exemplary level of transparency. I mean, can you imagine anyone else publically admitting that financial issues have anything to do with a server outage, even if it's true?
It's also time to congratulate Pat for having spent this difficult time delivering what his actual market wants. Not only did he fix the server and the store, he also pushed updates to -current during this time.
And it's time to congratulate the maintainers of Slackware's mirrors, who kept Slackware available so that no-one was inconvenienced by anything other than worry.
It's time to congratulate Eric on maintaining such an exemplary level of transparency. I mean, can you imagine anyone else publically admitting that financial issues have anything to do with a server outage, even if it's true?
It's also time to congratulate Pat for having spent this difficult time delivering what his actual market wants. Not only did he fix the server and the store, he also pushed updates to -current during this time.
And it's time to congratulate the maintainers of Slackware's mirrors, who kept Slackware available so that no-one was inconvenienced by anything other than worry.
+1000000
Thank you to everyone involved in Slackware. Slackware wouldn't be possible without you guys.
I'm a relative newcomer to Slackware; I've run Slackware for 8 years. Over the years I've tried a variety of distros and BSDs. Slackware is home to me. Slackware continues to deliver legendary stability, security, and excellent applications.
I get a really good chuckle when I read the doom and gloom bloggers, it reminds me a lot of some tabloids I could name.
Slackware is a rock.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.