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: Slackware64-current with "True Multilib." FreeBSD.
Originally Posted by H_TeXMeX_H
So, what would you like communicated ? The ETA ?
How about something like,
I've decided to take some time off to spend with the family as, afterall, they are more important than even Slackware (praise Bob).
However, please be assured that Mr. Whoever and Ms.Whomever will be on hand to keep the
good Ship Slackware on a steady course during my absence.
Upon my return the development of the next release will commence and it will be ready when it is ready, as usual.
Thank you for your patience and understanding.
I've used Slackware exclusively for a number of years & it's been solid.
The lack of an active current branch & general inactivity is a little concerning.
A bit of peer production and collaboration surely could only help, and inform.
I personally would fully support the Slackware development team taking a year off, 'security' updates aside I guess. The lull in active development has allowed me to look a little closer at what I have at my fingertips (13.37) rather than concentrate on what is to come.
I am really really happy with 13.37. I haven't experienced any problems. Everything just works, day in day out. That is exactly what I want in a system. I don't care about new fancy stuff. All I care about is that it is working today and that I can expect it to work half a year from now.
I don't have time for tings to start glitching. A new version that wouldn't be as flawless as the former, is not a version worth releasing, IMO. It would damage the name, and it's users productivity. If they can do the next version 80% now or 100% in one year, I know what I would choose. To be honest, it feels like I upgraded to 13.37 just a week ago. And if one reboot accounted for one day, it would actually by three days ago.
(Though I also expect that security issues are to be addressed. I don't have time for identity theft either )