|
このページはEtoJ逐語翻訳フィルタによって翻訳生成されました。 |
Copyright ? 2001,2006,2014 Eric S. Raymond, Rick Moen
| 改正 History | ||
|---|---|---|
| 改正 3.10 | 21 May 2014 | esr |
| New section on Stack 洪水. | ||
| 改正 3.9 | 23 Apr 2013 | esr |
| URL 直す／買収する，八百長をするs. | ||
| 改正 3.8 | 19 Jun 2012 | esr |
| URL 直す／買収する，八百長をする. | ||
| 改正 3.7 | 06 Dec 2010 | esr |
| Helpful hints for ESL （衆議院の）議長s. | ||
| 改正 3.7 | 02 Nov 2010 | esr |
| Several translations have disappeared. | ||
| 改正 3.6 | 19 損なう 2008 | esr |
| Minor update and new links. | ||
| 改正 3.5 | 2 Jan 2008 | esr |
| Typo 直す／買収する，八百長をする and some translation links. | ||
| 改正 3.4 | 24 損なう 2007 | esr |
| New section, "When asking about code". | ||
| 改正 3.3 | 29 Sep 2006 | esr |
| 倍のd in a good suggestion from Kai Niggemann. | ||
| 改正 3.2 | 10 Jan 2006 | esr |
| 倍のd in edits from Rick Moen. | ||
| 改正 3.1 | 28 Oct 2004 | esr |
| 文書 'Google is your friend!' | ||
| 改正 3.0 | 2 Feb 2004 | esr |
| Major 新規加入 of stuff about proper etiquette on Web 会議s. | ||
（米）棚上げする／（英）提議する of Contents
Translations: Brazilo-Portuguese Chinese (伝統的な) Czech Dutch Estonian French Georgian German Greek Hindi Hungarian Indonesion Japanese Lithuanian ポーランドの（人） Portuguese ロシアの Spanish Ukrainian Uzbek If you want to copy, mirror, translate, or excerpt this 文書, please see my copying 政策.
Many 事業／計画（する） websites link to this 文書 in their sections on how to get help. That's 罰金, it's the use we ーするつもりであるd ― but if you are a webmaster creating such a link for your 事業／計画（する） page, please 陳列する，発揮する prominently 近づく the link notice that we are not a help desk for your 事業／計画（する）!
We have learned the hard way that without such a notice, we will 繰り返して be pestered by idiots who think having published this 文書 makes it our 職業 to solve all the world's technical problems.
If you're reading this 文書 because you need help, and you walk away with the impression you can get it 直接／まっすぐに from the authors of this 文書, you are one of the idiots we are talking about. Don't ask us questions. We'll just ignore you. We are here to show you how to get help from people who 現実に know about the ソフトウェア or 金物類／武器類 you're 取引，協定ing with, but 99.9% of the time that will not be us. Unless you know for 確かな that one of the authors is an 専門家 on what you're 取引，協定ing with, leave us alone and everybody will be happier.
In the world of hackers, the 肉親，親類d of answers you get to your technical questions depends as much on the way you ask the questions as on the difficulty of developing the answer. This guide will teach you how to ask questions in a way more likely to get you a 満足な answer.
Now that use of open source has become 普及した, you can often get as good answers from other, more experienced 使用者s as from hackers. This is a Good Thing; 使用者s tend to be just a little bit more tolerant of the 肉親，親類d of 失敗s newbies often have. Still, 扱う／治療するing experienced 使用者s like hackers in the ways we recommend here will 一般に be the most 効果的な way to get useful answers out of them, too.
The first thing to understand is that hackers 現実に like hard problems and good, thought-刺激するing questions about them. If we didn't, we wouldn't be here. If you give us an 利益／興味ing question to chew on we'll be 感謝する to you; good questions are a 刺激 and a gift. Good questions help us develop our understanding, and often 明らかにする／漏らす problems we might not have noticed or thought about さもなければ. の中で hackers, “Good question!” is a strong and sincere compliment.
にもかかわらず this, hackers have a 評判 for 会合 simple questions with what looks like 敵意 or arrogance. It いつかs looks like we're reflexively rude to newbies and the ignorant. But this isn't really true.
What we are, unapologetically, is 敵意を持った to people who seem to be unwilling to think or to do their own homework before asking questions. People like that are time 沈むs ― they take without giving 支援する, and they waste time we could have spent on another question more 利益／興味ing and another person more worthy of an answer. We call people like this “losers” (and for historical 推論する／理由s we いつかs （一定の）期間 it “lusers”).
We realize that there are many people who just want to use the ソフトウェア we 令状, and who have no 利益／興味 in learning technical 詳細（に述べる）s. For most people, a computer is 単に a 道具, a means to an end; they have more important things to do and lives to live. We 認める that, and don't 推定する／予想する everyone to take an 利益／興味 in the technical 事柄s that fascinate us. にもかかわらず, our style of answering questions is tuned for people who do take such an 利益／興味 and are willing to be active 関係者s in problem-solving. That's not going to change. Nor should it; if it did, we would become いっそう少なく 効果的な at the things we do best.
We're (大部分は) volunteers. We take time out of busy lives to answer questions, and at times we're 圧倒するd with them. So we filter ruthlessly. In particular, we throw away questions from people who appear to be losers ーするために spend our question-answering time more efficiently, on 勝利者s.
If you find this 態度 obnoxious, condescending, or arrogant, check your 仮定／引き受けることs. We're not asking you to genuflect to us ― in fact, most of us would love nothing more than to を取り引きする you as an equal and welcome you into our culture, if you put in the 成果／努力 要求するd to make that possible. But it's 簡単に not efficient for us to try to help people who are not willing to help themselves. It's 承認する to be ignorant; it's not 承認する to play stupid.
So, while it isn't necessary to already be technically competent to get attention from us, it is necessary to 論証する the 肉親，親類d of 態度 that leads to competence ― 警報, thoughtful, observant, willing to be an active partner in developing a 解答. If you can't live with this sort of 差別, we 示唆する you 支払う／賃金 somebody for a 商業の support 契約 instead of asking hackers to 本人自身で 寄付する help to you.
If you decide to come to us for help, you don't want to be one of the losers. You don't want to seem like one, either. The best way to get a 早い and responsive answer is to ask it like a person with smarts, 信用／信任, and 手がかり（を与える）s who just happens to need help on one particular problem.
(改良s to this guide are welcome. You can mail suggestions to esr@thyrsus.com or 答える／応じる-自動車@linuxmafia.com. 公式文書，認める however that this 文書 is not ーするつもりであるd to be a general guide to netiquette, and we will 一般に 拒絶する suggestions that are not 特に 関係のある to eliciting useful answers in a technical 会議.)
Before asking a technical question by e-mail, or in a newsgroup, or on a website 雑談（する） board, do the に引き続いて:
Try to find an answer by searching the 古記録s of the 会議 or mailing 名簿（に載せる）／表（にあげる） you 計画（する） to 地位，任命する to.
Try to find an answer by searching the Web.
Try to find an answer by reading the 手動式の.
Try to find an answer by reading a FAQ.
Try to find an answer by 査察 or experimentation.
Try to find an answer by asking a 技術d friend.
If you're a programmer, try to find an answer by reading the source code.
When you ask your question, 陳列する，発揮する the fact that you have done these things first; this will help 設立する that you're not 存在 a lazy sponge and wasting people's time. Better yet, 陳列する，発揮する what you have learned from doing these things. We like answering questions for people who have 論証するd they can learn from the answers.
Use 策略 like doing a Google search on the text of whatever error message you get (searching Google groups 同様に as Web pages). This might 井戸／弁護士席 take you straight to 直す／買収する，八百長をする documentation or a mailing 名簿（に載せる）／表（にあげる） thread answering your question. Even if it doesn't, 説 “I googled on the に引き続いて phrase but didn't get anything that looked 約束ing” is a good thing to do in e-mail or news postings requesting help, if only because it 記録，記録的な／記録するs what searches won't help. It will also help to direct other people with 類似の problems to your thread by linking the search 条件 to what will hopefully be your problem and 決意／決議 thread.
Take your time. Do not 推定する／予想する to be able to solve a 複雑にするd problem with a few seconds of Googling. Read and understand the FAQs, sit 支援する, relax and give the problem some thought before approaching 専門家s. 信用 us, they will be able to tell from your questions how much reading and thinking you did, and will be more willing to help if you come 用意が出来ている. Don't 即時に 解雇する／砲火／射撃 your whole 兵器庫 of questions just because your first search turned up no answers (or too many).
準備する your question. Think it through. 迅速な-sounding questions get 迅速な answers, or 非，不，無 at all. The more you do to 論証する that having put thought and 成果／努力 into solving your problem before 捜し出すing help, the more likely you are to 現実に get help.
Beware of asking the wrong question. If you ask one that is based on 欠陥のある 仮定／引き受けることs, J. 無作為の Hacker is やめる likely to reply with a uselessly literal answer while thinking “Stupid question...”, and hoping the experience of getting what you asked for rather than what you needed will teach you a lesson.
Never assume you are する権利を与えるd to an answer. You are not; you aren't, after all, 支払う／賃金ing for the service. You will earn an answer, if you earn it, by asking a 相当な, 利益／興味ing, and thought-刺激するing question ― one that 暗黙に 与える／捧げるs to the experience of the community rather than 単に passively 需要・要求するing knowledge from others.
On the other 手渡す, making it （疑いを）晴らす that you are able and willing to help in the 過程 of developing the 解答 is a very good start. “Would someone 供給する a pointer?”, “What is my example 行方不明の?”, and “What 場所／位置 should I have checked?” are more likely to get answered than “Please 地位，任命する the exact 手続き I should use.” because you're making it （疑いを）晴らす that you're truly willing to 完全にする the 過程 if someone can just point you in the 権利 direction.
Be 極度の慎重さを要する in choosing where you ask your question. You are likely to be ignored, or written off as a loser, if you:
地位，任命する your question to a 会議 where it's off topic
地位，任命する a very elementary question to a 会議 where 前進するd technical questions are 推定する／予想するd, or 副／悪徳行為-versa
cross-地位，任命する to too many different newsgroups
地位，任命する a personal e-mail to somebody who is neither an 知識 of yours nor 本人自身で 責任がある solving your problem
Hackers blow off questions that are inappropriately 的d in order to try to 保護する their communications channels from 存在 溺死するd in irrelevance. You don't want this to happen to you.
The first step, therefore, is to find the 権利 会議. Again, Google and other Web-searching methods are your friend. Use them to find the 事業／計画（する） webpage most closely associated with the 金物類／武器類 or ソフトウェア giving you difficulties. Usually it will have links to a FAQ (Frequently Asked Questions) 名簿（に載せる）／表（にあげる）, and to 事業／計画（する） mailing 名簿（に載せる）／表（にあげる）s and their 古記録s. These mailing 名簿（に載せる）／表（にあげる）s are the final places to go for help, if your own 成果／努力s (含むing reading those FAQs you 設立する) do not find you a 解答. The 事業／計画（する） page may also 述べる a bug-報告（する）／憶測ing 手続き, or have a link to one; if so, follow it.
狙撃 off an e-mail to a person or 会議 which you are not familiar with is risky at best. For example, do not assume that the author of an informative webpage wants to be your 解放する／自由な 顧問. Do not make 楽観的な guesses about whether your question will be welcome ― if you're 自信のない, send it どこかよそで, or 差し控える from sending it at all.
When selecting a Web 会議, newsgroup or mailing 名簿（に載せる）／表（にあげる）, don't 信用 the 指名する by itself too far; look for a FAQ or 借り切る／憲章 to 立証する your question is on-topic. Read some of the 支援する traffic before 地位，任命するing so you'll get a feel for how things are done there. In fact, it's a very good idea to do a keyword search for words relating to your problem on the newsgroup or mailing 名簿（に載せる）／表（にあげる） 古記録s before you 地位，任命する. It may find you an answer, and if not it will help you 明確に表す a better question.
Don't shotgun-爆破 all the 利用できる help channels at once, that's like yelling and irritates people. Step through them softly.
Know what your topic is! One of the classic mistakes is asking questions about the Unix or Windows programming interface in a 会議 充てるd to a language or library or 道具 portable across both. If you don't understand why this is a 失敗, you'd be best off not asking any questions at all until you get it.
In general, questions to a 井戸／弁護士席-selected public 会議 are more likely to get useful answers than 同等（の） questions to a 私的な one. There are 多重の 推論する／理由s for this. One is 簡単に the size of the pool of 可能性のある 回答者／被告s. Another is the size of the audience; hackers would rather answer questions that educate many people than questions serving only a few.
Understandably, 技術d hackers and authors of popular ソフトウェア are already receiving more than their fair 株 of mis-的d messages. By 追加するing to the flood, you could in extreme 事例／患者s even be the straw that breaks the camel's 支援する ― やめる a few times, contributors to popular 事業／計画（する）s have 孤立した their support because collateral 損失 in the form of useless e-mail traffic to their personal accounts became unbearable.
Search, then ask on Stack 交流
In 最近の years, the Stack 交流 community of 場所／位置s has 現れるd as a major 資源 for answering technical and other questions and is even the preferred 会議 for many open-source 事業／計画（する）s.
Start with a Google search before looking at Stack 交流; Google 索引s it in real time. There's a very good chance someone has already asked a 類似の question, and the Stack 交流 場所／位置s are often 近づく the 最高の，を越す of the search results. If you didn't find anything through Google, search again on the 明確な／細部 場所／位置 most 関連した to your question (see below). Searching with tags can help 狭くする 負かす／撃墜する the results.
If you still didn't find anything, 地位，任命する your question on the one 場所／位置 where it's most on-topic. Use the formatting 道具s, 特に for code, and 追加する tags that are 関係のある to the 実体 of your question (特に the 指名する of the programming language, operating system, or library you're having trouble with). If a commenter asks you for more （警察などへの）密告，告訴（状）, edit your main 地位，任命する to 含む it. If any answer is helpful, click the up arrow to upvote it; if an answer gives a 解答 to your problem, click the check under the 投票（する）ing arrows to 受託する it as 訂正する.
Stack 交流 has grown to over 100 場所／位置s, but here are the most likely 候補者s:
最高の 使用者 is for questions about general-目的 計算するing. If your question isn't about code or programs that you talk to only over a 網状組織 関係, it probably goes here.
Stack 洪水 is for questions about programming.
Server Fault is for questions about server and 網状組織 行政.
Several 事業／計画（する）s have their own 明確な／細部 場所／位置s, 含むing Android, Ubuntu, TeX/LaTeX, and SharePoint. Check the Stack 交流 場所／位置 for an up-to-date 名簿（に載せる）／表（にあげる）.
Your 地元の 使用者 group, or your Linux 配当, may advertise a Web 会議 or IRC channel where newbies can get help. (In 非，不，無-English-speaking countries newbie 会議s are still more likely to be mailing 名簿（に載せる）／表（にあげる）s.) These are good first places to ask, 特に if you think you may have tripped over a 比較して simple or ありふれた problem. An advertised IRC channel is an open 招待 to ask questions there and often get answers in real time.
In fact, if you got the program that is giving you problems from a Linux 配当 (as is ありふれた today), it may be better to ask in the distro's 会議/名簿（に載せる）／表（にあげる） before trying the program's 事業／計画（する） 会議/名簿（に載せる）／表（にあげる）. The 事業／計画（する）'s hackers may just say, “use our build”.
Before 地位，任命するing to any Web 会議, check if it has a Search feature. If it does, try a couple of keyword searches for something like your problem; it just might help. If you did a general Web search before (as you should have), search the 会議 anyway; your Web-wide search engine might not have all of this 会議 索引d recently.
There is an 増加するing 傾向 for 事業／計画（する）s to do 使用者 support over a Web 会議 or IRC channel, with e-mail reserved more for 開発 traffic. So look for those channels first when 捜し出すing 事業／計画（する）-明確な／細部 help.
In IRC, it's probably best not to 捨てる a long problem description on the channel first thing; some people 解釈する／通訳する this as channel-flooding. Best to utter a one-line problem description in a way pitched to start a conversation on the channel.
When a 事業／計画（する） has a 開発 mailing 名簿（に載せる）／表（にあげる）, 令状 to the mailing 名簿（に載せる）／表（にあげる）, not to individual developers, even if you believe you know who can best answer your question. Check the documentation of the 事業／計画（する） and its homepage for the 演説（する）／住所 of a 事業／計画（する） mailing 名簿（に載せる）／表（にあげる）, and use it. There are several good 推論する／理由s for this 政策:
Any question good enough to be asked of one developer will also be of value to the whole group. Contrariwise, if you 嫌疑者，容疑者／疑う your question is too dumb for a mailing 名簿（に載せる）／表（にあげる）, it's not an excuse to 悩ます individual developers.
Asking questions on the 名簿（に載せる）／表（にあげる） 分配するs 負担 の中で developers. The individual developer (特に if he's the 事業／計画（する） leader) may be too busy to answer your questions.
Most mailing 名簿（に載せる）／表（にあげる）s are 古記録d and the 古記録s are 索引d by search engines. If you ask your question on-名簿（に載せる）／表（にあげる） and it is answered, a 未来 querent could find your question and the answer on the Web instead of asking it again.
If 確かな questions are seen to be asked often, developers can use that （警察などへの）密告，告訴（状） to 改善する the documentation or the ソフトウェア itself to be いっそう少なく 混乱させるing. But if those questions are asked in 私的な, nobody has the 完全にする picture of what questions are asked most often.
If a 事業／計画（する） has both a “使用者” and a “developer” (or “hacker”) mailing 名簿（に載せる）／表（にあげる） or Web 会議, and you are not 切り開く／タクシー／不正アクセスing on the code, ask in the “使用者” 名簿（に載せる）／表（にあげる）/会議. Do not assume that you will be welcome on the developer 名簿（に載せる）／表（にあげる）, where they're likely to experience your question as noise 混乱に陥れる／中断させるing their developer traffic.
However, if you are sure your question is 非，不，無-trivial, and you get no answer in the “使用者” 名簿（に載せる）／表（にあげる）/会議 for several days, try the “developer” one. You would be 井戸／弁護士席 advised to lurk there for a few daysor at least review the last few days of 古記録d messages, to learn the 地元の folkways before 地位，任命するing (現実に this is good advice on any 私的な or 半分-私的な 名簿（に載せる）／表（にあげる）).
If you cannot find a 事業／計画（する）'s mailing 名簿（に載せる）／表（にあげる） 演説（する）／住所, but only see the 演説（する）／住所 of the maintainer of the 事業／計画（する）, go ahead and 令状 to the maintainer. But even in that 事例／患者, don't assume that the mailing 名簿（に載せる）／表（にあげる） doesn't 存在する. について言及する in your e-mail that you tried and could not find the appropriate mailing 名簿（に載せる）／表（にあげる）. Also について言及する that you don't 反対する to having your message 今後d to other people. (Many people believe that 私的な e-mail should remain 私的な, even if there is nothing secret in it. By 許すing your message to be 今後d you give your 特派員 a choice about how to 扱う your e-mail.)
On mailing 名簿（に載せる）／表（にあげる）s, newsgroups or Web 会議s, the 支配する header is your golden 適切な時期 to attract qualified 専門家s' attention in around 50 characters or より小数の. Don't waste it on babble like “Please help me” (let alone “PLEASE HELP ME!!!!”; messages with 支配するs like that get discarded by reflex). Don't try to impress us with the depth of your anguish; use the space for a 最高の-concise problem description instead.
One good 条約 for 支配する headers, used by many tech support organizations, is “反対する - deviation”. The “反対する” part 明示するs what thing or group of things is having a problem, and the “deviation” part 述べるs the deviation from 推定する／予想するd 行為.
HELP! ビデオ doesn't work 適切に on my laptop!
X.org 6.8.1 misshapen mouse cursor, Fooware MV1005 vid. chipset
X.org 6.8.1 mouse cursor on Fooware MV1005 vid. chipset - is misshapen
The 過程 of 令状ing an “反対する-deviation” description will help you 組織する your thinking about the problem in more 詳細（に述べる）. What is 影響する／感情d? Just the mouse cursor or other graphics too? Is this 明確な／細部 to the X.org 見解／翻訳／版 of X? To 見解／翻訳／版 6.8.1? Is this 明確な／細部 to Fooware ビデオ chipsets? To model MV1005? A hacker who sees the result can すぐに understand what it is that you are having a problem with and the problem you are having, at a ちらりと見ること.
More 一般に, imagine looking at the 索引 of an 古記録 of questions, with just the 支配する lines showing. Make your 支配する line 反映する your question 井戸／弁護士席 enough that the next person searching the 古記録 with a question 類似の to yours will be able to follow the thread to an answer rather than 地位，任命するing the question again.
If you ask a question in a reply, be sure to change the 支配する line to 示す that you're asking a question. A 支配する line that looks like “Re: 実験（する）” or “Re: new bug” is いっそう少なく likely to attract useful 量s of attention. Also, pare quotation of previous messages to the 最小限 一貫した with 手がかり（を与える）ing in new readers.
Do not 簡単に 攻撃する，衝突する reply to a 名簿（に載せる）／表（にあげる） message ーするために start an 完全に new thread. This will 限界 your audience. Some mail readers, like mutt, 許す the 使用者 to sort by thread and then hide messages in a thread by 倍のing the thread. Folks who do that will never see your message.
Changing the 支配する is not 十分な. Mutt, and probably other mail readers, looks at other （警察などへの）密告，告訴（状） in the e-mail's headers to 割り当てる it to a thread, not the 支配する line. Instead start an 完全に new e-mail.
On Web 会議s the 支配するs of good practice are わずかに different, because messages are usually much more tightly bound to 明確な／細部 discussion threads and often invisible outside those threads. Changing the 支配する when asking a question in reply is not 必須の. Not all 会議s even 許す separate 支配する lines on replies, and nearly nobody reads them when they do. However, asking a question in a reply is a 疑わしい practice in itself, because it will only be seen by those who are watching this thread. So, unless you are sure you want to ask only the people 現在／一般に active in the thread, start a new one.
Finishing your query with “Please send your reply to... ” makes it やめる ありそうもない you will get an answer. If you can't be bothered to take even the few seconds 要求するd to 始める，決める up a 訂正する Reply-To header in your mail スパイ／執行官, we can't be bothered to take even a few seconds to think about your problem. If your mail program doesn't 許す this, get a better mail program. If your operating system doesn't support any e-mail programs that 許す this, get a better operating system.
In Web 会議s, asking for a reply by e-mail is 完全な rude, unless you believe the （警察などへの）密告，告訴（状） may be 極度の慎重さを要する (and somebody will, for some unknown 推論する／理由, let you but not the whole 会議 know it). If you want an e-mail copy when somebody replies in the thread, request that the Web 会議 send it; this feature is supported almost everywhere under 選択s like “watch this thread”, “send e-mail on answers”, etc.
We've 設立する by experience that people who are careless and sloppy writers are usually also careless and sloppy at thinking and coding (often enough to bet on, anyway). Answering questions for careless and sloppy thinkers is not rewarding; we'd rather spend our time どこかよそで.
So 表明するing your question 明確に and 井戸／弁護士席 is important. If you can't be bothered to do that, we can't be bothered to 支払う／賃金 attention. Spend the extra 成果／努力 to polish your language. It doesn't have to be stiff or formal ― in fact, hacker culture values informal, slangy and humorous language used with precision. But it has to be 正確な; there has to be some 指示，表示する物 that you're thinking and 支払う／賃金ing attention.
（一定の）期間, punctuate, and 出資する 正確に. Don't 混乱させる “its” with “it's”, “loose” with “lose”, or “discrete” with “控えめの”. Don't TYPE IN ALL CAPS; this is read as shouting and considered rude. (All-smalls is only わずかに いっそう少なく annoying, as it's difficult to read. Alan Cox can get away with it, but you can't.)
More 一般に, if you 令状 like a 半分-literate boob you will very likely be ignored. So don't use instant-messaging shortcuts. （一定の）期間ing "you" as "u" makes you look like a 半分-literate boob to save two entire keystrokes. Worse: 令状ing like a l33t script kiddie hax0r is the 絶対の kiss of death and 保証（人）s you will receive nothing but stony silence (or, at best, a heaping helping of 軽蔑（する） and sarcasm) in return.
If you are asking questions in a 会議 that does not use your native language, you will get a 限られた／立憲的な 量 of slack for （一定の）期間ing and grammar errors ― but no extra slack at all for laziness (and yes, we can usually 位置／汚点／見つけ出す that difference). Also, unless you know what your 回答者／被告's languages are, 令状 in English. Busy hackers tend to 簡単に 紅潮／摘発する questions in languages they don't understand, and English is the working language of the Internet. By 令状ing in English you 最小限に減らす your chances that your question will be discarded unread.
If you are 令状ing in English but it is a second language for you, it is good form to 警報 可能性のある 回答者／被告s to 可能性のある language difficulties and 選択s for getting around them. Examples:
English is not my native language; please excuse typing errors.
If you speak $LANGUAGE, please email/PM me; I may need 援助 translating my question.
I am familiar with the technical 条件, but some slang 表現s and idioms are difficult for me.
I've 地位，任命するd my question in $LANGUAGE and English. I'll be glad to translate 返答s, if you only use one or the other.
If you make your question artificially hard to read, it is more likely to be passed over in 好意 of one that isn't. So:
Send plain text mail, not HTML. (It's not hard to turn off HTML.)
MIME attachments are usually 承認する, but only if they are real content (such as an 大（公）使館員d source とじ込み／提出する or patch), and not 単に boilerplate 生成するd by your mail （弁護士の）依頼人 (such as another copy of your message).
Don't send e-mail in which entire paragraphs are 選び出す／独身 multiply-wrapped lines. (This makes it too difficult to reply to just part of the message.) Assume that your 回答者／被告s will be reading mail on 80-character-wide text 陳列する，発揮するs and 始める，決める your line 包む accordingly, to something いっそう少なく than 80.
However, do not 包む data (such as スピードを出す／記録につける とじ込み／提出する 捨てるs or 開会／開廷／会期 transcripts) at any 直す／買収する，八百長をするd column width. Data should be 含むd as-is, so 回答者／被告s can have 信用／信任 that they are seeing what you saw.
Don't send MIME 引用するd-Printable encoding to an English-language 会議. This encoding can be necessary when you're 地位，任命するing in a language ASCII doesn't cover, but many e-mail スパイ／執行官s don't support it. When they break, all those =20 glyphs scattered through the text are ugly and distracting ― or may 活発に 破壊行為 the semantics of your text.
Never, ever 推定する／予想する hackers to be able to read の近くにd proprietary 文書 判型s like Microsoft Word or Excel. Most hackers 反応する to these about 同様に as you would to having a pile of steaming pig manure 捨てるd on your doorstep. Even when they can 対処する, they resent having to do so.
If you're sending e-mail from a Windows machine, turn off Microsoft's problematic “Smart 引用するs” feature (From 道具s > AutoCorrect 選択s, （疑いを）晴らす the smart 引用するs checkbox under AutoFormat As You Type.). This is so you'll 避ける ぱらぱら雨ing garbage characters through your mail.
In Web 会議s, do not 乱用 “smiley” and “HTML” features (when they are 現在の). A smiley or two is usually 承認する, but colored fancy text tends to make people think you are lame. 本気で overusing smileys and color and fonts will make you come off like a giggly teenage girl, which is not 一般に a good idea unless you are more 利益／興味d in sex than answers.
If you're using a graphical-使用者-interface mail （弁護士の）依頼人 such as Netscape Messenger, MS 見通し, or their ilk, beware that it may 侵害する／違反する these 支配するs when used with its default settings. Most such （弁護士の）依頼人s have a menu-based “見解（をとる） Source” 命令（する）. Use this on something in your sent-mail folder, 立証するing sending of plain text without unnecessary 大（公）使館員d crud.
述べる the symptoms of your problem or bug carefully and 明確に.
述べる the 環境 in which it occurs (machine, OS, 使用／適用, whatever). 供給する your vendor's 配当 and 解放（する） level (e.g.: “Fedora 核心 7”, “Slackware 9.1”, etc.).
述べる the 研究 you did to try and understand the problem before you asked the question.
述べる the diagnostic steps you took to try and pin 負かす／撃墜する the problem yourself before you asked the question.
述べる any かもしれない 関連した 最近の changes in your computer or ソフトウェア configuration.
If at all possible, 供給する a way to 再生する the problem in a controlled 環境.
Do the best you can to 心配する the questions a hacker will ask, and answer them in 前進する in your request for help.
Giving hackers the ability to 再生する the problem in a controlled 環境 is 特に important if you are 報告（する）／憶測ing something you think is a bug in code. When you do this, your 半端物s of getting a useful answer and the 速度(を上げる） with which you are likely to get that answer both 改善する tremendously.
Simon Tatham has written an excellent essay する権利を与えるd How to 報告（する）／憶測 Bugs 効果的に. I 堅固に recommend that you read it.
You need to be 正確な and informative. This end is not served by 簡単に ダンピング 抱擁する 容積／容量s of code or data into a help request. If you have a large, 複雑にするd 実験（する） 事例／患者 that is breaking a program, try to 削減する it and make it as small as possible.
This is useful for at least three 推論する／理由s. One: 存在 seen to 投資する 成果／努力 in 簡単にするing the question makes it more likely you'll get an answer, Two: 簡単にするing the question makes it more likely you'll get a useful answer. Three: In the 過程 of 精製するing your bug 報告（する）／憶測, you may develop a 直す／買収する，八百長をする or workaround yourself.
When you are having problems with a piece of ソフトウェア, don't （人命などを）奪う，主張する you have 設立する a bug unless you are very, very sure of your ground. Hint: unless you can 供給する a source-code patch that 直す／買収する，八百長をするs the problem, or a regression 実験（する） against a previous 見解／翻訳／版 that 論証するs incorrect 行為, you are probably not sure enough. This 適用するs to webpages and documentation, too; if you have 設立する a documentation “bug”, you should 供給（する） 交替／補充 text and which pages it should go on.
Remember, there are many other 使用者s that are not experiencing your problem. さもなければ you would have learned about it while reading the documentation and searching the Web (you did do that before complaining, didn't you?). This means that very probably it is you who are doing something wrong, not the ソフトウェア.
The people who wrote the ソフトウェア work very hard to make it work 同様に as possible. If you （人命などを）奪う，主張する you have 設立する a bug, you'll be impugning their competence, which may 感情を害する／違反する some of them even if you are 訂正する. It's 特に undiplomatic to yell “bug” in the 支配する line.
When asking your question, it is best to 令状 as though you assume you are doing something wrong, even if you are 個人として pretty sure you have 設立する an actual bug. If there really is a bug, you will hear about it in the answer. Play it so the maintainers will want to わびる to you if the bug is real, rather than so that you will 借りがある them an 陳謝 if you have messed up.
Some people who get that they shouldn't behave rudely or arrogantly, 需要・要求するing an answer, 退却／保養地 to the opposite extreme of grovelling. “I know I'm just a pathetic newbie loser, but...”. This is distracting and unhelpful. It's 特に annoying when it's coupled with vagueness about the actual problem.
Don't waste your time, or ours, on 天然のまま 大主教 politics. Instead, 現在の the background facts and your question as 明確に as you can. That is a better way to position yourself than by grovelling.
いつかs Web 会議s have separate places for newbie questions. If you feel you do have a newbie question, just go there. But don't grovel there either.
It's not useful to tell hackers what you think is 原因（となる）ing your problem. (If your diagnostic theories were such hot stuff, would you be 協議するing others for help?) So, make sure you're telling them the raw symptoms of what goes wrong, rather than your 解釈／通訳s and theories. Let them do the 解釈／通訳 and diagnosis. If you feel it's important to 明言する／公表する your guess, 明確に label it as such and 述べる why that answer isn't working for you.
I'm getting 支援する-to-支援する SIG11 errors on kernel 収集するs, and 嫌疑者，容疑者／疑う a hairline 割れ目 on one of the motherboard traces. What's the best way to check for those?
My home-built K6/233 on an FIC-PA2007 motherboard (VIA Apollo VP2 chipset) with 256MB Corsair PC133 SDRAM starts getting たびたび（訪れる） SIG11 errors about 20 minutes after 力／強力にする-on during the course of kernel 収集するs, but never in the first 20 minutes. Rebooting doesn't 再開する the clock, but 力／強力にするing 負かす／撃墜する 夜通し does. Swapping out all RAM didn't help. The 関連した part of a typical 収集する 開会／開廷／会期 スピードを出す／記録につける follows.
Since the 先行する point seems to be a 堅い one for many people to しっかり掴む, here's a phrase to remind you: "All diagnosticians are from Missouri." That US 明言する／公表する's 公式の／役人 motto is "Show me" (earned in 1899, when 下院議員 Willard D. Vandiver said "I come from a country that raises corn and cotton and cockleburs and 民主党員s, and frothy eloquence neither 納得させるs nor 満足させるs me. I'm from Missouri. You've got to show me.") In diagnosticians' 事例／患者, it's not a 事柄 of 懐疑心, but rather a literal, 機能の need to see whatever is as の近くに as possible to the same raw 証拠 that you see, rather than your surmises and 要約s. Show us.
The 手がかり（を与える）s most useful in 人物／姿／数字ing out something that went wrong often 嘘（をつく） in the events すぐに 事前の. So, your account should 述べる 正確に what you did, and what the machine and ソフトウェア did, 主要な up to the 爆発. In the 事例／患者 of 命令（する）-line 過程s, having a 開会／開廷／会期 スピードを出す／記録につける (e.g., using the script 公共事業（料金）／有用性) and 引用するing the 関連した twenty or so lines is very useful.
If the program that blew up on you has diagnostic 選択s (such as -v for verbose), try to select 選択s that will 追加する useful debugging （警察などへの）密告，告訴（状） to the transcript. Remember that more is not やむを得ず better; try to choose a debug level that will 知らせる rather than 溺死するing the reader in junk.
If your account ends up 存在 long (more than about four paragraphs), it might be useful to succinctly 明言する／公表する the problem up 最高の，を越す, then follow with the chronological tale. That way, hackers will know what to watch for in reading your account.
If you are trying to find out how to do something (as …に反対するd to 報告（する）／憶測ing a bug), begin by 述べるing the goal. Only then 述べる the particular step に向かって it that you are 封鎖するd on.
Often, people who need technical help have a high-level goal in mind and get stuck on what they think is one particular path に向かって the goal. They come for help with the step, but don't realize that the path is wrong. It can take 相当な 成果／努力 to get past this.
How do I get the color-picker on the FooDraw program to take a hexadecimal RGB value?
I'm trying to 取って代わる the color （米）棚上げする／（英）提議する on an image with values of my choosing. 権利 now the only way I can see to do this is by editing each （米）棚上げする／（英）提議する slot, but I can't get FooDraw's color picker to take a hexadecimal RGB value.
The second 見解／翻訳／版 of the question is smart. It 許すs an answer that 示唆するs a 道具 better ふさわしい to the 仕事.
Hackers believe solving problems should be a public, transparent 過程 during which a first try at an answer can and should be 訂正するd if someone more knowledgeable notices that it is incomplete or incorrect. Also, helpers get some of their reward for 存在 回答者／被告s from 存在 seen to be competent and knowledgeable by their peers.
When you ask for a 私的な reply, you are 混乱に陥れる／中断させるing both the 過程 and the reward. Don't do this. It's the 回答者／被告's choice whether to reply 個人として ― and if he or she does, it's usually because he or she thinks the question is too ill-formed or obvious to be 利益／興味ing to others.
There is one 限られた／立憲的な exception to this 支配する. If you think the question is such that you are likely to get many answers that are all closely 類似の, then the 魔法 words are “e-mail me and I'll 要約する the answers for the group”. It is courteous to try and save the mailing 名簿（に載せる）／表（にあげる） or newsgroup a flood of 大幅に 同一の postings ― but you have to keep the 約束 to 要約する.
Open-ended questions tend to be perceived as open-ended time 沈むs. Those people most likely to be able to give you a useful answer are also the busiest people (if only because they take on the most work themselves). People like that are allergic to open-ended time 沈むs, thus they tend to be allergic to open-ended questions.
You are more likely to get a useful 返答 if you are explicit about what you want 回答者／被告s to do (供給する pointers, send code, check your patch, whatever). This will 焦点（を合わせる） their 成果／努力 and 暗黙に put an upper bound on the time and energy a 回答者／被告 must 配分する to helping you. This is good.
To understand the world the 専門家s live in, think of 専門的知識 as an abundant 資源 and time to 答える／応じる as a 不十分な one. The いっそう少なく of a time かかわり合い you 暗黙に ask for, the more likely you are to get an answer from someone really good and really busy.
So it is useful to でっちあげる，人を罪に陥れる your question to 最小限に減らす the time かかわり合い 要求するd for an 専門家 to field it ― but this is often not the same thing as 簡単にするing the question. Thus, for example, “Would you give me a pointer to a good explanation of X?” is usually a smarter question than “Would you explain X, please?”. If you have some 機能不全ing code, it is usually smarter to ask for someone to explain what's wrong with it than it is to ask someone to 直す／買収する，八百長をする it.
Don't ask others to debug your broken code without giving a hint what sort of problem they should be searching for. 地位，任命するing a few hundred lines of code, 説 "it doesn't work", will get you ignored. 地位，任命するing a dozen lines of code, 説 "after line 7 I was 推定する／予想するing to see <x>, but <y> occurred instead" is much more likely to get you a 返答.
The most 効果的な way to be 正確な about a code problem is to 供給する a 極小の bug-論証するing 実験（する） 事例／患者. What's a 極小の 実験（する） 事例／患者? It's an illustration of the problem; just enough code to 展示（する） the 望ましくない 行為 and no more. How do you make a 極小の 実験（する） 事例／患者? If you know what line or section of code is producing the problematic 行為, make a copy of it and 追加する just enough supporting code to produce a 完全にする example (i.e. enough that the source is 許容できる to the compiler/interpreter/whatever 使用／適用 過程s it). If you can't 狭くする it 負かす／撃墜する to a particular section, make a copy of the source and start 除去するing chunks that don't 影響する／感情 the problematic 行為. The smaller your 極小の 実験（する） 事例／患者 is, the better (see the section called “容積／容量 is not precision”).
生成するing a really small 極小の 実験（する） 事例／患者 will not always be possible, but trying to is good discipline. It may help you learn what you need to solve the problem on your own ― and even when it doesn't, hackers like to see that you have tried. It will make them more 協同組合.
If you 簡単に want a code review, say as much up 前線, and be sure to について言及する what areas you think might 特に need review and why.
Hackers are good at spotting homework questions; most of us have done them ourselves. Those questions are for you to work out, so that you will learn from the experience. It is 承認する to ask for hints, but not for entire 解答s.
If you 嫌疑者，容疑者／疑う you have been passed a homework question, but can't solve it anyway, try asking in a 使用者 group 会議 or (as a last 訴える手段／行楽地) in a “使用者” 名簿（に載せる）／表（にあげる）/会議 of a 事業／計画（する）. While the hackers will 位置／汚点／見つけ出す it, some of the 前進するd 使用者s may at least give you a hint.
Resist the 誘惑 to の近くに your request for help with semantically-null questions like “Can anyone help me?” or “Is there an answer?” First: if you've written your problem description halfway competently, such tacked-on questions are at best superfluous. Second: because they are superfluous, hackers find them annoying ― and are likely to return 論理（学）上 impeccable but dismissive answers like “Yes, you can be helped” and “No, there is no help for you.”
In general, asking yes-or-no questions is a good thing to 避ける unless you want a yes-or-no answer.
That's your problem, not ours. （人命などを）奪う，主張するing 緊急 is very likely to be 反対する-生産力のある: most hackers will 簡単に 削除する such messages as rude and selfish 試みる／企てるs to elicit 即座の and special attention. その上に, the word '緊急の' (and other 類似の 試みる／企てるs to 得る，とらえる attention in the 支配する line) often 誘発する／引き起こすs spam filters - your ーするつもりであるd 受取人s might never see it at all!
There is one 半分-exception. It can be 価値（がある） について言及するing if you're using the program in some high-profile place, one that the hackers will get excited about; in such a 事例／患者, if you're under time 圧力, and you say so politely, people may get 利益／興味d enough to answer faster.
This is a very risky thing to do, however, because the hackers' metric for what is exciting probably 異なるs from yours. 地位，任命するing from the International Space 駅／配置する would qualify, for example, but 地位，任命するing on に代わって of a feel-good charitable or political 原因（となる） would almost certainly not. In fact, 地位，任命するing “緊急の: Help me save the fuzzy baby 調印（する）s!” will reliably get you shunned or 炎上d even by hackers who think fuzzy baby 調印（する）s are important.
If you find this mysterious, re-read the 残り／休憩（する） of this how-to 繰り返して until you understand it before 地位，任命するing anything at all.
Be courteous. Use “Please” and “Thanks for your attention” or “Thanks for your consideration”. Make it （疑いを）晴らす you 高く評価する／（相場などが）上がる the time people spend helping you for 解放する／自由な.
To be honest, this isn't as important as (and cannot 代用品，人 for) 存在 grammatical, （疑いを）晴らす, 正確な and descriptive, 避けるing proprietary 判型s etc.; hackers in general would rather get somewhat brusque but technically sharp bug 報告（する）／憶測s than polite vagueness. (If this puzzles you, remember that we value a question by what it teaches us.)
However, if you've got your technical ducks in a 列／漕ぐ／騒動, politeness does 増加する your chances of getting a useful answer.
(We must 公式文書，認める that the only serious 反対 we've received from 退役軍人 hackers to this HOWTO is with 尊敬（する）・点 to our previous 推薦 to use “Thanks in 前進する”. Some hackers feel this connotes an 意向 not to thank anybody afterwards. Our 推薦 is to either say “Thanks in 前進する” first and thank 回答者／被告s afterwards, or 表明する 儀礼 in a different way, such as by 説 “Thanks for your attention” or “Thanks for your consideration”.)
Send a 公式文書，認める after the problem has been solved to all who helped you; let them know how it （機の）カム out and thank them again for their help. If the problem attracted general 利益／興味 in a mailing 名簿（に載せる）／表（にあげる） or newsgroup, it's appropriate to 地位，任命する the followup there.
Optimally, the reply should be to the thread started by the 初めの question 地位，任命するing, and should have ‘FIXED’, ‘RESOLVED’ or an 平等に obvious tag in the 支配する line. On mailing 名簿（に載せる）／表（にあげる）s with 急速な／放蕩な turnaround, a 可能性のある 回答者／被告 who sees a thread about “Problem X” ending with “Problem X - FIXED” knows not to waste his/her time even reading the thread (unless (s)he 本人自身で finds Problem X 利益／興味ing) and can therefore use that time solving a different problem.
Your followup doesn't have to be long and 伴う／関わるd; a simple “Howdy ― it was a failed 網状組織 cable! Thanks, everyone. - 法案” would be better than nothing. In fact, a short and 甘い 要約 is better than a long dissertation unless the 解答 has real technical depth. Say what 活動／戦闘 solved the problem, but you need not replay the whole troubleshooting sequence.
For problems with some depth, it is appropriate to 地位，任命する a 要約 of the troubleshooting history. 述べる your final problem 声明. 述べる what worked as a 解答, and 示す avoidable blind alleys after that. The blind alleys should come after the 訂正する 解答 and other 要約 構成要素, rather than turning the follow-up into a 探偵，刑事 story. 指名する the 指名するs of people who helped you; you'll make friends that way.
Besides 存在 courteous and informative, this sort of followup will help others searching the 古記録 of the mailing-名簿（に載せる）／表（にあげる）/newsgroup/会議 to know 正確に／まさに which 解答 helped you and thus may also help them.
Last, and not least, this sort of followup helps everybody who 補助装置d feel a 満足させるing sense of 終結 about the problem. If you are not a techie or hacker yourself, 信用 us that this feeling is very important to the gurus and 専門家s you tapped for help. Problem narratives that 追跡する off into 未解決の nothingness are 失望させるing things; hackers itch to see them 解決するd. The 好意／親善 that scratching that itch earns you will be very, very helpful to you next time you need to 提起する／ポーズをとる a question.
Consider how you might be able to 妨げる others from having the same problem in the 未来. Ask yourself if a documentation or FAQ patch would help, and if the answer is yes send that patch to the maintainer.
の中で hackers, this sort of good followup 行為 is 現実に more important than 従来の politeness. It's how you get a 評判 for playing 井戸／弁護士席 with others, which can be a very 価値のある 資産.
There is an 古代の and hallowed tradition: if you get a reply that reads “RTFM”, the person who sent it thinks you should have Read The Fucking 手動式の. He or she is almost certainly 権利. Go read it.
RTFM has a younger 親族. If you get a reply that reads “STFW”, the person who sent it thinks you should have Searched The Fucking Web. He or she is almost certainly 権利. Go search it. (The milder 見解／翻訳／版 of this is when you are told “Google is your friend!”)
In Web 会議s, you may also be told to search the 会議 古記録s. In fact, someone may even be so 肉親，親類d as to 供給する a pointer to the previous thread where this problem was solved. But do not rely on this consideration; do your 古記録-searching before asking.
Often, the person telling you to do a search has the 手動式の or the web page with the （警察などへの）密告，告訴（状） you need open, and is looking at it as he or she types. These replies mean that the responder thinks (a) the （警察などへの）密告，告訴（状） you need is 平易な to find, and (b) you will learn more if you 捜し出す out the （警察などへの）密告，告訴（状） than if you have it spoon-fed to you.
You shouldn't be 感情を害する／違反するd by this; by hacker 基準s, your 回答者／被告 is showing you a rough 肉親，親類d of 尊敬（する）・点 簡単に by not ignoring you. You should instead be thankful for this grandmotherly 親切.
If you don't understand the answer, do not すぐに bounce 支援する a 需要・要求する for 解明. Use the same 道具s that you used to try and answer your 初めの question (手動式のs, FAQs, the Web, 技術d friends) to understand the answer. Then, if you still need to ask for 解明, 展示（する） what you have learned.
For example, suppose I tell you: “It sounds like you've got a stuck zentry; you'll need to （疑いを）晴らす it.” Then: here's a bad followup question: “What's a zentry?” Here's a good followup question: “承認する, I read the man page and zentries are only について言及するd under the -z and -p switches. Neither of them says anything about （疑いを）晴らすing zentries. Is it one of these or am I 行方不明の something here?”
Much of what looks like rudeness in hacker circles is not ーするつもりであるd to give 罪／違反. Rather, it's the 製品 of the direct, 削減（する）-through-the-bullshit communications style that is natural to people who are more 関心d about solving problems than making others feel warm and fuzzy.
When you perceive rudeness, try to 反応する calmly. If someone is really 事実上の／代理 out, it is very likely a 上級の person on the 名簿（に載せる）／表（にあげる） or newsgroup or 会議 will call him or her on it. If that doesn't happen and you lose your temper, it is likely that the person you lose it at was behaving within the hacker community's norms and you will be considered at fault. This will 傷つける your chances of getting the （警察などへの）密告，告訴（状） or help you want.
On the other 手渡す, you will occasionally run across rudeness and posturing that is やめる gratuitous. The flip-味方する of the above is that it is 許容できる form to 激突する real 違反者／犯罪者s やめる hard, dissecting their misbehavior with a sharp 言葉の scalpel. Be very, very sure of your ground before you try this, however. The line between 訂正するing an incivility and starting a pointless flamewar is thin enough that hackers themselves not infrequently 失敗 across it; if you are a newbie or an 部外者, your chances of 避けるing such a 失敗 are low. If you're after （警察などへの）密告，告訴（状） rather than entertainment, it's better to keep your fingers off the keyboard than to 危険 this.
(Some people 主張する that many hackers have a 穏やかな form of autism or Asperger's Syndrome, and are 現実に 行方不明の some of the brain circuitry that lubricates “normal” human social interaction. This may or may not be true. If you are not a hacker yourself, it may help you 対処する with our eccentricities if you think of us as 存在 brain-損失d. Go 権利 ahead. We won't care; we like 存在 whatever it is we are, and 一般に have a healthy 懐疑心 about 臨床の labels.)
Jeff Bigler's 観察s about tact filters are also 関連した and 価値（がある） reading.
In the next section, we'll talk about a different 問題／発行する; the 肉親，親類d of “rudeness” you'll see when you misbehave.
半端物s are you'll screw up a few times on hacker community 会議s ― in ways 詳細（に述べる）d in this article, or 類似の. And you'll be told 正確に／まさに how you screwed up, かもしれない with colourful asides. In public.
When this happens, the worst thing you can do is whine about the experience, （人命などを）奪う，主張する to have been 口頭で 強襲，強姦d, 需要・要求する 陳謝s, 叫び声をあげる, 持つ／拘留する your breath, 脅す 訴訟s, complain to people's 雇用者s, leave the 洗面所 seat up, etc. Instead, here's what you do:
Get over it. It's normal. In fact, it's healthy and appropriate.
Community 基準s do not 持続する themselves: They're 持続するd by people 活発に 適用するing them, visibly, in public. Don't whine that all 批評 should have been 伝えるd 経由で 私的な e-mail: That's not how it 作品. Nor is it useful to 主張する you've been 本人自身で 侮辱d when someone comments that one of your （人命などを）奪う，主張するs was wrong, or that his 見解（をとる）s 異なる. Those are loser 態度s.
There have been hacker 会議s where, out of some misguided sense of hyper-儀礼, 関係者s are banned from 地位，任命するing any fault-finding with another's 地位，任命するs, and told “Don't say anything if you're unwilling to help the 使用者.” The resulting 出発 of clueful 関係者s to どこかよそで 原因（となる）s them to descend into meaningless babble and become useless as technical 会議s.
Exaggeratedly “friendly” (in that fashion) or useful: 選ぶ one.
Remember: When that hacker tells you that you've screwed up, and (no 事柄 how gruffly) tells you not to do it again, he's 事実上の／代理 out of 関心 for (1) you and (2) his community. It would be much easier for him to ignore you and filter you out of his life. If you can't manage to be 感謝する, at least have a little dignity, don't whine, and don't 推定する／予想する to be 扱う／治療するd like a 壊れやすい doll just because you're a newcomer with a theatrically hypersensitive soul and delusions of entitlement.
いつかs people will attack you 本人自身で, 炎上 without an 明らかな 推論する／理由, etc., even if you don't screw up (or have only screwed up in their imagination). In this 事例／患者, complaining is the way to really screw up.
These flamers are either lamers who don't have a 手がかり（を与える） but believe themselves to be 専門家s, or would-be psychologists 実験（する）ing whether you'll screw up. The other readers either ignore them, or find ways to を取り引きする them on their own. The flamers' 行為 creates problems for themselves, which don't have to 関心 you.
Don't let yourself be drawn into a flamewar, either. Most 炎上s are best ignored ― after you've checked whether they are really 炎上s, not pointers to the ways in which you have screwed up, and not cleverly ciphered answers to your real question (this happens 同様に).
Here are some classic stupid questions, and what hackers are thinking when they don't answer them.
Q: | Where can I find program or 資源 X? |
A: | The same place I'd find it, fool ― at the other end of a web search. Ghod, doesn't everybody know how to use Google yet? |
Q: | How can I use X to do Y? |
A: | If what you want is to do Y, you should ask that question without pre-supposing the use of a method that may not be appropriate. Questions of this form often 示す a person who is not 単に ignorant about X, but 混乱させるd about what problem Y they are solving and too fixated on the 詳細（に述べる）s of their particular 状況／情勢. It is 一般に best to ignore such people until they define their problem better. |
Q: | How can I configure my 爆撃する 誘発する? |
A: | If you're smart enough to ask this question, you're smart enough to RTFM and find out yourself. |
Q: | Can I 変える an AcmeCorp 文書 into a TeX とじ込み／提出する using the Bass-o-matic とじ込み／提出する converter? |
A: | Try it and see. If you did that, you'd (a) learn the answer, and (b) stop wasting my time. |
Q: | My {program, configuration, SQL 声明} doesn't work |
A: | This is not a question, and I'm not 利益／興味d in playing Twenty Questions to 調査する your actual question out of you ― I have better things to do. On seeing something like this, my reaction is 普通は of one of the に引き続いて:
|
Q: | I'm having problems with my Windows machine. Can you help? |
A: | Yes. Throw out that Microsoft trash and 任命する／導入する an open-source operating system like Linux or BSD. 公式文書，認める: you can ask questions 関係のある to Windows machines if they are about a program that does have an 公式の／役人 Windows build, or interacts with Windows machines (i.e., Samba). Just don't be surprised by the reply that the problem is with Windows and not the program, because Windows is so broken in general that this is very often the 事例／患者. |
Q: | My program doesn't work. I think system 施設 X is broken. |
A: | While it is possible that you are the first person to notice an obvious 欠陥／不足 in system calls and libraries ひどく used by hundreds or thousands of people, it is rather more likely that you are utterly clueless. 驚くべき／特命の／臨時の （人命などを）奪う，主張するs 要求する 驚くべき／特命の／臨時の 証拠; when you make a （人命などを）奪う，主張する like this one, you must 支援する it up with （疑いを）晴らす and exhaustive documentation of the 失敗 事例／患者. |
Q: | I'm having problems 任命する／導入するing Linux or X. Can you help? |
A: | No. I'd need 手渡すs-on 接近 to your machine to troubleshoot this. Go ask your 地元の Linux 使用者 group for 手渡すs-on help. (You can find a 名簿（に載せる）／表（にあげる） of 使用者 groups here.) 公式文書，認める: questions about 任命する／導入するing Linux may be appropriate if you're on a 会議 or mailing 名簿（に載せる）／表（にあげる） about a particular 配当, and the problem is with that distro; or on 地元の 使用者 groups 会議s. In this 事例／患者, be sure to 述べる the exact 詳細（に述べる）s of the 失敗. But do careful searching first, with "linux" and all 怪しげな pieces of 金物類／武器類. |
Q: | How can I 割れ目 root/steal channel-ops 特権s/read someone's e-mail? |
A: | You're a lowlife for wanting to do such things and a moron for asking a hacker to help you. |
Finally, I'm going to illustrate how to ask questions in a smart way by example; pairs of questions about the same problem, one asked in a stupid way and one in a smart way.
This question just begs for "STFW" as a reply.
This one has already STFWed, and sounds like there might be a real problem.
The querent assumes that somebody else screwed up. Arrogant git...
The querent has 明示するd the 環境, read the FAQ, is showing the error, and is not assuming his problems are someone else's fault. This one might be 価値（がある） some attention.
J. 無作為の Hacker's 返答 to this is likely to be “権利. Do you need burping and diapering, too?” followed by a punch of the 削除する 重要な.
This person, on the other 手渡す, seems worthy of an answer. He/she has 展示（する）d problem-solving 知能 rather than passively waiting for an answer to 減少（する） from on high.
In the last question, notice the subtle but important difference between 需要・要求するing “Give me an answer” and “Please help me 人物／姿／数字 out what 付加 diagnostics I can run to 達成する enlightenment.”
In fact, the form of that last question is closely based on a real 出来事/事件 that happened in August 2001 on the linux-kernel mailing 名簿（に載せる）／表（にあげる） (lkml). I (Eric) was the one asking the question that time. I was seeing mysterious lockups on a Tyan S2462 motherboard. The 名簿（に載せる）／表（にあげる） members 供給（する）d the 批判的な （警察などへの）密告，告訴（状） I needed to solve them.
By asking the question in the way I did, I gave people something to chew on; I made it 平易な and attractive for them to get 伴う／関わるd. I 論証するd 尊敬（する）・点 for my peers' ability and 招待するd them to 協議する with me as a peer. I also 論証するd 尊敬（する）・点 for the value of their time by telling them the blind alleys I had already run 負かす／撃墜する.
Afterwards, when I thanked everyone and 発言／述べるd how 井戸／弁護士席 the 過程 had worked, an lkml member 観察するd that he thought it had worked not because I'm a “指名する” on that 名簿（に載せる）／表（にあげる）, but because I asked the question in the proper form.
Hackers are in some ways a very ruthless meritocracy; I'm 確かな he was 権利, and that if I had behaved like a sponge I would have been 炎上d or ignored no 事柄 who I was. His suggestion that I 令状 up the whole 出来事/事件 as 指示／教授／教育 to others led 直接／まっすぐに to the composition of this guide.
If you can't get an answer, please don't take it 本人自身で that we don't feel we can help you. いつかs the members of the asked group may 簡単に not know the answer. No 返答 is not the same as 存在 ignored, though admittedly it's hard to 位置／汚点／見つけ出す the difference from outside.
In general, 簡単に re-地位，任命するing your question is a bad idea. This will be seen as pointlessly annoying. Have patience: the person with your answer may be in a different time-zone and asleep. Or it may be that your question wasn't 井戸／弁護士席-formed to begin with.
There are other sources of help you can go to, often sources better adapted to a novice's needs.
There are many online and 地元の 使用者 groups who are 熱中している人s about the ソフトウェア, even though they may never have written any ソフトウェア themselves. These groups often form so that people can help each other and help new 使用者s.
There are also plenty of 商業の companies you can 契約 with for help, both large and small. Don't be 狼狽d at the idea of having to 支払う／賃金 for a bit of help! After all, if your car engine blows a 長，率いる gasket, chances are you would take it to a 修理 shop and 支払う／賃金 to get it 直す／買収する，八百長をするd. Even if the ソフトウェア didn't cost you anything, you can't 推定する／予想する that support to always come for 解放する／自由な.
For popular ソフトウェア like Linux, there are at least 10,000 使用者s per developer. It's just not possible for one person to 扱う the support calls from over 10,000 使用者s. Remember that even if you have to 支払う／賃金 for support, you are still 支払う／賃金ing much いっそう少なく than if you had to buy the ソフトウェア 同様に (and support for の近くにd-source ソフトウェア is usually more expensive and いっそう少なく competent than support for open-source ソフトウェア).
Be gentle. Problem-関係のある 強調する／ストレス can make people seem rude or stupid even when they're not.
Reply to a first 違反者／犯罪者 off-line. There is no need of public humiliation for someone who may have made an honest mistake. A real newbie may not know how to search 古記録s or where the FAQ is 蓄える／店d or 地位，任命するd.
If you don't know for sure, say so! A wrong but 権威のある-sounding answer is worse than 非，不，無 at all. Don't point anyone 負かす／撃墜する a wrong path 簡単に because it's fun to sound like an 専門家. Be humble and honest; 始める，決める a good example for both the querent and your peers.
If you can't help, don't 妨げる. Don't make jokes about 手続きs that could trash the 使用者's 体制／機構 ― the poor 次第に損なう might 解釈する／通訳する these as 指示／教授／教育s.
Ask 調査（する）ing questions to elicit more 詳細（に述べる）s. If you're good at this, the querent will learn something ― and so might you. Try to turn the bad question into a good one; remember we were all newbies once.
While muttering RTFM is いつかs 正当化するd when replying to someone who is just a lazy slob, a pointer to documentation (even if it's just a suggestion to google for a 重要な phrase) is better.
If you're going to answer the question at all, give good value. Don't 示唆する kludgy workarounds when somebody is using the wrong 道具 or approach. 示唆する good 道具s. Reframe the question.
Answer the actual question! If the querent has been so 徹底的な as to do his or her 研究 and has 含むd in the query that X, Y, Z, A, B, and C have already been tried without good result, it is supremely unhelpful to 答える／応じる with “Try A or B,” or with a link to something that only says, “Try X, Y, Z, A, B, or C.”.
Help your community learn from the question. When you field a good question, ask yourself “How would the 関連した documentation or FAQ have to change so that nobody has to answer this again?” Then send a patch to the 文書 maintainer.
If you did 研究 to answer the question, 論証する your 技術s rather than 令状ing as though you pulled the answer out of your butt. Answering one good question is like feeding a hungry person one meal, but teaching them 研究 技術s by example is showing them how to grow food for a lifetime.
If you need 指示／教授／教育 in the basics of how personal computers, Unix, and the Internet work, see The Unix and Internet 根底となるs HOWTO.
When you 解放（する） ソフトウェア or 令状 patches for ソフトウェア, try to follow the 指導基準s in the ソフトウェア 解放（する） Practice HOWTO.