#, fuzzy msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "POT-Creation-Date: 2018-12-08 14:45-0200\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Put one translator per line, in the form NAME , YEAR1, YEAR2 msgctxt "_" msgid "translator-credits" msgstr "" #. (itstool) path: info/title #: article.translate.xml:4 msgid "How to get best results from the FreeBSD-questions mailing list" msgstr "" #. (itstool) path: affiliation/address #: article.translate.xml:9 #, no-wrap msgid "grog@FreeBSD.org" msgstr "" #. (itstool) path: info/author #: article.translate.xml:8 msgid "" "GregLehey <_:address-1/> " msgstr "" #. (itstool) path: legalnotice/para #: article.translate.xml:13 msgid "FreeBSD is a registered trademark of the FreeBSD Foundation." msgstr "" #. (itstool) path: legalnotice/para #: article.translate.xml:15 msgid "" "Microsoft, IntelliMouse, MS-DOS, Outlook, Windows, Windows Media and Windows " "NT are either registered trademarks or trademarks of Microsoft Corporation " "in the United States and/or other countries." msgstr "" #. (itstool) path: legalnotice/para #: article.translate.xml:19 msgid "" "Motif, OSF/1, and UNIX are registered trademarks and IT DialTone and The " "Open Group are trademarks of The Open Group in the United States and other " "countries." msgstr "" #. (itstool) path: legalnotice/para #: article.translate.xml:23 msgid "" "QUALCOMM and Eudora are registered trademarks of QUALCOMM Incorporated." msgstr "" #. (itstool) path: legalnotice/para #: article.translate.xml:25 msgid "" "Many of the designations used by manufacturers and sellers to distinguish " "their products are claimed as trademarks. Where those designations appear in " "this document, and the FreeBSD Project was aware of the trademark claim, the " "designations have been followed by the ™ or the ® symbol." msgstr "" #. (itstool) path: info/pubdate #. (itstool) path: info/releaseinfo #: article.translate.xml:33 article.translate.xml:35 msgid "" "$FreeBSD: head/en_US.ISO8859-1/articles/freebsd-questions/article.xml 52192 " "2018-08-30 10:31:43Z ebrandi $" msgstr "" #. (itstool) path: abstract/para #: article.translate.xml:38 msgid "" "This document provides useful information for people looking to prepare an e-" "mail to the FreeBSD-questions mailing list. Advice and hints are given that " "will maximize the chance that the reader will receive useful replies." msgstr "" #. (itstool) path: abstract/para #: article.translate.xml:43 msgid "" "This document is regularly posted to the FreeBSD-questions mailing list." msgstr "" #. (itstool) path: sect1/title #. (itstool) id: article.translate.xml#Introduction #: article.translate.xml:49 msgid "Introduction" msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:51 msgid "" "FreeBSD-questions is a mailing list maintained by the " "FreeBSD project to help people who have questions about the normal use of " "FreeBSD. Another group, FreeBSD-hackers, discusses more " "advanced questions such as future development work." msgstr "" #. (itstool) path: note/para #: article.translate.xml:58 msgid "" "The term hacker has nothing to do with breaking into other " "people's computers. The correct term for the latter activity is " "cracker, but the popular press has not found out yet. The " "FreeBSD hackers disapprove strongly of cracking security, and have nothing " "to do with it. For a longer description of hackers, see Eric Raymond's How To Become " "A Hacker" msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:67 msgid "" "This is a regular posting aimed to help both those seeking advice from " "FreeBSD-questions (the newcomers), and also those who answer " "the questions (the hackers)." msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:71 msgid "" "Inevitably there is some friction, which stems from the different viewpoints " "of the two groups. The newcomers accuse the hackers of being arrogant, stuck-" "up, and unhelpful, while the hackers accuse the newcomers of being stupid, " "unable to read plain English, and expecting everything to be handed to them " "on a silver platter. Of course, there is an element of truth in both these " "claims, but for the most part these viewpoints come from a sense of " "frustration." msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:79 msgid "" "In this document, I would like to do something to relieve this frustration " "and help everybody get better results from FreeBSD-questions. In the " "following section, I recommend how to submit a question; after that, we will " "look at how to answer one." msgstr "" #. (itstool) path: sect1/title #. (itstool) id: article.translate.xml#subscribe #: article.translate.xml:86 msgid "How to subscribe to FreeBSD-questions" msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:88 msgid "" "FreeBSD-questions is a mailing list, so you need mail access. Point your WWW " "browser to the information page of the FreeBSD-questions mailing list. In the section titled Subscribing to freebsd-questions " "fill in the Your email address field; the other fields are " "optional." msgstr "" #. (itstool) path: note/para #: article.translate.xml:95 msgid "" "The password fields in the subscription form provide only mild security, but " "should prevent others from messing with your subscription. Do not " "use a valuable password as it will occasionally be emailed back " "to you in cleartext." msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:101 msgid "" "You will receive a confirmation message from mailman; follow the included instructions to complete your subscription." "" msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:105 msgid "" "Finally, when you get the Welcome message from " "mailman telling you the details of the list and " "subscription area password, please save it. If you ever " "should want to leave the list, you will need the information there. See the " "next section for more details." msgstr "" #. (itstool) path: sect1/title #. (itstool) id: article.translate.xml#unsubscribe #: article.translate.xml:113 msgid "How to unsubscribe from FreeBSD-questions" msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:115 msgid "" "When you subscribed to FreeBSD-questions, you got a welcome message from " "mailman. In this message, amongst other things, " "it told you how to unsubscribe. Here is a typical message:" msgstr "" #. (itstool) path: sect1/literallayout #: article.translate.xml:120 #, no-wrap msgid "" "Welcome to the freebsd-questions@freebsd.org mailing list!\n" "\n" "To post to this list, send your email to:\n" "\n" " freebsd-questions@freebsd.org\n" "\n" "General information about the mailing list is at:\n" "\n" " https://lists.freebsd.org/mailman/listinfo/freebsd-questions\n" "\n" "If you ever want to unsubscribe or change your options (e.g., switch to\n" "or from digest mode, change your password, etc.), visit your\n" "subscription page at:\n" "\n" "https://lists.freebsd.org/mailman/options/freebsd-questions/grog%40lemsi.de\n" "\n" "You can also make such adjustments via email by sending a message to:\n" "\n" " freebsd-questions-request@freebsd.org\n" "\n" "with the word `help' in the subject or body (don't include the\n" "quotes), and you will get back a message with instructions.\n" "\n" "You must know your password to change your options (including changing\n" "the password, itself) or to unsubscribe. It is:\n" "\n" " 12345\n" "\n" "Normally, Mailman will remind you of your freebsd.org mailing list\n" "passwords once every month, although you can disable this if you\n" "prefer. This reminder will also include instructions on how to\n" "unsubscribe or change your account options. There is also a button on\n" "your options page that will email your current password to you." msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:154 msgid "" "From the URL specified in your Welcome message you may visit " "the Account management page and enter a request to " "Unsubscribe you from FreeBSD-questions mailing list." msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:159 msgid "" "A confirmation message will be sent to you from mailman; follow the included instructions to finish unsubscribing." msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:163 msgid "" "If you have done this, and you still can not figure out what is going on, " "send a message to freebsd-questions-request@FreeBSD.org, and " "they will sort things out for you. Do not send a " "message to FreeBSD-questions: they can not help you." msgstr "" #. (itstool) path: sect1/title #. (itstool) id: article.translate.xml#askwho #: article.translate.xml:171 msgid "" "Should I ask -questions or -hackers?" msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:174 msgid "" "Two mailing lists handle general questions about FreeBSD, FreeBSD-" "questions and FreeBSD-hackers. In some cases, " "it is not really clear which group you should ask. The following criteria " "should help for 99% of all questions, however:" msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:182 msgid "" "If the question is of a general nature, ask FreeBSD-questions. Examples might be questions about installing FreeBSD or the use of " "a particular UNIX utility." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:189 msgid "" "If you think the question relates to a bug, but you are not sure, or you do " "not know how to look for it, send the message to FreeBSD-questions." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:195 msgid "" "If the question relates to a bug, and you are sure that " "it is a bug (for example, you can pinpoint the place in the code where it " "happens, and you maybe have a fix), then send the message to " "FreeBSD-hackers." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:203 msgid "" "If the question relates to enhancements to FreeBSD, and you can make " "suggestions about how to implement them, then send the message to " "FreeBSD-hackers." msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:209 msgid "" "There are also a number of other specialized mailing " "lists, which caters to more specific interests. The criteria above " "still apply, and it is in your interest to stick to them, since you are more " "likely to get good results that way." msgstr "" #. (itstool) path: sect1/title #. (itstool) id: article.translate.xml#before #: article.translate.xml:218 msgid "Before submitting a question" msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:220 msgid "" "You can (and should) do some things yourself before asking a question on one " "of the mailing lists:" msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:225 msgid "" "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." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:235 msgid "" "Read the manual pages, and the FreeBSD documentation (either installed in " "/usr/doc or accessible via WWW at http://www.FreeBSD.org), especially the " "handbook and the FAQ." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:244 msgid "" "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 https://www.FreeBSD.org/mail and https:" "//www.FreeBSD.org/search/search.html#mailinglists respectively. This " "can be done at other WWW sites as well, for example at http://marc.theaimsgroup.com." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:255 msgid "" "Use a search engine such as Google or Yahoo to find answers to your question." msgstr "" #. (itstool) path: sect1/title #. (itstool) id: article.translate.xml#submit #: article.translate.xml:263 msgid "How to submit a question" msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:265 msgid "" "When submitting a question to FreeBSD-questions, consider the following " "points:" msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:270 msgid "" "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." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:283 msgid "" "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. FreeBSD problem or " "Help 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." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:293 msgid "" "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." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:299 msgid "" "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." "" msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:305 msgid "" "A lot of badly formatted messages come from bad mailers or badly configured mailers. The " "following mailers are known to send out badly formatted messages without you " "finding out about them:" msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:313 msgid "Eudora" msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:317 msgid "exmh" msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:321 msgid "Microsoft Exchange" msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:325 msgid "" "Microsoft Outlook" msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:329 msgid "" "Try not to use MIME: a lot of people use mailers which do " "not get on very well with MIME." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:335 msgid "" "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." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:344 msgid "" "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." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:351 msgid "" "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:" msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:357 msgid "" "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." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:364 msgid "" "With any problem which could 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?" msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:370 msgid "" "There is a judgement call here, of course, but the output of the " "dmesg8 command can frequently be very useful, since it tells not just " "what hardware you are running, but what version of FreeBSD as well." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:377 msgid "" "If you get error messages, do not say I get error messages, " "say (for example) I get the error message 'No route to host'." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:383 msgid "" "If your system panics, do not say My system panicked, say " "(for example) my system panicked with the message 'free vnode isn't'." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:389 msgid "" "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." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:396 msgid "" "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?" msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:406 msgid "" "A lot of the information you need to supply is the output of programs, such " "as dmesg8, or console messages, which usually appear in " "/var/log/messages. 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 " "dmesg8, redirect the output to a file and include that. For example," msgstr "" #. (itstool) path: listitem/screen #: article.translate.xml:416 #, no-wrap msgid "% dmesg > /tmp/dmesg.out" msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:418 msgid "" "This redirects the information to the file /tmp/dmesg.out." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:423 msgid "" "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." msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:434 msgid "" "To summarize, let's assume you know the answer to the following question " "(yes, it is the same one in each case). You choose which of these two " "questions you would be more prepared to answer:" msgstr "" #. (itstool) path: example/title #: article.translate.xml:440 msgid "Message 1" msgstr "" #. (itstool) path: example/literallayout #: article.translate.xml:442 #, no-wrap msgid "" "Subject: HELP!!?!??\n" "I just can't get hits damn silly FereBSD system to\n" "workd, and Im really good at this tsuff, but I have never seen\n" "anythign sho difficult to install, it jst wont work whatever I try\n" "so why don't you guys tell me what I doing wrong." msgstr "" #. (itstool) path: example/title #: article.translate.xml:450 msgid "Message 2" msgstr "" #. (itstool) path: example/literallayout #: article.translate.xml:452 #, no-wrap msgid "" "Subject: Problems installing FreeBSD\n" "\n" "I've just got the FreeBSD 2.1.5 CDROM from Walnut Creek, and I'm having a " "lot\n" "of difficulty installing it. I have a 66 MHz 486 with 16 MB of\n" "memory and an Adaptec 1540A SCSI board, a 1.2GB Quantum Fireball\n" "disk and a Toshiba 3501XA CDROM drive. The installation works just\n" "fine, but when I try to reboot the system, I get the message\n" "Missing Operating System." msgstr "" #. (itstool) path: sect1/title #. (itstool) id: article.translate.xml#followup #: article.translate.xml:464 msgid "How to follow up to a question" msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:466 msgid "" "Often you will want to send in additional information to a question you have " "already sent. The best way to do this is to reply to your original message. " "This has three advantages:" msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:472 msgid "" "You include the original message text, so people will know what you are " "talking about. Do not forget to trim unnecessary text out, though." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:478 msgid "" "The text in the subject line stays the same (you did remember to put one in, " "did you not?). Many mailers will sort messages by subject. This helps group " "messages together." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:484 msgid "" "The message reference numbers in the header will refer to the previous " "message. Some mailers, such as mutt, can thread messages, showing the exact " "relationships between the messages." msgstr "" #. (itstool) path: sect1/title #. (itstool) id: article.translate.xml#answer #: article.translate.xml:494 msgid "How to answer a question" msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:497 msgid "Before you answer a question to FreeBSD-questions, consider:" msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:501 msgid "" "A lot of the points on submitting questions also apply to answering " "questions. Read them." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:506 msgid "" "Has somebody already answered the question? The easiest way to check this is " "to sort your incoming mail by subject: then (hopefully) you will see the " "question followed by any answers, all together." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:511 msgid "" "If somebody has already answered it, it does not automatically mean that you " "should not send another answer. But it makes sense to read all the other " "answers first." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:517 msgid "" "Do you have something to contribute beyond what has already been said? In " "general, Yeah, me too answers do not help much, although " "there are exceptions, like when somebody is describing a problem they are " "having, and they do not know whether it is their fault or whether there is " "something wrong with the hardware or software. If you do send a me " "too answer, you should also include any further relevant information." "" msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:527 msgid "" "Are you sure you understand the question? Very frequently, the person who " "asks the question is confused or does not express themselves very well. Even " "with the best understanding of the system, it is easy to send a reply which " "does not answer the question. This does not help: you will leave the person " "who submitted the question more frustrated or confused than ever. If nobody " "else answers, and you are not too sure either, you can always ask for more " "information." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:538 msgid "" "Are you sure your answer is correct? If not, wait a day or so. If nobody " "else comes up with a better answer, you can still reply and say, for " "example, I do not know if this is correct, but since nobody else has " "replied, why don't you try replacing your ATAPI CDROM with a frog?." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:547 msgid "" "Unless there is a good reason to do otherwise, reply to the sender and to " "FreeBSD-questions. Many people on the FreeBSD-questions are lurkers: they learn by reading messages sent and replied to by others. If you " "take a message which is of general interest off the list, you are depriving " "these people of their information. Be careful with group replies; lots of " "people send messages with hundreds of CCs. If this is the case, be sure to " "trim the Cc: lines appropriately." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:558 msgid "" "Include relevant text from the original message. Trim it to the minimum, but " "do not overdo it. It should still be possible for somebody who did not read " "the original message to understand what you are talking about." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:565 msgid "" "Use some technique to identify which text came from the original message, " "and which text you add. I personally find that prepending " "> to the original message works best. " "Leaving white space after the > and " "leave empty lines between your text and the original text both make the " "result more readable." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:575 msgid "" "Put your response in the correct place (after the text to which it replies). " "It is very difficult to read a thread of responses where each reply comes " "before the text to which it replies." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:581 msgid "" "Most mailers change the subject line on a reply by prepending a text such as " "Re: . If your mailer does not do it automatically, you should " "do it manually." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:587 msgid "" "If the submitter did not abide by format conventions (lines too long, " "inappropriate subject line), please fix it. In the case " "of an incorrect subject line (such as HELP!!??), change the " "subject line to (say) Re: Difficulties with sync PPP (was: HELP!!??). That way other people trying to follow the thread will have less " "difficulty following it." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:595 msgid "" "In such cases, it is appropriate to say what you did and why you did it, but " "try not to be rude. If you find you can not answer without being rude, do " "not answer." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:599 msgid "" "If you just want to reply to a message because of its bad format, just reply " "to the submitter, not to the list. You can just send him this message in " "reply, if you like." msgstr ""