Index: trunk/docs/Changelog
===================================================================
--- trunk/docs/Changelog	(revision 100)
+++ trunk/docs/Changelog	(revision 101)
@@ -1,3 +1,7 @@
-2.3.3:
+2.3.4:
+	* fixed compilation of kern_head (problem reported by S. Clormann)
+	* more typos fixed (reported by John Horne)
+
+2.3.3 (27-03-2007):
 	* fixed typos in configure.ac and manual (reported by John Horne)
 	* don't use mysql_options on x86_64, since libmysql is broken
Index: trunk/docs/FAQ.html
===================================================================
--- trunk/docs/FAQ.html	(revision 100)
+++ trunk/docs/FAQ.html	(revision 101)
@@ -139,5 +139,5 @@
 </ul>
 </div>
-<p><i>FAQ Revised: Monday 12 February 2007 23:06:43</i></p>
+<p><i>FAQ Revised: Saturday 14 April 2007 17:05:58</i></p>
 <hr><h2>Table of Contents</h2>
 <dl>
@@ -161,4 +161,5 @@
 <li><a href="#Build and install8">2.9. What is sh_tiger1.s?</a></li>
 <li><a href="#Build and install9">2.10. Why does static compiling (<code>--enable-static</code>) on MaxOS X fail ?</a></li>
+<li><a href="#Build and install10">2.11. Why does compiling with MySQL fail on Solaris ?</a></li>
 </ul></dd>
 <dt><b>3. File checking</b></dt>
@@ -406,4 +407,13 @@
 <a href="http://developer.apple.com/qa/qa2001/qa1118.html">Technical Q&A QA1118</a>. 
 This is a MacOS X issue and not a bug in samhain.<br><br></dd>
+<dt><b><a name="Build and install10">2.11. Why does compiling with MySQL fail on Solaris ?</a></b></dt>
+<dd>The reason is often the shell script 'mysql_config' that comes as part
+of MySQL. This script is intended to print appropriate compiler flags for
+compiling applications that use MySQL. Unfortunately, since Sun compiles
+MySQL with the Solaris compiler, this script outputs options for the Solaris 
+compiler (i.e. unsuitable for gcc). To solve this problem, you need to move
+this script (i.e. 'mysql_config') out of your PATH before running 
+<tt>./configure</tt> (unless of course you are using the Solaris compiler
+rather than gcc).<br><br></dd>
 </dl>
 <hr><h2>3. File checking</h2>
@@ -469,5 +479,5 @@
 as &quot;localhost&quot; to the server, thus the server 
 needs to trust the client name
-as reported by the client itself, and suppress all eroors on resolving
+as reported by the client itself, and suppress all errors on resolving
 this name to the apparent address. In the server configuration:
 
@@ -587,5 +597,6 @@
      <p>
      Alternatively, you can <code>scp</code> the database
-     to the client, run <code>samhain -t update -l none</code> (you
+     to the client, run <code>samhain -t update -l none --foreground</code> 
+     (you
      need to avoid logging because otherwise you will get in conflict with
      the running samhain daemon), and then <code>scp</code> the