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.
Maybe he wants to retire? Maybe he's had enough of maintaining Slackware?)
I know I would have after 20 years.
The problem is not so much Pat taking more time away (I don't blame him at all for that), the issue is that no other members of the team have commit rights, so when he does take time for himself, everything stops. It's very reminiscent of what happened with the linux kernel before Linus appointed various lieutenants and handed over management of various subsystems to them . These days properly maintaining a linux distro is too big a job for just one man to do full-time, let alone part-time. If Pat is feeling a little burnt-out on Slackware then I'm not at all surprised. I see it as an organisational weakness.
If there's any truth in any of the scenarios that we can all imagine, then surely we should leave the team insiders to handle whatever needs handling.
Besides, there's not been much compelling innovation since 13.37 came out. The new KDE may be an exception, but other new developments (OpenJDK, GTK3, orphaning of ConsoleKit vice systemd) have "World of Pain" written all over them. Security updates aside, right now is a good time for us all to chillax.
Distribution: Slackware64-current with "True Multilib." FreeBSD.
Mr. Volkerding has been done "this" for about twenty years, and as others have pointed out, if he wants to take some time off
I don't think anyone would blame him, he has earned it. However, such a sabbatical should be announced and people appointed to take up the slack (pun intended) during his absence. To do otherwise is.... well....
OTOH, maybe he is planning a major overhaul of Slackware that will dazzle the world and bring mickeysoft to their knees in awe?
Only time will tell...
Last edited by cwizardone; 01-09-2012 at 01:05 PM.
Slackware has enough developers.
Keep your patience please, Slackware is alive and so is Pat. Updates to -current are in the pipeline.
As I explained in my blog posts and here on the forum, Pat needs to spend time on other things besides Slackware, hence the apparent lack of movement. Sometimes, priorities can shift, but they will shift back too!