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
How can I unsubscribe?
You can use the same interface as above; or, you can follow the instructions that are at the bottom of every mailing list message that is sent.
Please do not send unsubscribe messages directly to the public lists themselves. First, this will not accomplish your goal, and second, it will irritate the existing subscribers, and you will probably get flamed. This is a classical mistake when using mailing lists; please try to avoid it.
Are archives available?
Yes. Threaded archives are available <link xlink:href="">here</link>.
Are mailing lists available in a digest format?
Yes. See <link xlink:href=""> the Mailman web interface</link>.
Mailing List Etiquette
Participation in the mailing lists, like participation in any community, requires a common basis for communication. Please make only appropriate postings, and follow common rules of etiquette.
What should I do before I post?
You have already taken the most important step by reading this document. However, if you are new to FreeBSD, you may first need to familiarize yourself with the software, and all the social history around it, by reading the numerous <link xlink:href="@@URL_RELPREFIX@@/docs/books.html">books and articles</link> that are available. Items of particular interest include the <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/faq/index.html"> FreeBSD Frequently Asked Questions (FAQ)</link> document, the <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/index.html"> FreeBSD Handbook</link>, and the articles <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/articles/freebsd-questions/article.html"> How to get best results from the FreeBSD-questions mailing list</link>, <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/articles/explaining-bsd/article.html"> Explaining BSD</link>, and <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/articles/new-users/article.html"> FreeBSD First Steps</link>.
It is always considered bad form to ask a question that is already answered in the above documents. This is not because the volunteers who work on this project are particularly mean people, but after a certain number of times answering the same questions over and over again, frustration begins to set in. This is particularly true if there is an existing answer to the question that is already available. Always keep in mind that almost all of the work done on FreeBSD is done by volunteers, and that we are only human.
What constitutes an inappropriate posting?
Postings must be in accordance with the charter of the mailing list.
Personal attacks are discouraged. As good net-citizens, we should try to hold ourselves to high standards of behavior.
Spam is not allowed, ever. The mailing lists are actively processed to ban offenders to this rule.
What is considered proper etiquette when posting to the mailing lists?
Please wrap lines at 75 characters, since not everyone uses fancy GUI mail reading programs.
Please respect the fact that bandwidth is not infinite. Not everyone reads email through high-speed connections, so if your posting involves something like the content of <filename>config.log</filename> or an extensive stack trace, please consider putting that information up on a website somewhere and just provide a URL to it. Remember, too, that these postings will be archived indefinitely, so huge postings will simply inflate the size of the archives long after their purpose has expired.
Format your message so that it is legible, and PLEASE DO NOT SHOUT!!!!!. Do not underestimate the effect that a poorly formatted mail message has, and not just on the FreeBSD mailing lists. Your mail message is all that people see of you, and if it is poorly formatted, badly spelled, full of errors, and/or has lots of exclamation points, it will give people a poor impression of you.
Please use an appropriate human language for a particular mailing list. Many non-English mailing lists are <link xlink:href="@@URL_RELPREFIX@@/community/mailinglists.html"> available</link>.
For the ones that are not, we do appreciate that many people do not speak English as their first language, and we try to make allowances for that. It is considered particularly poor form to criticize non-native speakers for spelling or grammatical errors. FreeBSD has an excellent track record in this regard; please, help us to uphold that tradition.
Please use a standards-compliant Mail User Agent (MUA). A lot of badly formatted messages come from <link xlink:href="">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">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 on these mailing lists 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 that they missed it and not bother to look.
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; not only it is a real pain, but 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 <command>dmesg</command>, 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>.


No matching activity found.

Browse all component changes

Source information

Source string comment
(itstool) path: listitem/para
Source string location
String age
a year ago
Source string age
a year ago
Translation file
articles/mailing-list-faq.pot, string 35