LQ Suggestions & FeedbackDo you have a suggestion for this site or an idea that will make the site better? This forum is for you.
PLEASE READ THIS FORUM - Information and status updates will also be posted here.
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.
The focus on 0 reply threads is good, but when a thread gets at least one reply, it then becomes a lower priority for browsers even if the OP's problem remains unsolved. Perhaps there could be an additional marker next to the thread subject (controlled by the OP? or some other mechanism?) indicating whether the problem remains? Just tossing out an idea here; anyone think this would be helpful? Obviously if neglected by posters it would then be ignored by browsers and become useless, but if posters paid attention to it and turned it off upon problem resolution it might become quite a useful filtering option, IMHO.
Thanks Jeremy for a fabulous site!
As mentioned, there have been numerous discussions in the past on how to mark threads as being "solved", "answered", "unanswered", "still need help", etc. The Search function will retrieve those conversations.
In brief, it's a great idea in theory, but finding a practical way of implementing it is the dealkiller. It comes down to the fact that the only person who can indicate whether the problem was solved or not is the OP, and therefore, in order for the system to work, it would require everyone who posts a question to maintain their own threads in perpetuity.
Various tools have been deployed in the past that attempted to provide that functionality, but the reality was that nobody used them. Overall, I would encourage all LQ'ers to simply post back to their thread if a particular piece of advice was helpful. It's polite, plus it's extraordinarily helpful to future readers who are encountering the same issue.
I think a flag that also checks via logins. If the OP doesn't log back in within a couple of days/a week, the unanswered flag gets turned to inactive.
And, of course something in their profile/emails to remind them of stuff. I mean, I'm getting daily? emails telling me about activities on my threads (which I can't figure out how to turn off), and on threads that I've looked at (I'm not always interested in them, just looking damnit).
Distribution: Debian, Red Hat, Slackware, Fedora, Ubuntu
You'd never get a notification for a thread you only looked at. To stop getting the notification, simply unsubscribe from the thread (there is a direct link in the notification email or you can browse them in your UserCP).