pulled up Brian's latest FAQ fixes

diff --git a/FAQ b/FAQ
index b7e44323cd97795db3e7b6b8fd5497752c0de73d..498b3a54a5b57e26c740a0ed3b7362420fc84d12 100644 (file)
--- a/FAQ
+++ b/FAQ
@@ -65,12 +65,13 @@ A: This is often caused by TXT records with missing close quotes.  Check that
 all TXT records containing quoted strings have both open and close quotes.
 
 
-Q: How do I produce a usable core file from a multithreaded named
-on Linux?
+Q: How do I produce a usable core file from a multithreaded named on Linux?
 
-A: Apply the kernel patch found in contrib/linux/coredump-patch and rebuild
-the kernel.  This patch causes multithreaded programs to dump the correct
-thread.
+A: If the Linux kernel is 2.4.7 or newer, multithreaded core dumps
+are usable (that is, the correct thread is dumped).  Otherwise, if using
+a 2.2 kernel, apply the kernel patch found in contrib/linux/coredump-patch
+and rebuild the kernel.  This patch will cause multithreaded programs to dump
+the correct thread.
 
 
 Q: How do I restrict people from looking up the server version?
@@ -144,7 +145,7 @@ Q: I keep getting log messages like the following.  Why?
 
    Jun 21 12:00:00.000 client 10.0.0.1#1234: update denied
 
-Someone is trying to update your DNS data using the RFC2136 Dynamic
+A: Someone is trying to update your DNS data using the RFC2136 Dynamic
 Update protocol.  Windows 2000 machines have a habit of sending dynamic
 update requests to DNS servers without being specifically configured to
 do so.  If the update requests are coming from a Windows 2000 machine,
@@ -156,7 +157,7 @@ Q: I see a log message like the following.  Why?
 
    couldn't open pid file '/var/run/named.pid': Permission denied
 
-You are most likely running named as a non-root user, and that user
+A: You are most likely running named as a non-root user, and that user
 does not have permission to write in /var/run.  The common ways of
 fixing this are to create a /var/run/named directory owned by the named
 user and set pid-file to "/var/run/named/named.pid", or set