The translation is temporarily closed for contributions due to maintenance, please come back later.

Source string Read only

(itstool) path: listitem/para
Context English State
You can (and should) do some things yourself before asking a question on one of the mailing lists:
Try solving the problem on your own. If you post a question which shows that you have tried to solve the problem, your question will generally attract more positive attention from people reading it. Trying to solve the problem yourself will also enhance your understanding of FreeBSD, and will eventually let you use your knowledge to help others by answering questions posted to the mailing lists.
Read the manual pages, and the FreeBSD documentation (either installed in <filename>/usr/doc</filename> or accessible via WWW at <uri xlink:href="http://www.FreeBSD.org">http://www.FreeBSD.org</uri>), especially the <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/index.html">handbook</link> and the <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/faq/index.html">FAQ</link>.
Browse and/or search the archives for the mailing list, to see if your question or a similar one has been asked (and possibly answered) on the list. You can browse and/or search the mailing list archives at <uri xlink:href="https://www.FreeBSD.org/mail">https://www.FreeBSD.org/mail</uri> and <uri xlink:href="https://www.FreeBSD.org/search/search.html#mailinglists">https://www.FreeBSD.org/search/search.html#mailinglists</uri> respectively. This can be done at other WWW sites as well, for example at <uri xlink:href="http://marc.theaimsgroup.com">http://marc.theaimsgroup.com</uri>.
Use a search engine such as <link xlink:href="http://www.google.com">Google</link> or <link xlink:href="http://www.yahoo.com">Yahoo</link> to find answers to your question.
How to Submit a Question
When submitting a question to FreeBSD-questions, consider the following points:
Remember that nobody gets paid for answering a FreeBSD question. They do it of their own free will. You can influence this free will positively by submitting a well-formulated question supplying as much relevant information as possible. You can influence this free will negatively by submitting an incomplete, illegible, or rude question. It is perfectly possible to send a message to FreeBSD-questions and not get an answer even if you follow these rules. It is much more possible to not get an answer if you do not. In the rest of this document, we will look at how to get the most out of your question to FreeBSD-questions.
Not everybody who answers FreeBSD questions reads every message: they look at the subject line and decide whether it interests them. Clearly, it is in your interest to specify a subject. <quote>FreeBSD problem</quote> or <quote>Help</quote> are not enough. If you provide no subject at all, many people will not bother reading it. If your subject is not specific enough, the people who can answer it may not read it.
Format your message so that it is legible, and PLEASE DO NOT SHOUT!!!!!. We appreciate that a lot of people do not speak English as their first language, and we try to make allowances for that, but it is really painful to try to read a message written full of typos or without any line breaks.
Do not underestimate the effect that a poorly formatted mail message has, not just on the FreeBSD-questions mailing list. Your mail message is all people see of you, and if it is poorly formatted, one line per paragraph, badly spelt, or full of errors, it will give people a poor impression of you.
A lot of badly formatted messages come from <link xlink:href="http://www.lemis.com/email.html">bad mailers or badly configured mailers</link>. The following mailers are known to send out badly formatted messages without you finding out about them:
<trademark class="registered">Eudora</trademark>
exmh
<trademark class="registered">Microsoft</trademark> Exchange
<trademark class="registered">Microsoft</trademark> <trademark class="registered">Outlook</trademark>
Try not to use <acronym>MIME</acronym>: a lot of people use mailers which do not get on very well with <acronym>MIME</acronym>.
Make sure your time and time zone are set correctly. This may seem a little silly, since your message still gets there, but many of the people you are trying to reach get several hundred messages a day. They frequently sort the incoming messages by subject and by date, and if your message does not come before the first answer, they may assume they missed it and not bother to look.
Do not include unrelated questions in the same message. Firstly, a long message tends to scare people off, and secondly, it is more difficult to get all the people who can answer all the questions to read the message.
Specify as much information as possible. This is a difficult area, and we need to expand on what information you need to submit, but here is a start:
In nearly every case, it is important to know the version of FreeBSD you are running. This is particularly the case for FreeBSD-CURRENT, where you should also specify the date of the sources, though of course you should not be sending questions about -CURRENT to FreeBSD-questions.
With any problem which <emphasis>could</emphasis> be hardware related, tell us about your hardware. In case of doubt, assume it is possible that it is hardware. What kind of CPU are you using? How fast? What motherboard? How much memory? What peripherals?
There is a judgement call here, of course, but the output of the <citerefentry><refentrytitle>dmesg</refentrytitle><manvolnum>8</manvolnum></citerefentry> command can frequently be very useful, since it tells not just what hardware you are running, but what version of FreeBSD as well.
If you get error messages, do not say <quote>I get error messages</quote>, say (for example) <quote>I get the error message 'No route to host'</quote>.
If your system panics, do not say <quote>My system panicked</quote>, say (for example) <quote>my system panicked with the message 'free vnode isn't'</quote>.
If you have difficulty installing FreeBSD, please tell us what hardware you have. In particular, it is important to know the IRQs and I/O addresses of the boards installed in your machine.
If you have difficulty getting PPP to run, describe the configuration. Which version of PPP do you use? What kind of authentication do you have? Do you have a static or dynamic IP address? What kind of messages do you get in the log file?
A lot of the information you need to supply is the output of programs, such as <citerefentry><refentrytitle>dmesg</refentrytitle><manvolnum>8</manvolnum></citerefentry>, or console messages, which usually appear in <filename>/var/log/messages</filename>. Do not try to copy this information by typing it in again; it is a real pain, and you are bound to make a mistake. To send log file contents, either make a copy of the file and use an editor to trim the information to what is relevant, or cut and paste into your message. For the output of programs like <citerefentry><refentrytitle>dmesg</refentrytitle><manvolnum>8</manvolnum></citerefentry>, redirect the output to a file and include that. For example,
<prompt>%</prompt> <userinput>dmesg &gt; /tmp/dmesg.out</userinput>
This redirects the information to the file <filename>/tmp/dmesg.out</filename>.
If you do all this, and you still do not get an answer, there could be other reasons. For example, the problem is so complicated that nobody knows the answer, or the person who does know the answer was offline. If you do not get an answer after, say, a week, it might help to re-send the message. If you do not get an answer to your second message, though, you are probably not going to get one from this forum. Resending the same message again and again will only make you unpopular.
Component Translation Difference to current string
This translation Translated FreeBSD Doc (Archived)/articles_freebsd-questions
The following string has the same context and source.
Translated FreeBSD Doc (Archived)/articles_mailing-list-faq

Loading…

No matching activity found.

Browse all component changes

Source information

Source string comment
(itstool) path: listitem/para
Flags
read-only
Source string location
article.translate.xml:345
String age
a year ago
Source string age
a year ago
Translation file
articles/freebsd-questions.pot, string 53