I’m sorry if you felt I was being rude - I was actually trying to help you. The first and second link shows you an excellant references on how to ask a question. Many people do not know and have not been told - I sure didn’t.
If you don’t wish our help - I’m sorry to see you go. If you don’t want to do any research on your own and expect us to hold your hand the whole way… then maybe this isn’t the right website for you.
[b]Before you ask[/b]
Before asking a technical question by email, or in a newsgroup, or on a website chat board, do the following:
- Try to find an answer by searching the Web.
- Try to find an answer by reading the manual.
- Try to find an answer by reading a FAQ.
- Try to find an answer by inspection or experimentation.
- Try to find an answer by asking a skilled friend.
- If you are a programmer, try to find an answer by reading the source code.
When you ask your question, display the fact that you have done these things first; this will help establish that you’re not being a lazy sponge and wasting people’s time. Better yet, display what you have learned from doing these things. We like answering questions for people who have demonstrated that they can learn from the answers…
Prepare your question. Think it through. Hasty-sounding questions get hasty answers, or none at all. The more you do to demonstrate that you have put thought and effort into solving your problem before asking for help, the more likely you are to actually get help…
Never assume you are entitled to an answer. You are not; you aren’t, after all, paying for the service. You will earn an answer, if you earn it, by asking a question that is substantial, interesting, and thought-provoking ? one that implicitly contributes to the experience of the community rather than merely passively demanding knowledge from others.
On the other hand, making it clear that you are able and willing to help in the process of developing the solution is a very good start. ?Would someone provide a pointer??, ?What is my example missing?? and ?What site should I have checked?? are more likely to get answered than ?Please post the exact procedure I should use.? because you’re making it clear that you’re truly willing to complete the process if someone can simply point you in the right direction.
Be precise and informative about your problem
* Describe the symptoms of your problem or bug carefully and clearly.
* Describe the environment in which it occurs (machine, OS, application, whatever). Provide your vendor's distribution and release level (e.g.: ?Fedora Core 1?, ?Slackware 9.1?, etc.).
* Describe the research you did to try and understand the problem before you asked the question.
* Describe the diagnostic steps you took to try and pin down the problem yourself before you asked the question.
* Describe any recent changes in your computer or software configuration that might be relevant.
Do the best you can to anticipate the questions a hacker will ask, and to answer them in advance in your request for help.