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.
Distribution: Debian, Red Hat, Slackware, Fedora, Ubuntu
Interview with Patrick Volkerding
I'm happy to announce that Patrick Volkerding has agreed to be next in the LQ Interview Series. Let me know what questions you'd like me to ask in this thread. I'll pick some of the best ones and add them to the questions I already have and then them to Patrick some time next week.
1) slackware.com contains a good amount of deprecated information. Have you considered updating the site or nominating a site maintainer or making it into a wiki where others can keep it up-to-date ? (or at least nominating a site like slackwiki.com to be the official wiki).
2) Every time slackware.com goes down, people panic, and sometimes this can hurt slackware's reputation and prevent it from reaching its full potential. Have you considered alternative hosting options or converting it to a wiki ? (or at least posting what's going on somewhere to stop wild speculation of impending doom and apocalypse)
3) As the sole slackware maintainer and BDFL have you ever considered a more interactive approach to distro development and maintenance ? For example, using git to maintain the slackbuilds, and maybe let others contribute ? This may lighten the load on you and the other non-official maintainers.
4) How are things going in general ? (hopefully well) Is there anything slackware fans can do to help with any inconveniences ?
5) Have you considered ways to better communicate with slackware users, like a blog ?
Please, no more "when is the next release", it is in the FAQ:
Q: When will the next version of Slackware be released?
It's usually our policy not to speculate on release dates, since that's what it is -- pure speculation. It's not always possible to know how long it will take to make the upgrades needed and tie up all the related loose ends. As things are built for the upcoming release, they'll be uploaded into the -current tree. If the -current does not exist, it probably means we have just released a new version of Slackware. A new -current tree will be formed shortly after the new release is made.
The wider Slackware community seems to get extremely protective of Pat when it perceives any kind of negativity. Is that helpful, or should we all just chill out?
The desktop environments and their dependencies continue to add bulk, and slackware-current seems to be bigger than a DVD at the moment. Is that going to cause a problem for the next release?
Right now, there are a number of quite intrusive technical changes coming from the big distributions. (It would perhaps be provocative to be specific, but I guess we all know who and what.) Is this a threat to Slackware's distinctiveness? Do Pat and the team get consulted? Are there any of these changes that Pat would commend to us?
Yes, the next version of Slackware will be released when it's ready.
The question I've had is how does Pat determine that the next version is ready? Is it just a whim? Is there stress and stability testing involved? If so, what kind? Is there some sort of goal that has to be achieved for a release? What is the process by which a Slackware release is deemed ready?