Attachment #15533 for bug #28776

View | Details | Raw Unified | Return to bug 28776
Collapse All | Expand All




	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 <ulink
	url="http://www.tuxedo.org/~esr/faqs/hacker-howto.html">How To Become
	A Hacker</ulink></para>
    </note>
    
    <para>This is a regular posting aimed to help both those seeking advice

    
    <para>When you get the reply from <application>majordomo</application>
      telling you the details of the list, <emphasis>please save
      it</emphasis>. If you ever should want to leave the list, you'll need
      the information there.  See the next section for more details.</para>
  </sect1>
  


    <itemizedlist>
      <listitem>
	<para>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

	
	<para>Don't 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's poorly
	  formatted, one line per paragraph, badly spelt, or full of
	  errors, it will give people a poor impression of you.</para>

	<para>A lot of badly formatted messages come from
	  <ulink url="http://www.lemis.com/email.html">bad mailers or badly
	  configured mailers</ulink>.  The following mailers are known to
	  send out badly formatted messages without you finding out about
	  them:</para>


      <listitem>
	<para>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, <quote>I
	don't know if this is correct, but since nobody else has
	replied, why don't you try replacing your ATAPI CD-ROM with
	a frog?</quote>.</para>
      </listitem>

      <listitem>

Return to bug 28776

Lines 46-52 Link Here

(-)en_US.ISO8859-1/articles/freebsd-questions/article.sgml (-9 / +10 lines)
46	out yet. The FreeBSD hackers disapprove strongly of cracking	46	out yet. The FreeBSD hackers disapprove strongly of cracking
47	security, and have nothing to do with it. For a longer description of	47	security, and have nothing to do with it. For a longer description of
48	hackers, see Eric Raymond's <ulink	48	hackers, see Eric Raymond's <ulink
49	url="http://www.tuxedo.org/~esr/faqs/hacker-howto.html">How To Become A Hacker</ulink></para>	49	url="http://www.tuxedo.org/~esr/faqs/hacker-howto.html">How To Become
		50	A Hacker</ulink></para>
50	</note>	51	</note>
51		52
52	<para>This is a regular posting aimed to help both those seeking advice	53	<para>This is a regular posting aimed to help both those seeking advice
Lines 83-89 Link Here
83		84
84	<para>When you get the reply from <application>majordomo</application>	85	<para>When you get the reply from <application>majordomo</application>
85	telling you the details of the list, <emphasis>please save	86	telling you the details of the list, <emphasis>please save
86	it</emphasis>. If you ever should want to leave the list, you'll need	87	it</emphasis>. If you ever should want to leave the list, you'll need
87	the information there. See the next section for more details.</para>	88	the information there. See the next section for more details.</para>
88	</sect1>	89	</sect1>
89		90
Lines 201-207 Link Here
201		202
202	<itemizedlist>	203	<itemizedlist>
203	<listitem>	204	<listitem>
204	<para> Remember that nobody gets paid for answering a FreeBSD	205	<para>Remember that nobody gets paid for answering a FreeBSD
205	question. They do it of their own free will. You can influence this	206	question. They do it of their own free will. You can influence this
206	free will positively by submitting a well-formulated question	207	free will positively by submitting a well-formulated question
207	supplying as much relevant information as possible. You can	208	supplying as much relevant information as possible. You can
Lines 232-244 Link Here
232		233
233	<para>Don't underestimate the effect that a poorly formatted mail	234	<para>Don't underestimate the effect that a poorly formatted mail
234	message has, not just on the FreeBSD-questions mailing list.	235	message has, not just on the FreeBSD-questions mailing list.
235	Your mail message is all people see of you, and if it's poorly	236	Your mail message is all people see of you, and if it's poorly
236	formatted, one line per paragraph, badly spelt, or full of	237	formatted, one line per paragraph, badly spelt, or full of
237	errors, it will give people a poor impression of you.</para>	238	errors, it will give people a poor impression of you.</para>
238		239
239	<para>A lot of badly formatted messages come from	240	<para>A lot of badly formatted messages come from
240	<ulink url="http://www.lemis.com/email.html">bad mailers or badly	241	<ulink url="http://www.lemis.com/email.html">bad mailers or badly
241	configured mailers</ulink>. The following mailers are known to	242	configured mailers</ulink>. The following mailers are known to
242	send out badly formatted messages without you finding out about	243	send out badly formatted messages without you finding out about
243	them:</para>	244	them:</para>
244		245
Lines 486-495 Link Here
486	<listitem>	487	<listitem>
487	<para>Are you sure your answer is correct?	488	<para>Are you sure your answer is correct?
488	If not, wait a day or so. If nobody else comes up with a	489	If not, wait a day or so. If nobody else comes up with a
489	better answer, you can still reply and say, for example, <quote>I	490	better answer, you can still reply and say, for example, <quote>I
490	don't know if this is correct, but since nobody else has	491	don't know if this is correct, but since nobody else has
491	replied, why don't you try replacing your ATAPI CD-ROM with	492	replied, why don't you try replacing your ATAPI CD-ROM with
492	a frog?</quote>.</para>	493	a frog?</quote>.</para>
493	</listitem>	494	</listitem>
494		495
495	<listitem>	496	<listitem>