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.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
As a relatively-newbie I think I could make a suggestion on how to help people write better initial threads. There have been one or two occasions when I have come up with a very unexpected problem and no idea what might have caused it. I honestly wanted to include the relevant information, but I had no clue what information I should include. Perhaps if we could create and sticky a post with a quick outline of what information would be relevant people would add information.
I know, this does nothing to fix the problem of people being lazy, but it might help those of us who are just ignorant. :-)
LQ's own XavierP has written an excellent tutorial on how to use LQ as well as how to ask a question. If you have not already seen them, I'd suggest taking a few moments to read through them. They both contain a great deal of useful info
I've read the post, as I think everyone should. I just meant - maybe we should sticky a post with information like "usually the last 20-25 lines of a long error message are what we should see" and "if you are dealing with a foo problem you should provide your kernel version"
The first time I had a build error, I didn't want to just say "I got ERROR:2", but neither did I want to post 692 lines of code.
I would be willing to write said post myself, but I really don't think I'm qualified.
qualified? Can you use linux? then you're qualified.
Seriously, have a go. I'm sure it will be appreciated and useful. If anything, it will encourage those more qualified (if lazy) to improve upon your article- you would have gotten the hardest part out of the way- just starting it.
I don't know if it's just my firefox, but you could improve the site by making sure that the oracle add doesn't come up over the menu options across the top under the logo! I can't click on some of them.
1. Can we have a code button as well as a quote button on the quick reply window?
This was asked before, but Jeremy said that he doesn't want to overload the quick reply box with too many controls. After all, it is meant to load faster than the full reply box and hence it's fairly basic.
I don't know if it's just my firefox, but you could improve the site by making sure that the oracle add doesn't come up over the menu options across the top under the logo! I can't click on some of them.
Rgds
Yeah, the oracle add covering up the drop down menus is really annoying.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.