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.
I'm not going to single anyone out, since there are several people doing this. Let me just say that it would help all involved if everyone took the time to come up with more specific thread names. Just naming threads "Slackware" or "Slackware 9.0" or "Slackware problem" does little to nothing to help define to people what the problem involves. People are more likely to click on a thread and try to help, if they see something like "Resolution problem" or something like that, because it will bring to mind problems that some of us have had in the past and know how to fix.
This is a Slackware forum. We all know you are using Slackware. Let's be more inventive with respect to thread naming.
I just thought about that today. Good call. Also "I have a problem" and "Please help" and so on. Well, obviously - this is mainly a place to get and give help for problems. But the "Slackware 9, Slackware 9, Slack, Slackware" especially.
I feel this isn't a problem in just Slackware but all the forums on this site. We have tried to express this many times and also usually mentioning if you reply in the thread with a bad title.
We don't need to come off as rude but something like this would work if you see a thread with a badly titled thread, maybe mentioning after you supply a solution to their problem if you answered it that is:
"In the future if you can provide a better and more helpful thread title, this helps members browsing and searching the forums to know specifically what your thread is discussing/asking."