SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
In regards to the site requiring old version of php, really ?...I can rewrite the site in less than a couple of hours with new php code or django or any other framework. Slackware is a one man show, as most members have already pointed out, like others I have offered hardware, hosting and coding but so far no word from Pat. We can mention all the logical steps to provide a solution for such a simple problem but we dont make the decisions. It is the main reason I do not use Slackware in a production environment due to the 'oshit' factor of its unknown state. A real distribution requires a group of people with a common goal, and I hope there is some type of organization put in place in Slackware's future or it will be time to move on. I love Slackware and the effort of the core team but website aside the overall attitude of "we dont need a website" and "who cares" really is bothersome sometimes. Are we that l33t or is it a hip thing now to not have a website and pretend to have sticks up our butts.
In regards to the site requiring old version of php, really ?...
No, not "really". That was my speculation. What we've actually heard was:
There are also offers for virtual space, and (most helpful of all), some people offering to take a look at the main issue, which is that the site will need work (perhaps even a rewrite) to bring it up on a new machine.
This is an interesting thread. It's always amusing to see this sort of thread (similar to those next update ones). I just notice a new one, related to panic posted today. I've been using Slackware a long time. I didn't even notice slackware.com is occasionally unavailable until Eric started this thread. I don't go to Slackware.com much these days. No need for it. I sync to a mirror (Thanks AlienBOB). One in a while a mirror, goes down, I switch to another or just wait it out. That's never failed me. When all lines of communication are cut off (i.e., this forum), then perhaps I will panic.
I do think slackware.com is very important, but like Eric, and I am sure others here, I am satisfied with the supplied answers to the question.It's enough for me to know it's "in the hopper". I am sure it will be accessible again sooner or later, when it ready.