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 was not going to respond to this thread. Guys, the subject that Slackware.com is down is not that important as far as getting information. Sure, it would be nice to have a site that is reliable. Slackware was without a site in the past and still survived.
I notice that you talk like this is a simple inconvenience, and that it doesn't matter. Yet here we are, on page 12, discussing what is up with the state of Slackware.
Everyone on LQ knows that slackware isn't going to die. But the important thing is the signal effect this has. Not for us, the "hardcore userbase", but for everyone else. That's why this matters so much to me. My local kebab house got a website for crying out load, and here Slackware Linux suddenly don't?
Quote:
Originally Posted by NetrixTardis
Yes, we are aware of the problems with www.slackware.com.
Yes, it will come back up eventually.
When?
when it is ready!
Really? Are you guys even serious? I'm volunteering in hosting websites for small organizations. I've been woken up in the middle of the night because a website with like 100 visitors daily wasn't working. If we've got downtime, planned or not, we inform our customers.
It's 2012, one simply don't not have a website. People don't make a call or go to a local store to grab a catalog to check something out. You go to their website. This is especially so when it comes to software.
The point is that information is crucial. In 2012 if you are serious in what you are doing, you have a website. And if that website is to fail for one reason or another, you put up a 503 or whatever the code is. And when things get real bad, you inform people. Else you get this, what we have here, speculations.
Quote:
Originally Posted by smoooth103
Caitlyn, your comments about Slackware and pretty much everything you say is completely off-base. It reminds me of bad local new reporter who tries to break a story on one sentence of information obtained from a stranger on the street corner.
Newsflash! It's how society works! And when there is no official information opposing this, guess what. Shit hits the fan. And no, Eric and Robbys responses on a forum doesn't count. (Though I thank them for their contribution to this thread).
Slackware won't die, but certainly it's reputation will suffer. And that is my not very humble opinion
Well, yes I have. But we get our internet connection from the university and we aren't allowed to host commercial websites. So to do this I would have to send in an application, and that will probably take several days to process. :/
I notice that you talk like this is a simple inconvenience, and that it doesn't matter. Yet here we are, on page 12, discussing what is up with the state of Slackware.
Everyone on LQ knows that slackware isn't going to die. But the important thing is the signal effect this has. Not for us, the "hardcore userbase", but for everyone else. That's why this matters so much to me. My local kebab house got a website for crying out load, and here Slackware Linux suddenly don't?
Really? Are you guys even serious? I'm volunteering in hosting websites for small organizations. I've been woken up in the middle of the night because a website with like 100 visitors daily wasn't working. If we've got downtime, planned or not, we inform our customers.
It's 2012, one simply don't not have a website. People don't make a call or go to a local store to grab a catalog to check something out. You go to their website. This is especially so when it comes to software.
The point is that information is crucial. In 2012 if you are serious in what you are doing, you have a website. And if that website is to fail for one reason or another, you put up a 503 or whatever the code is. And when things get real bad, you inform people. Else you get this, what we have here, speculations.
Newsflash! It's how society works! And when there is no official information opposing this, guess what. Shit hits the fan. And no, Eric and Robbys responses on a forum doesn't count. (Though I thank them for their contribution to this thread).
Slackware won't die, but certainly it's reputation will suffer. And that is my not very humble opinion
I agree with all of that. If the site goes down, we must be informed about it, else you get threads like this and people start panicking and it hurts Slackware's reputation. Something must change about this to improve its reputation and prevent future incidents.
There is one problem tho ... communication with Pat V and the devs is difficult. It is hard to implement something like this when communication is not efficient.
slackwiki.com looks good, I didn't know that the address changed, and nobody posted about it (or at least I didn't see it). I think it could serve as a starting point for a new official slackware site. Just change the front page to something more appealing, put a clear description of slackware and links to the important stuff, and then things will improve from there.
Caitlyn, your comments about Slackware and pretty much everything you say is completely off-base. It reminds me of bad local new reporter who tries to break a story on one sentence of information obtained from a stranger on the street corner. You attempt to formulate fifty conclusions from one forum statement and repost all your unconfirmed opinions as first hand information.
I predict that her "factual article" will include whining about how mean we were to give her feedback (like this) on her writing process and communication strategy. That's what she calls "personal attacks", you know.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,085
Rep:
Quote:
Originally Posted by Dinithion
I notice that you talk like this is a simple inconvenience, and that it doesn't matter. Yet here we are, on page 12, discussing what is up with the state of Slackware.
Everyone on LQ knows that slackware isn't going to die. But the important thing is the signal effect this has. Not for us, the "hardcore userbase", but for everyone else. That's why this matters so much to me. My local kebab house got a website for crying out load, and here Slackware Linux suddenly don't?
Really? Are you guys even serious? I'm volunteering in hosting websites for small organizations. I've been woken up in the middle of the night because a website with like 100 visitors daily wasn't working. If we've got downtime, planned or not, we inform our customers.
It's 2012, one simply don't not have a website. People don't make a call or go to a local store to grab a catalog to check something out. You go to their website. This is especially so when it comes to software.
The point is that information is crucial. In 2012 if you are serious in what you are doing, you have a website. And if that website is to fail for one reason or another, you put up a 503 or whatever the code is. And when things get real bad, you inform people. Else you get this, what we have here, speculations.
Newsflash! It's how society works! And when there is no official information opposing this, guess what. Shit hits the fan. And no, Eric and Robbys responses on a forum doesn't count. (Though I thank them for their contribution to this thread).
Slackware won't die, but certainly it's reputation will suffer. And that is my not very humble opinion
Very well said, Dinithion!
The complete lack of basic common business sense over this last year has been very disheartening, to say the least.
This is all going to be pretty funny when Patrick pops in next week and has been on mountain vacation for three weeks and has no clue of this phantom "meltdown"... He'll probably just ./restart server and all will be well again. lol.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,085
Rep:
Quote:
Originally Posted by H_TeXMeX_H
...There is one problem tho ... communication with Pat V and the devs is difficult. It is hard to implement something like this when communication is not efficient...
Well... They all, including Mr. Volkerding, do read this message board and their e-mail addresses are available.
slackwiki.com looks good, I didn't know that the address changed, and nobody posted about it (or at least I didn't see it).
I don't think it was announced. It threw me when I first noticed following a comment in this thread near the end of last year.
Quote:
Originally Posted by H_TeXMeX_H
I think it could serve as a starting point for a new official slackware site.
Niels Horn told me around that time that slackwiki.org was registered to Erik Hanson, though I am not sure what happened. I presume Erik either deciding it wasn't needed or the registration simply lapsed. Either way it seems that slackwiki.com/.org are not "official". Sure, like SlackBuilds.org the wiki is important to the wider community but it isn't one of PatV's sites.
Edit: It seems that the registration lapsed once previously (roughly a year before), so it is reasonable to expect it might be the same thing this time. Though as I said, it is not an official site anyway. Also it seems to be run by the same groups of people who maintain SlackBuilds.org. If so they are doing it for free in their spare time. So no complaints from me. We only need one domain for slackwiki anyway.
Last edited by ruario; 04-18-2012 at 01:41 PM.
Reason: I added a second quote from H_TeXMeX_H, added link to posts about previous problems
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
