New error messages

Fix for creating read-only files on windows
Manual updates


BitKeeper/deleted/.del-acconfig.h~65f1202b3b5c345f:
  ***MISSING WEAVE***
BitKeeper/deleted/.del-acconfig.h~7b620dbd69ea6074:
  ***MISSING WEAVE***
Docs/manual.texi:
  Small clarifications
BitKeeper/etc/ignore:
  Added Docs/manual.aux Docs/manual.cp Docs/manual.cps Docs/manual.dvi Docs/manual.fn Docs/manual.fns Docs/manual.ky Docs/manual.pg Docs/manual.toc Docs/manual.tp Docs/manual.vr Docs/manual_a4.ps Docs/manual_letter.ps to the ignore list
mysql-test/chew_on_this/select.res:
  ***MISSING WEAVE***
mysys/my_open.c:
  Fix for windows where some files where created read only
sql/ha_myisam.cc:
  Added 'checking table' to process-list status
sql/opt_range.cc:
  Cleanup
sql/share/czech/errmsg.sys:
  New error messages
sql/share/czech/errmsg.txt:
  New error messages
sql/share/italian/errmsg.sys:
  New error messages
sql/share/italian/errmsg.txt:
  New error messages

1 files changed, 16 insertions, 9 deletions

diff --git a/Docs/manual.texi b/Docs/manual.texi
index 0d1be9b735f..65b7abd976e 100644
--- a/Docs/manual.texi
+++ b/Docs/manual.texi
@@ -7491,6 +7491,10 @@ It is recomended you use MIT-pthreads on FreeBSD 2.x and native threads on
 Versions 3 and up. It is possible to run with  native threads on some late
 2.2.x versions but you may encounter problems shutting down mysqld.
 
+The @strong{MYSQL} Makefiles require GNU make (@code{gmake}) to work.
+If you want to compile @strong{MYSQL} you need to install GNU make
+first.
+
 Be sure to have your name resolver setup correct. Otherwise you may
 experience resolver delays or failures when connecting to mysqld.
 
@@ -7514,10 +7518,6 @@ shell> rm config.cache
 shell> ./configure --with-mit-threads
 @end example
 
-The behavior of FreeBSD @code{make} is slightly different from that of GNU
-@code{make}. If you have @code{make}-related problems, you should install GNU
-@code{make}.
-
 FreeBSD is also known to have a very low default file handle limit.
 @xref{Not enough file handles}. Uncomment the ulimit -n section in
 safe_mysqld or raise the limits for the mysqld user in /etc/login.conf
@@ -20233,11 +20233,11 @@ start @code{mysqld} with @code{--skip-bdb} o not waste memory for this cache.
 The value of the @code{--bdb-home} option.
 
 @item @code{bdb_lock_max}
-The maximum number of locks (1000 by default) you can have active on a BDB
-table. You should increase this if you get errors of type
-@code{bdb: Lock table is out of available locks} when you have do long
-transactions or when mysqld has to examine a lot of rows to calculate
-the query.
+The maximum number of locks (1000 by default) you can have active on a
+BDB table. You should increase this if you get errors of type @code{bdb:
+Lock table is out of available locks} or @code{Got error 12 from ...}
+when you have do long transactions or when @code{mysqld} has to examine
+a lot of rows to calculate the query.
 
 @item @code{bdb_logdir}
 The value of the @code{--bdb-logdir} option.
@@ -22519,6 +22519,13 @@ Normally you should start mysqld with @code{--bdb-recover} if you intend
 to use BDB tables.  This may, however, give you problems when you try to
 start mysqld if the BDB log files are corrupted. @xref{Starting server}.
 
+With @code{bdb_lock_max} you can specify the maximum number of locks
+(1000 by default) you can have active on a BDB table. You should
+increase this if you get errors of type @code{bdb: Lock table is out of
+available locks} or @code{Got error 12 from ...}  when you have do long
+transactions or when @code{mysqld} has to examine a lot of rows to
+calculate the query.
+
 @node BDB characteristic, BDB TODO, BDB start, BDB
 @subsection Some characteristic of @code{BDB} tables: