How to ask questions the smart way wisdom Copyright (c) 2001 by Eric S. Raymond Chinese Copyleft 2001 by DHGRAND (Nobody / Ginux) English: http://www.tuxedo.org/~esr/faqs/ Smart-qustions.html thanks to Eric patient poorer and consent, this article is completed and released, this guide English copyright is all, the Chinese copyright is owned by DHGRAND [NoBody / Ginux]. How to ask for a directory introduction to ask for a careful selection of the forum to use the mailing list with the message, the syntax is correct, spelling no misunderstanding is rich in easy-to-read format, the accurate title is exactly description, the amount of information is not more symptoms, do not say Guess the symptoms in the order of symptoms, don't ask for private reply. You want to ask what do you want to ask if you solve the problem. If you want to solve the meaningful question, you will have no harm, and often help the problem, add a short story how to understand the answer RTFM and STFW: Don't bother me, still don't understand: (In the face of unhealthy, don't like a loser, then ask questions, bad problems can't find the answer ==== Introduction ==== in the hacker world, when proposed When a technical problem, what kind of answer you can get? This depends on the difficulty of digging out the answer, it also depends on what you ask. This guide is designed to help you improve your skills to get your most wanted answer. First of all you It must be understood that the hackers only prefer the arduous tasks, or can inspire their thinking. If do we come back? If you have a good question worthy of chewing the taste, we will be grateful to you. The problem is that incentives, it is a thick gift, which can improve our understanding, and usually expose what we have never realized or thoughts. For hackers, "asking!" Is a strong praise from the heart. The hackers have a despise simple problem and unfriendly bad name, sometimes it seems that we have hostile to the newbie, but it is not that. We don't want to cover up the contempt of such people - they don't want to think Or don't do what they should do before you ask. This kind of person will only murder - they are only willing to ask, never pay, do not consume our time, and we can use time in more interesting problems Or more worthy of the answer. We call such artificially "losers" (due to historical reasons, we sometimes fight "lusers"). We also know that many people just want to use the software we have written, technical details Not interested. For most people, the computer is just a tool, a means to achieve the purpose. They have more important things to do, there is more important life. We understand this, and it is not expected that everyone is interested in the technical problems of our dischat.
However, the style of our answer is aimed at such a group of people - they are interested, and willing to actively participate in the problem. This will not change, nor should it change; if we change, we will lose our efficiency. We have a large extent belong to volunteers, with the time from the busy life to solve the answer, and often submerged. So we have ruthlessly filter out some topics, especially those who look like a loser, so that more efficient use of time to answer the victory. If you think that we are too arrogant, let you not be cool, let you wrote, you can think about it. We didn't ask you to succumb to us - in fact, most people in our favorite fair trading, as long as you pay small efforts to meet the minimum requirements, we will welcome you to join our culture. Come. But let us help those who don't want to help themselves. If you can't accept this "discrimination", we recommend that you spend money to find a technical support agreement to find a technical support agreement, don't give help to hackers. If you decide to help us, of course, I don't want to be considered a loser, and I don't want to be a member of the loser. The best way to get a valid answer is to ask questions like winners - smart, confident, and solve problems, just occasionally, it needs to get a little help on a specific issue. (Welcome to this guide to make improvements to this guide, please e-mail to esr@thyrsus.com, however, please note that this article is not a general guide to the network etiquette, I usually refuse to adopt the proposal for the technical forum to get useful answers.) (Of course, if you write Chinese, it is best to send it to DHGRAND@hotmail.com ;-) ======== before question ======== By email, news group or chat room Before the problem, check you if you have: 1. Read the manual, try to find an answer yourself. 2. Look in the answer in FAQ (a well-maintained FAQ can include :). 3. Search online (personal recommendation google ~). 4. I am in listening to your friends. When you ask questions, you must first explain what you have before this; this will help to establish your image: You are not a beggar who is inused, do not want to waste others. Can explain what you have learned from these operations. If the questioner can learn something from the answer, we are more happy to answer his questions. Thoughtful thinking, ready for your problem, the question of the grass rate can only get the answer to the grass rate, or you can't get any answers. The more you show your efforts to solve the problem before seeking help, the you can get a substantive help. Be careful, don't ask questions. If your problem is based on the wrong assumption, the ordinary hacker (J. Random Hacker usually uses meaningless literal explanation to reply you, thinking "stupid problems ...", I hope you will answer from the question (and Did you you want to get a lesson. Never think of being qualified to get answers, you don't have this eligibility. After all, you didn't pay any remuneration for this service.
You have to go back to "earn" back to an answer, relying on a question of connotation, interesting, thinking incentive effect - a problem with potential contribution to the community, not just passive from others Knowledge - to earn this answer. On the other hand, you are willing to do something in the process of finding the answer, it is a very good start. "Who can give some indications?" Because you seem to have a correct direction, you have your ability and determination. ======== How to ask ======== ------------ Carefully choose the forum ------------ Carefully choose to ask questions . If you are likely to be described below, you are likely to be ignored or seen as a loser: 1. The forum that is not between the wind horse is posted on your problem 2. Exploring the high-level technical forum posted very primary questions; Violation of 3. In too many different news groups, the crossed hackers usually cut off the problem of the wrong place to protect their communities without being submerged. You won't want your post being cut off this way. In general, the problem is sent to a well-selected public forum, which is easier to get useful answers than the closed small circles. This phenomenon has a variety of reasons, one of which is the public forum has more potential questions; another reason is to have more listeners in the public forum. The hacker is more willing to make the tried as possible - not a limited one or two - from the answer. ---------------- Try to use the mailing list ---------------- If a project has its own development mailing list, you must send the problem Go to this mailing list instead of a developer, even if you know who can answer your questions. Take a closer look at the project documentation and project homepage, find the message list address of this project, the reason for this is four: 1. Any questions worthy of ask a developer, it is worth mentioning to the entire development group. Conversely, if you think this problem is not worth mentioning in the mailing list, there is no reason to use it to harass any developer. 2. Ask questions on the mailing list to share the developer's workload. A developer (especially when he is the responsible person of the project), you may not have time to answer your questions. 3. Most mailing lists have historical archives, and they can retrieve in the search engine. People can find your questions and answers from it, do not need to ask again in the list again. 4. If a problem is often proposed, developers can improve the document or improve the software to reduce the user's sleep. And if the problem is always proposed in private, there will be no one has a whole grasp of this. If you can't find the item list address of the project, you can only see the project maintainer, then write to the maintor. In this case, don't think that the mailing list does not exist. Show in your letter You have tried our best to find the mailing list. In addition, you don't mind transfer this news to others. (Most people think that private letters should be private, even if there is nothing confidential. Allow your news to others, giving the recruiter a choice for handling your email.
) ---------------------------- Use the words, the grammat is correct, spelling the words ------------ ---------------- We found out from experience, careful writers often also think about horses and tiger (I dare to pack). The problem that answers carelessly is not worth it, we would rather turn the time elsewhere. Therefore, it is very important to clearly express your problems. If you are troublesome, we will be too lazy to take care of you. Note to push your use, do not have to use a strange language - in fact, the values of hacker culture are unfair. Accurately use slang and humorous language, but don't use it; you must indicate that you are thinking, paying attention. Correct spelling, punctuation and case is important. Don't confuse "ITS" and "IT's" or "Loose" and "Lose". Don't use all uppercase forms, this is regarded as a rude loudly shout (all don't use your lowercase, because this will bring difficulties to read .alan Cox can use all lowercase, but you can't do it). More general, if your question is written like a half illiteracy, you are likely to be ignored. If you write like a geek (cracking enthusiast) or gray, you will be able to find it yourself, guarantee that you can't get ruthlessly resistant (or the best ending is A big pile of "help"). If you ask questions with non-nominal forums, you can make a little fault to spell and grammar - but you can't think about the horse tiger (right, we can figure out the respective respective respectively). In addition, unless you know what words you will use, please use English. Hackers in a hurry often skip their problems they don't understand, and English is a working language on the network. You can reduce your problem with English. It is not read. -------------------------------------- If people create your question, it is difficult to read And understanding, it will be easier to be ignored. So you want: 1. Use plain text messages, don't use HTML (it's not difficult to turn off HTML). 2. You can usually attach the MIME accessory, but must have real content (such as additional source files or patches), not just the file template generated by your mail client (such as a copy of your message). 3. Do not put all the questions in a full segment of non-stop. (This will make the answer to the answer to answer some of the questions, even if you can answer all the questions, I also want to have a clear one :). It is very likely that the recipient can only read the letter on a text display of 80 character widths, so the row surround mode is within 80 characters. 4. Do not use mime quoted-printable encoding in English forum; this encoding format is necessary to speak the language that the ASCII code cannot be expressed, but many mail agents do not support it, at this time, "= 20" The symbols are separated by text, and there is difficult to see and distract. 5. Never expect the hacker to read the file format of the closed ownership, such as the soft Word format.
Most of the black passengers are like you are full of hot-baked pig manure on the ladder on the door (the meaning of anyone will not step into your door - the translator's note). 6. If you send an email through a computer that installs Windows, close the soft stupid "intelligent reference" function. This will make you free from junk characters in the email. ---------------------------- Use the meaning of use, describe the accurate title -------------- -------------- In the mailing list or newsgroup, the topic title within about 50 words is the golden timing of seizing senior experts. Don't use your chatter "help" (not to say "help !!!!!" This opportunity is to waste this opportunity. Don't want to use your pain to touch us, don't use space instead of the problem, even if it is an extremely simple description. Stupid question: Help! My lap is not displayed normally! Smart problems: Xfree86 4.1 Lower mouse cursor deformed, FooWare MV1005 display chip. If you ask questions in your reply, remember to modify the content headline, indicating that there is a problem. A problem that looks like "Re: Test" or "Re: new bug" is difficult to attract enough attention. In addition, reference and delete the contents of the previous article, leave a clue to the new readers. ------------------ Accurate description, the amount of information is large ---------------- 1. Carefully describe the symptoms. 2. Provide a problem that occurs (machine configuration, operating system, application, and other). 3. Explain how you study and understand this problem before you ask questions. 4. Note What steps you have taken before you ask questions. 5. Russen has recently made hardware, software changes that may have an impact. Try to think about how a hacker will ask you, give him an answer when you ask questions. Simon Tatham wrote an excellent essay called "How to Effective Report Bug". Strongly recommend you to read it. -------- Words are not available -------- You need to provide accurate and effective information. This is not asking you to simply put the ton of error code or data completely dump in your question. If you have a large and complicated test condition, try to cut it as much as possible. There is at least three points everywhere. First, you have made your efforts to simplify the problem, which allows you to answer the opportunity to increase; second, simplify the problem to increase the opportunity to get useful answers; third, in the process of refining your BUG report, Maybe you can find a problem or make corrections. ------------------ just say symptoms, don't say guess ------------------ telling hackers you think is How can I have no help? (If your inferior is so effective, do you want to help others?), So be sure that you originally tell the symptoms of their questions, don't add your own understanding and push. Let hackers diagnose it.
Stupid question: I encountered a SIG11 error in the kernel compilation, I suspect that a flying line is on the front line of the motherboard, how should this be the best? Clever problem: I have a set of K6 / 233 systems, motherboards are FIC-PA2007 (VIA Apollo VP2 chipset), 256MB Corsair PC133 SDRAM, frequently generating SIG11 errors in kernel compilation, from booting 20 minutes later, this situation I never happen within 20 minutes before booting. It is useless to restart, but it will work 20 minutes in one night. All memory has changed, no effect. Typical compilation records in the relevant part .... ------------------ The symptoms are listed in time ------------------ the most helpful thing to find out Clues are often a series of operations before the problem, so your description should include steps, as well as the computer's reaction until the problem is generated. In the case of a command line, save an operational record (eg, using scripting tools), and reference related to about 20 commands will be greatly helpful. If the crash has a diagnostic option (for example with -v to detail mode), try carefully considering the option to add useful debug information in the operational record. If your explanation is long (more than four paragraphs), the problem will help, followed by the next time. This hacker knows what to find in your instructions. -------------- Don't require private reply -------------- hackers believe that there should be public, transparent processes. As long as any more people have noticed the incomplete or incorrect answer, this initial answer can be corrected and should be corrected. At the same time, through ability and knowledge, everyone is noted, and is accepted by everyone, answering the questioner got the rewards. If you ask the other party to answer you privately, this has destroyed the entire process and also destroyed the reward system. Don't mention this requirement, this is the right of the respondent, which is to choose whether to reply privately - if he chooses this, it is often because he believes that this answer is too obvious or adversely affected, others will not be interested. There is only one limited exception: if you expect to receive a lot of similar answers, you can say: "Send the answer to me, let me summarize." It is very gentleman's wind - but please remember, fulfill your commitment to summarize. -------------- Understand what you want to ask -------------- Nothing margin, a few days of unhappy time black hole. People who can give you useful answers are also the most busy people (they are busy because they must do most of them.). Such people don't have a cold, so they can also say that they have a bad cold about the margin. If you explicitly express what you need to answer (provide suggestions, send a code, check your patch or other), it is most likely to get useful answers. This will set a maximum of time and energy, which makes it easy to help you.
To understand the world of experts, to imagine professional skills as abundant resources, while replying time is poor resources. Solve your problem, the less time you need, the more you can take an answer from a busy expert port. Therefore, the structure of the optimization problem is minimized, and the experts will have a lot of help - this usual and simplified issues are different. So, ask "I want to know better X, can I give some hints?" I usually ask "Can you explain X?" Better. If your code can't work, ask what is wrong, than you ask others to make much more attention. ------------------------ Don't ask questions to solve your own ------------------- ---- hacker is always good at distinguishing which issues should be solved by yourself; because most of us have solved such problems. Similarly, these problems have to be done by you, you will learn from the middle. You can ask for a prompt, but don't ask for a complete solution. ---------------- Remove meaningless questions ---------------- Don't use meaningless words, such as "someone can help I? "Or" Is there an answer? ". First of all: If you are not very suitable for the description of the problem, this is more painted. Second: Because this question is to draw the snake, the hacker will be tired of you - and usually use logically correct answers to represent their contempt, for example: "Yes, someone can help you" or "no answer". ---------------------------- Humble is not harmful, and often help ------------- --------------- Binbin courtesy, use "please" and "first thank you first." Let everyone know that you spend time obligations to help heart gratitude. To be honest, although this is not like syntax, clear accurate description, avoid private formats, etc. (can not be used to replace them); hackers usually prefer to directly and technical kens reports, rather than Binbin There is a ritual nonsense (if this makes you confused, please remember, the standard we measure a problem value is: it can learn how much). However, if you have a lot of problems, you can't solve it, and the courtesy will increase your opportunity to get useful answers. (We note that since this guide is released, the only serious defective feedback from the Senior Hacker is the first to thank this. Some hackers feel that "thank you", I will not thank anyone. Our suggestions are: all thank you.) ------------------------ Problem After adding a short description --------- --------------- After the problem is resolved, send someone to all the people who have helped you, let them know how the problem is solved, and once again thank them. If the problem has attracted extensive attention in newsgroups or mailing lists, it should be made there. Supplementation does not have to be long or deep; simple sentence "Hello, it turned out to be a problem! Thank you - Bill" More than anything is stronger.
In fact, unless the conclusion is really technical, short and lovely summary is better than a long academic papers. Explain how the problem is solved, but it is not necessary to repeat the process of solving the problem. In addition to representing politeness and feedback, this supplement helps others in the mailing list / newsgroup / forum to search for your full solution to you, which may also be useful to them. Finally (at least?), This supplement helps all people who have provided help have been satisfied. If you are not a older or hacker, I believe us, this feeling is very important for those tutors or experts you have to help them. The problem will be discouraged; the hackers are eager to see the problem is resolved. Good people have good news, meet their desire, you will taste the sweetness when you post new questions. ============ How to understand the answer ============ ------------------ RTFM and STFW Don't bother me -------------------- There is an ancient and sacred tradition: If you receive the reply of "RTFM (Read The Fucking Manual", answer Those who think you should read the TMD manual. Of course, basically he is right, you should read it. RTFM has a young relative. If the answer is "STFW (Search The Fucking Web)", the responder thinks you should go to TMD online search. Basically, he is also right, you will go. Usually, one of these two sentences to answer your person will give you a manual or a URL that you need content, and when they play these words, they are reading. These replies mean that the answer is considered (1). The information you need is very easy to get; (2). You can search for this information than the filling you can let you learn more. Don't be refreshed for this; in accordance with the criteria of hackers, he did not see the requirements for you, and it is already able to represent your attention to you. You should express our gratitude to his grandmother. ---------- still don't understand: (---------- If you are not very understanding the answer, don't immediately ask the other party to explain. It's like you have tried to solve the problem. Handbook, FAQ, network, the master is to understand it. If you really need the other party to explain, remember what you have learned. For example, if I answer you: "It seems that ZENTRY is blocked. You should first clear it first. ", Then:" What is ZENTRY? "What is ZENTRY?" The smart question should be like this: "Oh ~ I have seen help :) but only -z and -p two The parameters mentioned ZENTRY: (and there is no clear explanation: More appropriate, this is the product of the straightforward communication. This communication method comes from the solution of people's concern - how many people feel warm, but they are still paste. If you feel that you are treated with rude, please stay calm. If someone has a crude wild, there will be a list / newsgroup / forum's elders to talk to him. If you don't have this, you are a lot of temper, it is likely that the other party's words and deeds are the hacker community behavior specification license, and you are considered It is fault. This will not be conducive to you get information or help. On the other hand, you can also have a rough words and mentality without any reason. The other of the above phenomena is that people allow 狠 击 击 真 冒,, use a sharp speech to analyze their improper words. If you really decide to do this, take a closer care and carefully you have your own components. The reasonable rude and the unable to launch a fine line, and the hacker who has lost the collision is not a small number; if you are a novice or the door, the opportunity does not commit this fault is very embarrassing. If you want to get information, not to come trouble, don't take a risk to reply, it is best to pick it up from the keyboard. (Some people claim that most hackers have mild symptoms of lonely or social disorder syndrome, and the lack of partial brain tissue structure that helps "common people" in social behavior. This may be true, maybe not. If you are not a hacker So, people we imagine that there is a defective person in the brain, help you face our weird. There is something to say, we don't care; we are happy to live with your own ideas, and always hold a quite doubtful attitude toward medical concept. In the next section, we will talk about another topic; "Rude" that may be encountered when you are in the wrong way. ================ Never like a loser ================ It is possible, you will be subject to the forum in the hacker community. Many public attacks - use the various methods or similar methods mentioned herein, and it is likely to have a wide range of bypass sides to tell you how much you hate you. If the nightmares come true, what you can do is complaining, complaining that you have attacked personal attacks, ask the other side to apologize, scream, breathe, threaten to complain to each other, tell his boss, do not pick up the toilet seat ,Etc., etc. However, you should do this: Go, this is not big. In fact, it is appropriate and beneficial (mainly for your body and mind :). The community's norms do not rely on communities, but to actively promote their people to maintain, this maintenance is open, obvious. Don't complain that all criticism should be transferred through private letter, it shouldn't be the same. When others pointed out your words, or when he has different views, he insists that he is shame you are useless. These are the attitude of the loser. There are some hacker forums, for the misunderstanding of highly self-reliability, prohibiting participants from posting the post to find the post, and being told "If you don't want to help the user, then shut up. ", They think that the topic of the participant will only make them intoxicated in the meaningless chatter, thereby losing the meaning of the technical forum. Exaggerated" Friendly "(in that way) is also useful help: you You can choose it. Remember: When hackers say you are very annoying, (Whether you use a rude language) Warning you don't do that, he is not targeted (1) you, and (2) his community. He Originally, you can easily ignore you, wipe you from his sight. If you can't accept your gratitude, at least you should show your gas, don't complain, don't expect just because you are a newcomer, you have a drama Sensitive fragile nerve and self-sealing rights, and is treated with fragile dolls. ========== Think down, ask ==================================================================================================================== And the hacker thinks in the heart of the refusing: Question: Where can I find X programs? Question: My program / configuration / SQL declaration does not use problems: my windows has problems, can you help me? Question: I have a problem when I installed Linux (or X), can you help me? Question: How can I crack the root account / stealing OP privilege / read the email? Question: Where can I find the X program? Answer: On I found it, the idiots - the one of the search engine. Scorpio! Does anyone not use Google? Question: My program (configuration, SQL declaration) does not answer: This is not a problem, I am Find out your true problem is not interested - if you want me to ask you 20 questions - I have something more interesting. When I see this problem, my reaction is usually not Before you have three: 1. Do you have anything to add? 2. True, I hope you can get it. 3. Do you have any birds with me? Question: My windows has a problem, can you help me? Answer: Yes, throw away the soft rubbish, change Linux. Question: I have a problem when I installed Linux (or X), can you help me? Answer: No, I only personally do it in your computer Find a problem. Or go to your local Linux user group seek your handle guidance (you can find the list of users here). Question: How can I crack the root account / steal OP privilege / read someone else's mail? Answer: I want to do this, indicating that you are a man; if you want to find a hacker to help you, you are an idiot! ============== Good problem, bad problem =============== Finally, I will give some examples to explain how smart questions; the same problem The two questions were put together, one is stupid, the other is wise. Stupid question: Where can I find information about FOONLY FLURBAMATIC? This question is nothing to get the answer "STFW". Clever question: I have searched "Fooly Flurbamatic 2600" with Google, but I didn't find useful results. Who knows where to find information on this kind of equipment? This problem has been STFW, it seems that he really encounters trouble. Stupid question: I can't compile the source code I found from the Foo project. How is it so bad? He feels that it is the fault of others. This arrogant guy: (smart problem: Foo project code cannot be compiled in Nulix 6.2. I have read FAQ, but I didn't mention the problem related to Nulix. This is My compilation process record, what do I do? He tells the environment, and also read FAQ, but also indicated the mistake, and he did not push the responsibility of the problem to others. This guy is worth paying attention. . 问题: My motherboard has a problem, who will help me? Ordinary hackers answer the answer to this type of question is usually: "Okay, have you take back the back and change diaper?", Then press the delete key Clever question: I tried X, Y and Z on the S2464 motherboard, but there was no effect, I tried A, B and C. Please note that when I try C, I will showcase the sideband transmission. Contract, but the result is unexpected. What is the usual reason for the sideband leak on the multi-processor motherboard? Who has a good idea to do something test? This guy, from another perspective, worth it Go to answer him. He showed the ability to solve the problem, not to sit on the sky and drop the answer. In the last question, pay attention to "tell me the answer" and "give me the revelation, point out what I should do what diagnosis work" And important differences. In fact, the latter problem is derived from a real question on the list of Linux kernels in August 2001. I (ERIC) is the person who makes a problem. I observed on the Tyan S2464 motherboard. This uninterreciated lock phenomenon, the list members provide important information to solve that problem. Through my question method, I gave everyone something worthy of taste; I made people very easy to participate and attracted it. I showed it. I have their equivalent ability, invite them to discuss with me. I told them the detour that I have gone to avoid them to waste time, this is a respect for the value of others.
