引言

在黑客的世界,你所提技术问题的回答很大程度上取决于你提问的方式与解决此问题的难度,本文将教你如何提问才更有可能得到满意的答复。

开源程序的使用已经很广,你通常可以从其它更有经验的用户而不是黑客那里得到回答.这是好事,他们一般对新手常有的毛病更容忍一点.然尔,使用我们介绍的方法象对待黑客那样对待这些有经验的用户,通常能最有效地得到问题的解答。

第一件需要明白的事是黑客喜欢难题和激发思考的好问题.假如不是这样,我们也不会写本文了.如果你能提出一个有趣的问题让我们咀嚼玩味,我们会感激你。好的问题是种激励与礼物帮助我们发展认知揭示没有注意或想过的问题.在黑客中“,,,是非常真挚的赞许好问题!”。

除此而外,黑客有遇到简单问题就表现出敌视或傲慢的名声,有时候我们看起来还对新手和愚蠢的家伙有条件反射式的无礼,但并不真正是这样。

我们只是毫无歉意地敌视那些提问前不愿思考、不做自己该做之事的人.这种人就象时间无底洞──他们只知道获取,不愿意付出,他们浪费了时间,这些时间本可用于其它更值得回答的人和更有趣的问题.我们将这种人叫做”失败者(失败者)”(由于历史原因我们有时将“失败者”,“lusers拼为”)

我们注意到许多人只想用我们写的软件,他们对学习技术细节没有兴趣.对大多数人而言,计算机只是种工具,是种达到目的的手段.他们要生活并且有更要紧的事要做,我们承认这点,也从不指望每个人都对这些让我们着迷的技术问题感兴趣.不过,我们回答问题的风格是为了适应那些真正对此有兴趣并愿意主动参与问题解决的person,这一点不会变,也不该变.如果这都变了,我们就会在自己能做得最好的事情上不再那么犀利。

我们(多数)是自愿者从自己繁忙的生活中抽时间来回答问题有时会力不从心.因此我们会无情地滤除问题,,,,”特别是那些看起来象是失败者的胜利者”,以便更有效地把回答问题的时间留给那些

如果你认为这种态度令人憎恶、以施惠者自居或傲慢自大,请检查你的假设,我们并未要求你屈服──事实上,假如你做了该做的努力使之成为可能,我们中的大多数人非常乐意平等地与你交流并欢迎你接纳我们的文化.试图去帮助那些不愿自救的人对我们简直没有效率,不懂没有关系,但愚蠢地行事不行。

所以,你不必在技术上很在行才能吸引我们的注意,但你必须表现出能引导你在行的姿态──机敏、思考、善于观察、乐于主动参与问题的解决.如果你做不到这些使你与众不同的事情,我们建议你付钱跟别人签商业服务合同,而不是要求黑客无偿帮助。

If you decide to ask for help, you don't want to be a loser, you don't want to be seen as a failure. The best way to get a quick response is to make the questioner look smart, self - confident, and suggest that it is just a matter of chance to be helped on a particular issue.

Welcome to correct this paper, you can send the proposal to esr@thyrsus.com. Please note that this article does not want to become a general network etiquette guide, I generally refuse to those with the technical forum will lead to useful recovery is not particularly relevant recommendations

Question before

Do the following by e-mail, news group, or web forums to ask technical questions:

  • Try to search the Internet to find the answer
  • Try reading the manual to find the answer.
  • Try to read the FAQ (common problem) document to find the answer.
  • Try to check your answers or try to find the answer.
  • Try to find the answer to ask knowledgeable friends
  • If you are a programmer, try to read the source code to find the answer.

When asking questions, please state that you have done the above, which will help to establish the impression that you are not a parasite and waste other people's time. Best to express what you learn from the middle school, we like to answer those who show the answer to learn from the people.

Use certain strategies, such as using Google to search for the errors you encounter (both search page also look up the discussion group), may directly find a solution to the problem of the document or mail list. Even if there is no result, in the e-mail or news group posted a question when I was in Google in the following sentences but did not find any useful thing is a good thing.

Prepare your questions and think about the problem. A hasty question can only be answered lightly, or a. In asking questions, the more you show and try to solve problems, the more likely you are to get practical help.

Pay attention to the problem. If you ask questions based on the wrong assumption, a hacker will probably want to "stupid" questions...... "Answer your questions in a literal, useless answer, and hope that it will only be a lesson for you to answer, not the experience you need.

Never assume that you are qualified to answer. You do not have this qualification, after all, you do not have to pay for this service. If you can ask questions that are content, fun, and motivation - there is no doubt that there is no doubt that you can contribute more to the society than the negative ones, and you will "earn" the answer to that question.

On the other hand, it is a good start to show that you are willing to participate in the problem. "Is there anyone who can point to a direction? "I," this is what point? "," I should check which website? Please give me the complete steps I can use to get a reply, because you show that you are happy to complete the rest of the process as long as there is someone who can point you in the direction you want.

Question time

Carefully selected Forum

To see where the question, if you do the things that will probably be written off or to be seen as "loser":

  • To post a topic completely unrelated to the topic of the Forum
  • In the Forum on the issue of high - level technical problems, or vice versa.
  • Cross posting in too many different news groups at the same time
  • For neither acquaintance has no obligation to solve your problem person posting your private email
  • In order to protect the communication channel is not the thing that is not closed, hackers will get rid of those who do not find the problem, you will not want to have this experience.

So the first step is to find the forum, Google and other search engines or your friends, you can use them to search and you encounter difficulties of the software and hardware issues related to the project's website. That usually has a project FAQ list, mailing lists and their documents link. If your efforts (including reading FAQ) are not the result, the mailing list is the last place to get help. The site of the project may also have reports of bugs in the process or link, if so, go and see.

Sending messages to a stranger or forum is likely to be an adventure. Do not assume, for example, that a person who is rich in information is a free consultant who wants to act as your advisor, and don't think you will be welcomed to do a good idea. If you're not sure, send it elsewhere or simply don't get it.

Don't trust your name too much when choosing a web forum, news group, or mailing list, look at FAQ or permission to make sure that your question is relevant to the topic. Posted before Zi Ke first read the posts to help you feel the way there. In fact, it is a good idea to search for the key words in the news group or the mailing list before you post, and you may find the answer. Even if not, can also help you to sort out a better problem.

Don't like disposable "fire" machine gun all help pass, it was like yelling and unpleasant. One by one.

Figure out your theme! One of the most typical errors in the Windows platform is a kind of language, libraries or tools in the language, libraries or tools to mention about the operating system program interface issues. If you don't understand why this is a mistake, the best in the clear concept before what also don't ask.

In general, asking questions in a carefully selected public forum is more likely to get a useful response than asking the same question in a private forum. There are many reasons to support this, one is to see how many potential respondents, the two is to see how many of the participants in the forum, the hacker is more willing to answer questions that can inspire the majority of people.

It can be understood that sophisticated hackers and some of the authors of popular software are receiving inappropriate messages that are beyond their capacity. Like the extra can straw that broke the camel's back, you may also make a move towards the extreme, has good several times the, the author of some popular software withdrew from the support of the software, because with the flock to the private email a lot of useless messages become intolerable.

Novice oriented web forums and IRC usually respond quickly

Local user organizations or the Linux distribution you use may be getting help from novice web forums or IRC (Internet Relay Chat) (in non English speaking countries, the new forum is likely to be a mailing list), these places are a good place to start asking questions, especially when you feel that you may only be relatively simple or general problems. Through the propaganda of the IRC channel is a public invitation to ask questions, you can usually get a reply in real time.

In fact, if the issue of the program from a certain issue (which is very common), in the program of the project forum or list of questions before the best first in the issue of the forum or list in the list, (otherwise) the project hackers may only reply with our code"

Before posting on any web forums, check to see if there is a search function. If there is, try to try some of the key words search, maybe there is help. If you have done a full web search before then, or just another search forum, search engines may not have all of the content of this forum recently.

Through web forums or IRC channel to provide users with the support of the project has a growing trend, e-mail communication is more for the project development and retention. First in the web forum or IRC to seek help from the project related.

The second step, using the project mailing list

When a project has a developer mailing list, even if you are sure who is the best answer to the question, but also to the list rather than one of the individual questions. Check the documents and home page of the project, find the mailing list and make use of it. There are several good reasons to adopt this strategy:

Any good enough questions to individual developers will also benefit the entire project team. On the contrary, if you think your problem for the entire project team, Tai Yuchun, this can not be a reason to disturb a single developer.

Asking questions on the list can balance the developer's burden, and a single developer (especially the project leader) may be too busy to answer your questions.

Most mailing lists have historical documents and are indexed by search engines, others can find your questions and answers through web searches without having to ask again in the mailing list.

If some questions are often asked, developers can use this information to improve the documentation or the software itself to make it more clearly. If it's just a private question, no one can see the full scene of the most common problems.

If a project has a "user" or "developer" (or "hacker") mailing list or web forums, and you do not play with those code, to the "user" list or forum questions. Don't assume that you will be welcomed in the developer list, who will most likely suffer from your noise.

However, if you believe that your problem is not general, and in the "user" list or a few days in the forum did not reply, you can try the "developer" list or forum. It is recommended that you observe a few days before posting a good idea of what you are doing (in fact this is a good idea to take part in any private or semi private list).

If you can't find a project mailing list, and can only be found in the maintainer of the project address, just to the sender. Even in this case, don't assume that the mailing list does not exist. Stating that you have tried and failed to find the appropriate mailing list in your email address, and you are not opposed to forwarding your message to others (many believe that even if no secret, private e-mail should not be made public. By allowing your e-mail to be sent to the corresponding personnel to deal with the choice of your mail.

Use clear and meaningful topics

In mailing lists, news groups, or web forums, the subject is the golden opportunity to attract qualified professionals with fifty or fewer characters, and don't use the words "please help me" (let's say, "please help me."!!!! "The news of this theme will be erased by the conditional reflex type. Don't use your pain depth to impress us, on the contrary, to describe the use of Super Space in this concise and to the point in question.

The good practice of using the subject is "object - bias" (description), and many technical support groups do this. In the "object" section, it is a question of which or what group of things are specified. In the "Deviation" section, the description is not consistent with the desired line.

Foolish:

Help ah! My laptop video is not working properly!

Wise:

XFree86 4.1 twist the mouse cursor, a graphics card MV1005 model of the chip group

More wise:

XFree86 4.1 mouse cursor is distorted by using a MV1005 model of a certain graphics card

The process of writing an "object - to - Deviation" description will help you to organize your problem more specifically. What has been affected? Just a mouse cursor or other graphics? Only appears in XFree86? Or just in its version 4.1? Is for a graphics card? Or is it just the chipset of its MV1005 model? A hacker can immediately understand what is the problem you are in, what is your own problem.

More generally, imagine looking for a document index that only shows the subject. Let your subject better reflect the problem, you can make the next search for similar problems can be found in the document directly to find the answer to the clues and not to post questions.

If you want to ask in reply, make sure to change the subject to indicate that you are asking a question, a topic like "re: test" or "re: new bug" is unlikely to cause enough attention. At the same time, will reply with the new topic is not related to the reference content as far as possible to delete

For a list of messages, don't just click on the reply (button) to start a new thread, which will limit your audience. Some mail reading programs, such as MUTT, allow users to sort by clues and to hide the message through the fold line, so that people do not always see your message.

Just changing the subject is not enough. Mutt and other mail reading programs should also check the information of other mail headers other than the subject so that it can specify a clue, so it is better to send a new message.

In web forums, because messages are closely combined with specific cues and are usually not visible outside of the line, a slightly different way of asking a good question is not important (some forums don't even allow a separate topic in response, and it's basically no one to see). But asking questions by itself is questionable, because they will only be read by people who are looking at the clues. So, unless you want to ask in the clue of the currently active population, or build their own good.

Make it easier to reply

Please refer to...... Answer "to end the problem will probably make you get no answer. If you think it's troublesome to take a few seconds to set up a reply address in the mail client, we also think it takes a few seconds to think about your problem. If your mail client program does not support this, change a good point. If the operating system does not support all this mail client program, but also a good point.

In a web forum, it is completely rude to ask for an e-mail reply, unless you are sure that the information is confidential and that someone will only let you know the answer for some unknown reason. If you're just trying to get an e-mail alert when someone replies, you can ask the forum to send it. Almost all of the forums provide such as "pay attention to the clues", "reply to send mail" function.

Use clear, grammar and spelling.

Experience tells us that careless and sloppy writers are often careless and sloppy thinking and programming (I bet). For these benefits and what not careless sloppy thinker to answer the question, we would rather spend time in other places.

To express your problem clearly and completely is very important. If you think this is a problem, we also feel the trouble. Take extra effort to consider the words, not too stiff and formal - in fact, hacker culture is very important to be able to accurately use the informal, slang and humorous statements. But it must be very accurate, and there are signs that you are thinking and closing the question.

Correct spelling, punctuation and capitalization, not to "its" confuse "it's" and "loose" into "lose" or "discrete" inflicted "discreet". Do not use all caps, it will be seen as rude shout (all lowercase or less, because it is not easy to read. Cox[Alan note: the famous hacker, an important player in the Linux kernel, might be able to do this, but you can't do it.

In general, if you write like a semi illiterate fool, probably not to be ignored. If like a small child doodle that is absolutely courting death can be sure nobody will care about you (or most is to give you a lot of blame and ridicule).

If you ask questions in a non - mother tongue, your spelling and grammatical mistakes will be limited, but laziness will not be tolerated (yes, we usually see the difference). At the same time, unless you know the language used by the responder, please write in English. Busy hackers will generally be directly deleted with their read do not understand the language of the message. In the Internet, English is the working language, written in English can be your problem is not to be directly removed to the lowest possible.

Send questions in easy to read format

If you make the problem difficult to read, it will probably be ignored, people are more willing to read and understand the problem, so:

Use text instead of HTML (Hyper Text Markup Language) (it's not hard to close HTML)

Use MIME (Multipurpose Internet mail extensions) attachments are usually no problem, provided that the content (such as attached to the source file or patch), and not just the mail client program template (for example, only the message content copy).

Do not send a single sentence but just mail back repeatedly (which makes reply part very difficult). Imagine your reader is reading a message in 80 characters wide text terminal, set your line return point less than 80 columns.

However, don't use any fixed column back data (such as log file or directly transfer the session records). The data should be included in the original, so that the respondents are convinced that they see the same thing as you see.

In English forum, do not use MIME'Quoted-Printable'encoding to send messages. This encoding is likely to be necessary for posting non ASCII languages, but a lot of mail agency programs do not support. When they are broken, the "=20" signs that are spread around the text are ugly and distracting.

Do not refer to the hackers read the use of closed special format documents, such as Microsoft Corp's Word or Excel files, etc., most hackers response to this is just like some people will still take the heat of the pig manure at your door when you react. Even if they can deal with it, they hate it.

If you send an e-mail from a computer using windows, shut down Microsoft's stupid "smart" function, so as not to spread spam messages in your mail.

In web forums, do not abuse "expression symbols" and "HTML" functions (when they are available). One or two expression symbols are usually no problem, but the fancy color text tends to make people think you are a incompetent person. Excessive use of emoticons, colors and fonts will make you look like a little girl. It's usually not a good idea, unless you're more interested in the nature and not the useful reply.

If you use a graphical user interface for mail client programs (such as Netscape Co's Messenger, Microsoft Corp's Outlook or other similar), pay attention to their default configuration is not set to meet these requirements. Most of these programs are based on the menu of the "view source" command, use it to check the message sent to ensure that the message is sent to the pure text files without extra impurities.

The description of the problem should be accurate and content

Carefully and clearly describe the symptoms of the problem.

Describes the problems that occur in the environment (host, operating system, application, any related) that provide the vendor's release and version number (for example: "Core Fedora 2", "Slackware 9.1", etc.)

Description of the research and understanding of questions before.

A diagnostic procedure to determine the problem before the question is asked.

Describes any recent changes to the computer or software configuration.

Try best to predict the hacker will mention the problem, and prepare the answer in advance.

Tatham Simon wrote an article called how to effectively report bugs, I strongly recommend that you read.

More is not equal to accurate

You should (write) and accurate content, simply a lot of code or data "dumping" not to help message. If you have a large and complex test sample that allows the program to crash, try to cut it as small as possible.

There are at least three reasons to support this. First, let other people see that you are trying to simplify the problem so that you are more likely to get a reply. Second, simplifying the question makes you more likely to get a useful response. Third, in the process of purification of the bug report, you may have found a way to solve the problem or a matter of expediency.

Do not easily claim to find bugs

When you encounter problems in a software, unless you are very, very, very, do not easily claim to find a bug. Tip: unless you can provide the source code patch to solve the problem, or to the previous version of the regression test to show the wrong behavior, otherwise you are probably not fully confident. For web pages and documents, you should be able to provide an alternative to the text if you have found a "bug" in the document.

Remember that there are a lot of other users that have not experienced problems you encounter, otherwise you read a document or web search should found (you before complaining already do this, right? ). This also means that it is likely that you are mistaken, not the software itself has a problem.

People who write software are usually very hard to make it as perfect as possible. If you claim to have found a bug, it implies that they have done something wrong, which is almost always unpleasant - even if you are right, the subject of the "bug" is particularly not sophisticated.

When you ask questions, even if you are very certain that you have found a real bug, it is better to write something like what you did wrong. If you really have a bug, you'll see it in the reply. In so doing, if you really have bugs, the defenders will apologize to you, and it will be better than the one you screwed up and owe someone an apology.

Humble instead he should do

Some people know they should not arrogant or rude act and get a reply, but humble they retreated to the opposite extreme, "I know I just what is not, what also do not understand the loser, but... ". This makes people puzzled and did not help, when accompanied by a vague description of practical problems is especially objectionable.

Don't lower primates strategy waste everyone's time. On the contrary, as clearly stated background facts and your problem, the humble better straighten out your position.

Sometimes, a web forum with separate beginners ask regional, if you really think a problem at the beginning of shallow, in that to be, but as don't humble.

Describe problem symptoms rather than guess.

Tell hackers what you think is the cause of the problem is not used (if your diagnosis theory is a great thing, you will also consult others for help? ). So, make sure you just tell them the original symptoms of the problem, not your explanation and theory, so they can explain and diagnose it. If you think it's important to state your guess, it's clear that it's just your guess and why they don't work.

Foolish:

I compile the kernel when a series of SIG11 errors, suspected of a circuit board on the motherboard off, and find their best way is what?

Wise:

I assembled the computer (K6/233 CPU, FIC-PA2007 motherboard (via Apollo VP2 chip group), Corsair PC133 SDRAM 256MB memory) recently in the boot for about 20 minutes, compile the kernel frequently reported SIG11 wrong, but in the first 20 minutes of never a problem. Restart will not reset the clock, but the whole night off. Replace all memory unanswered questions related to typical compile session log follows.

List of symptoms by time

What happens before a problem usually contains the most effective clues to solve the problem. So, it should be exactly what you and the computer did before the crash. In the case of a command line processing, a session log (such as running a script tool generated) and a reference to a number of related (such as 20) record will be very helpful.

If the program crashes diagnostic options (such as V verbose option), carefully consider these choices can add options for debugging information in the record.

If your record is long (e.g., more than four), it may be more useful to start with a brief description of the problem and then to list the details of the process at a later time. In so doing, the hacker knows what to look for when you read your record.

Describe purpose rather than steps

If you want to figure out how to do something (instead of reporting a bug), describe your goal at the beginning, and then describe the problems you have encountered.

Often this situation, to seek technical assistance in the head have a higher level of goals, they can achieve their goals in a specific way to be stuck, and then ran to ask how to go, but did not realize that the road itself has a problem, the results to a lot of effort to pass.

Foolish:

How can I make a color picker graphics program has sixteen hexadecimal RGB value?

Wise:

I'm trying to with their selected numerical color replace the color of a picture sheet. Now, the only thing I know is to edit each slot table, but it cannot give a graphic program in the color picker made hexadecimal RGB values.

The second formulation is wise, and it makes it possible to suggest a more appropriate tool for the completion of the task.

Don't ask for a private reply

Hackers think the problem solving process should be open and transparent, if more people in this process should be aware of the incomplete or improper, the initial reply to be able to, but also should be corrected. At the same time, as the respondent also because of the ability and knowledge to be seen by other peers to get some kind of return.

When you ask for a private reply, the process and returns are aborted. Don't do this, ask the person to decide whether or not to answer the question: if he does, it is usually because he thinks the problem is too bad or too superficial to be meaningless to others.

There is a limited exception to this rule, and if you are certain that a question can lead to a large number of duplicate responses, "send me an email and I will conclude these responses to the group". It is very polite to try to save the mailing list or the news group from a flood of similar responses, but you should keep your promise.

Problem should be clear

Boundless problems usually regarded as no clear time limit pit. Most may give you a useful answer usually is the most busy people (if only because they bear most of the work), these people for no limit of time sinkhole is extremely offensive, so they also have a tendency to hate the endless problems.

If you are clear about what you want to do (such as pointing direction, sending code, checking the patch or other), you are more likely to get a useful response. This allows them to concentrate and indirectly set the time and energy they need to spend to help you get the upper limit, which is good.

To understand the world of expert life, you can imagine: where there is a wealth of expertise in resources but the scarcity of response time. The less time you secretly asked them to give, the more you can from these really knowledgeable also really busy experts answered.

So limit your questions to the least amount of time you need to answer a question. This is usually not the same as the simplification problem. For example, "could you please give me some advice about how to interpret the X? "Often than" please explain X "wise. If you have any code that doesn't work, please ask someone else to see if there is a problem.

Don't post your homework

Hackers are good at finding "homework" questions. Most of us have done their homework, and that is what you have done in order to learn from their experiences. Ask a prompt no relationship, but not a complete solution.

If you suspect that you have encountered a homework problem, but still can not be resolved, try in the user group forum or (as a last resort) in the project of the "user" mailing list or forum questions. Although hackers will see it, some senior users may still give you tips.

Delete meaningless questions

Resist the help message at the end of the help message, such as "can someone help me? Or is there an answer? "In the sense that there is no such thing as a sense of meaning. First, if the problem description is not complete, these additional items can only be superfluous. Second, because they are superfluous, hackers would think that these things are annoying - it is possible to use a logical but sent back, such as "yes, you can get help" and "no, not to give you the help.""

In general, avoid mentioning "yes or no" questions, unless you want to get a "yes or no" type of answer.

Do not deliberately marked the issue of emergency

This is your own problem, don't let us. Declared that "emergency" is very likely to backfire: most hackers will delete this message, they think this is rude and selfish attempt to get immediate and special concern.

There is a little bit of local exception, if you are in some high visibility, will make the hackers are excited by the local use of the program, it may be worth doing so. In this case, if you have a deadline pressure, but also very polite to mention this, people may have enough interest to answer a little faster.

Of course, this is very risky, because hackers are very different from you on what is the most exciting standard. For example, from the International Space Station posted no problem, but on behalf of the good feeling of charity or political reasons to do so almost certainly not. In fact, posting "urgent: help me save the furry seals! "Hackers will certainly be avoided or angry, even if they think the little furry seals are important.

If you think this is unbelievable, and the rest of the contents read several times, until a clear re posting.

Politeness is always harmless.

Be polite, use "please" and "thank you for your attention" or "thank you for your advice" and let others know that you appreciate their free time to spend time with you.

To be frank, this is not the right grammar, the words are clear, accurate, and the content and avoid the use of special format important (but also can not replace them). Hackers generally prefer to read a little abrupt but distinct stink bug reports, and not the kind of polite but vague report. If you don't understand, remember that we are able to teach us something to evaluate a problem according to the problem.

However, if you have already talked about technical issues, it is certain that you will increase your chances of getting a useful answer.

We have to point out that this is the only place where some old hackers have seriously objected to the "advance thanks" that was previously recommended, and some hackers believe that this implies that no one should be grateful for any further. Our proposal is to say "thank you" in advance, and afterwards to say thank you to the reply. Or in other ways, such as "thank you for your attention" or "thank you for your advice.".

A brief description of the problem after the settlement of the problem

After the problem is solved to all the people who have helped to add a message, so that they know how to solve the problem and once again thank you. If the problem is widely concerned in the mailing list or in the news group, it is more appropriate to append the message.

The most ideal way is to reply to this message with a clue to the original question and to include the "resolved", "resolved", "set", or other similar meanings. In a crowded mailing list, a see clue "X" and "x has been resolved in reply potential who understood without wasting time (unless he personally feel that the" X "interesting), it can be to spend the time to solve other problems.

You don't have to be too long and too complex, a simple "hello" is a bad line! Thank you, Bill. "It's better than nothing. In fact, in addition to solve the problem of non real technical depth, a short and sweet summary is better than a long and minute statement. That is what action to solve the problem, need to replay the whole story debugging.

The depth of the problem, the post troubleshooting history is appropriate. Describe the final state of the problem, what is the solution to solve the problem, after which we can not specify the detour to avoid. Should avoid the detour section should be placed on the right solutions and other summary of the material, rather than the news into detective fiction. List the names of those who have helped you, and you will make friends.

In addition to polite, content, this type of chasing posts will help other people in the mailing list, news group or forum documents to find a real solution to your problem, so that they benefit.

In addition to the above, this kind of chasing posts also allows each person to participate in helping to solve the problem arising from a sense of satisfaction. If you are not a technical expert or a hacker, trust us, this feeling is very important for an experienced and expert who is seeking help. Describe the problem to the end always have never been heard of since frustrating, hackers itch itch desire to see them being resolved. Tickle you earn good to you next time again posted questions very very helpful.

Consider how to avoid other people will encounter similar problems in the future, ask yourself to make a document or FAQ patch has no help, if any, will be sent to the maintenance of the patch.

In hacking, this behavior is actually more important than the traditional politeness, but also you treat others to win the reputation of the way, which is a very valuable asset.

How to interpret the answer

RTFM and STFW: how do you know that you're totally screwed up

There is an ancient and sacred tradition: if you receive the "RTFM" reply, the sender that you should go to "read the Fucking Manual". He's probably right. Go and read it.

RTFM has a young family, if you receive a "STFW" back to the sender, think you should search "damn network". He's probably right, go and have a look. A little bit more softly, "Google is your friend! ")

In the web forum, you may also be asked to search the forum's documents. As a matter of fact, it may even be possible for you to provide you with a clue to the problem. But do not rely on this kind of kindness, the question should be before the search for a document.

Often, people who call you search have opened a manual or web page that can solve your problem. These replies mean he thinks: first, the information you need is easy to find. Second, their own look for more than others to feed their mouth to learn more.

You shouldn't feel offended by this, according to the hacker's standard, he doesn't have to say that you are a kind of respect to you, but you should be grateful that he is eager to help you.

If you don't understand

If you do not understand the answer, do not immediately back to a requirement that the news, first try your original question when used the same tools (manual, FAQ, web pages, knowledgeable friends, etc.) try to make sense of return. If you still need to explain, show what you already know.

If, for example, I tell you: "sounds like an input has a problem, you need to clear it, then a bad replies:" what is a zentry? ". And this is a good thread: "yes, I read the manual, an input only in the - Z and the - P switch is mentioned, but did not mention the removal of an option, you is which one is the mistake the? "

Treat rudeness

And many in hacker circles seem rude not mean to offend. On the contrary, it is a straightforward, a knife to see blood type of communication style. This style for more attention to solve the problem rather than make others feel uncomfortable and confused the people is very natural.

If you feel offended, try to react calmly. If someone has really done a thing, the mail list or news group or forum in the senior will say hello to him. If this does not happen and you get angry, then you get angry about the image of the language may seem normal in the hacker community, and you will be regarded as the wrong side, which will hurt you to get information or help opportunities.

On the other hand, you will occasionally encounter really rude and boring words. Contrary to the above, the real offenders dealt a heavy blow to, with sharp language will be the mincemeat of all are acceptable. However, you must be very, very, very, very well. Correct rude remarks and began a meaningless saliva war across the line, hackers their reckless more lines are not uncommon. If you are a new hand or outsiders, chances of avoiding such a blunder is not high. If you want to get information rather than killing time, it's better not to put your hands on the keyboard to avoid risks.

Some people assert that many hackers have mild autism autism or Asperger's syndrome, a certain lack of smooth human society "normal" contact brain circuitry. That may be true or false. If you're not a hacker, maybe you think we have a problem with our brains that can help you cope with our erratic behavior. So just do it, we don't care. We like the way we are now, and generally have a considerable doubt about the clinical diagnosis. )

In the next section, we will talk to another question, when you do not act at that time will be subject to the "offensive""

Don't react like a loser.

In the forum of the hacker community there are a few times you will mess up - in this paper, a detailed or similar way. You will be made to mess up, perhaps will bring some color words.

The worst thing that happened later, you can do Mo too you whine of the encounter, claimed was verbal attacks, apology, screaming, hold your breath, threatening to resort to the law, to the employers complain, forgot closing toilet cover and so on. Opposite, you should do this:

Go through, this is normal. As a matter of fact, it is good for health and proper.

Community standards are not maintained by themselves, they are maintained through active and open implementation of the participants. Don't cry all the criticism should be conveyed via private messages, this is not the way things work. When someone criticizes you for some of your claims or their opinions, it is a failure to insist that an individual is insulted and useless.

There are other hacker forums, too high courtesy requirements of misleading, asking participants to prohibit posting any other post pick fault messages, and was told that if you do not want to help users shut up". The results of the ideas of the participants have left the results will only make them become meaningless chatter and useless technology forum.

Is the exaggeration of the "friendship" (in the above manner) or useful? Pick one.

Remember: when a hacker says you've screwed up, and (no matter how harsh) tells you not to do it again, he's acting to care for you and his community. For him, it's much easier to ignore you and filter out your life. If you can't do it for, at least a little dignity. Don't make loud lamentations, not because you are a have dramatic super sensitive soul and thought qualified newcomers, they expect others to you treated like a fragile doll.

Sometimes, even if you don't mess it up (or just someone else will think you messed up), some people will attack you for no reason at all. In this case, it is really going to complain about the problem of mess.

These finding fault or is what also do not understand but opinionated experts with guy, or is testing whether you really will be messed up, a psychologist. Other readers either ignore or use their own way to deal with them. These finding in trouble for yourself, that you don't have to worry about.

Don't allow yourself to be drawn into a war of words, most of the war of words best to ignore - is, of course, you verify them only a war of words, did not point out you get hit, and there is no clever will hide the real answer questions in the (this is also possible) after.

Question taboo

Here are some of the typical stupid questions and hackers don't answer their thoughts.

  • Q: where can I find a program or X resource?
  • Q: how do I use Y to do X?
  • Q: how do I configure my shell tips?
  • Q: can I use the Bass-o-matic file conversion tool to convert AcmeCorp documents to TeX format?
  • Q: my {program, configuration, SQL statement} is not running
  • Q: I have a problem with my windows computer. Can you help me?
  • Q: my program is not running, I think the system tool X have problems
  • Q: I have difficulty installing Linux or X, can you help me?
  • Q: how can I break the privilege of a super user / channel operator to view someone's e-mail?

Q: where can I find a program or X resource?

Answer: I find it in the same place, stupid once - in the web search engine. God, do you still have people who don't know how to use Google?

Q: how do I use Y to do X?

Answer: if you want to do is Y, do not give a question when the method may not be appropriate. This problem that questions not only on X complete ignorance, also to solve the problem y confused, also be situation specific imprisoned the thinking. Wait until they get the problem out.

Q: how do I configure my shell tips?

Answer: if you have enough wisdom to ask this question, you should also have enough wisdom to RTFM, and then to find their own.

Q: can I use the Bass-o-matic file conversion tool to convert AcmeCorp documents to TeX?

Answer: try to know. If you try, you know the answer, you don't have to waste my time.

Q: my {program, configuration, SQL statement} is not running

Answer: This is not a problem, I do not have the interest to guess what you have the problem - I have more important things to do. To see this stuff, my reaction is generally as follows:
Do you have anything to add?
Oh, that's too bad. I hope you can get it.
What does it really matter to me?

Q: I have a problem with my windows computer. Can you help me?

Answer: Yes, the windows garbage deleted, install an open source operating system such as Linux or BSD.

Note: if a program has an official Windows version or an interaction with windows (such as Samba), you can ask questions related to windows, but don't be surprised by the response to Windows operating system instead of the program itself.

Q: my program is not running, I think the system tool X have problems

A: you might be the first to notice that there are obvious flaws in the system call and library files that are used by thousands of users. Extraordinary claims to extraordinary evidence, when you make a claim like this, you must have a clear and detailed defect documentation backing.

Q: I installed Linux or X to meet a problem, can you help?

Answer: No, I need hand operation of your computer to help you debug, the whereabouts of the local Linux user group seek help (you can find a list of user groups here)

Note: it may be appropriate to raise questions about the installation of this issue in a mailing list or forum or local user organization for a Linux distribution service. At this point, should describe the exact details of the problem. Prior to this, the first with the Linux and all of the suspected hardware (for keywords) carefully search.

Q: how can I break the privilege of a super user / channel operator to view someone's e-mail?

Answer: want to do this kind of thing that you are a despicable guy, want to let hackers teach you to do this kind of thing that you are an idiot.

Good and bad

In the end, I will demonstrate the wisdom of asking questions. The same question two kinds of questions, one kind is stupid, another kind is wise.

Silly: where can I find something about the Flurbamatic Foonly device?

The question is begging for a STFW response.

Wise: I used Google to search for "Flurbamatic Foonly 2600", but did not find anything useful, who knows where to find the programming information for this device?

The man has been searching the Internet, and it sounds like he may have had a problem.

Stupid: I can not compile the source code of a project, why it is so broken?

He assumed it was a mess, and it was too arrogant.

Wise: the source of a project can not be compiled under the Linux 6.2 version. I read the documents, but there is no Linux related issues. This is the compilation of records, I did something wrong?

He pointed out the running environment, read the FAQ, lists the errors, there is no assumption that the problem is someone else's fault, this guy is worth noting.

Silly: my motherboard has a problem, who can help me?

A hacker response might be: "yes, but also need to help you back and change a diaper? "And then the delete key.

Wise: I tried X, Y and S2464 on the Z board, and when they all failed, they tried A, B, and C. Note that I am trying to C strange symptoms, obviously something is doing so and so things, this is not expected. What are the reasons for the MP Athlon motherboard that causes such and such things? Who knows what I can do to determine the problem?

On the contrary, the man seems to be worth the answer. He has the ability to solve problems rather than wait for pie in the sky.

At the end of the question, pay attention to "give me a reply" and "please help me see what I can do to get inspired" subtle but important differences between.

In fact, the last issue is essentially derived from the August 2001 Linux kernel mailing list (lkml) on the real event, I (Eric) was asked that question, I found that the S2462 Tyan motherboard has a mysterious crash phenomenon, mail list members to provide me with the key information to solve this problem.

By the way of questioning, I gave people can chew. I managed to make it easy and attractive for the participants, as well as to show respect for the ability of the peers and to invite them to negotiate with me. Had told them that I had gone through the road, I also showed the respect for their precious time.

Later, when I thanked everyone and commented on the good experience, a member of the Linux kernel mailing list said he didn't think it was because my name was on the list, but because I got the right answer.

Hackers are very ruthless elite in some aspects. I think he is right, if I behaved like an unearned parasite, regardless of who I am will be ignored or scold. He suggested that the whole incident as a guide to other people's questions directly led to the preparation of this article.

If there is no reply

If you don't get the answer, please don't think we don't want to help you, sometimes just because the team members do not know the answer. No reply is not equal to being ignored, of course, it must be admitted that it is difficult to see the difference between the two.

In general, it will be regarded as meaningless to put the question to the question again.

There are other resources that can be sought help, usually in some of the resources that are new to the novice.

There are a number of online and local users, although they do not write any software, but they are very enthusiastic about the software. These groups are usually formed by mutual assistance and help novices.

There are a number of Business Companies to provide support services (red hat and Linuxcare are the two most famous, there are many other). Don't get frustrated because you have to pay for some money! After all, if the cylinder pad your car burned, you probably have to spend money to find a repair shop to get it right. Even if the software doesn't cost you a penny, you can't expect service support to be free.

As popular as Linux software, each developer has at least ten thousand or more users, a person can not meet the requirements of such a multi user services. Remember, even if you have to pay to get support, you have to pay far less money than you have to pay for software (and the service support for closed source software is usually a little more expensive than open source software).

How to better answer the question

A little kind of attitude. The pressure of a problem often makes people seem rude or stupid, but it's not the way it is.

In reply to a first offender. There is no need to publicly humiliate those who make mistakes, a true novice may not even know how to search or where to find FAQ.

If you're not sure, be sure to say it! A listen to the authority of the wrong reply than not even worse, do not sound like an expert to give others a fun. Be humble and honest, and give a good example to both the questioner and the fellow.

If you can't help, don't hinder. Not on the specific steps the joke, that might destroy installed user -- some poor dork will take it as a true instruction.

Exploratory questions to elicit more details. If you do well, you can learn something - you can do it too. Try to change the problem into a good problem, do not forget that we are all new.

Despite of any slackers complain loudly RTFM is legitimate, point out that the document position (even if it's just a suggestion to do a Google keyword search) will be better.

If you are determined to answer, give a good answer. When somebody is using the wrong tool or improper methods don't suggest clumsy expedient and should be recommended for better tools and re organization.

Help your community learn from problems. When replying to a good question, ask yourself "how to modify the relevant documents or FAQ documents so as not to answer the same question again? "And then send a patch to the document defender.

If you are really making a response to the study, show your skills and not just end up with results. After all, "teach a person to fish, as to teach people to fish".