UPDATE: FAQ-4.9 (dmesg)

Below is a diff to augment FAQ 4.9 in hopes of getting more dmesg's sent in and 
making sure they are usable.


--- faq/faq4.html.orig	Wed Feb 21 17:02:00 2007
+++ faq/faq4.html	Wed Feb 21 18:14:44 2007
@@ -2043,11 +2043,43 @@
  [email protected]
 </pre>
 where <tt>[email protected]</tt> is your regular email account.
-(or transfer the dmesg output using FTP/scp/floppydisk/carrier-pigeon/...)
 
 <p>
+The methods above are much easier but if you chose not to configure mail on 
+your OpenBSD system, you should still send your dmesg to the developers. Save 
+your dmesg output to a text file.
+<pre>
+$ dmesg > ~/dmesg.txt
+</pre>
+<p>
+Then transfer the file (using FTP/scp/floppydisk/carrier-pigeon/...)  to the
+system you normally use for email. 
+
+<p>
+Since the dmesg output you send in is processed automatically, when using 
+alternate email clients/systems to send in your dmesg be sure to remember the
+following: 
+<ul>
+<li>Make sure your email client is configured to send messages as plain text
+    (do not use HTML-formatted email) 
+<li>Make sure to turn off any forced line break feature. Many email clients are 
+    configured to insert line breaks at 72 characters/columns (the norm for
+    mailing lists), so be sure to turn this feature off.
+<li>Make sure your email client does not reformat messages into "text-flow" 
+    nonsesne.
+<li>Do not send the dmesg output as file attachement. You should
+    cat/pipe/copy/paste the dmesg output into the body of the message.
+</ul>
+
+<p>
 <strong>NOTE</strong> - Please send only GENERIC kernel dmesgs. Custom
 kernels that have device drivers removed are not helpful.
+
+<p>
+<strong>NOTE</strong> - If you have a supported multiprocessor system and 
+normally run the GENERIC.MP kernel, it is helpful to developers to see the dmesg
+output of both the GENERIC kernel and the GENERIC.MP kernel, so please send both
+of them in separate emails.
 
 <p>
 Also note that the dmesgs are received on a computer using the