Print and error message also if a read from file results in the Linux error EEXIST; may happen if the disk is broken

Now log_pos is the real position of the event. For events that are between BEGIN and COMMIT,
log_pos is still the BEGIN's log_pos.
This fixes bug #52 (If only transactions are run on the master then t

   redirected to the new location

   (Bug #121)

into serg.mysql.com:/usr/home/serg/Abk/mysql-4.0

into mysql.com:/space/my/mysql-4.0

  Change mode to -rwxrwxr-x

   distribution to fix a test failure in test "func_encrypt"

  Add comment that Guilhem should check master_log_name, pending etc are right if the master log gets rotated

  Remove (already commented out) code about storing the latest relay log pos info to InnoDB: we will probably use only the master log pos info when we restart a slave after a crash

  Do not try to resolve the table name of a corrupt page if the code is in ibbackup, i.e., the dict system is not initialized

Fixed bug in LOCK TABLE + DROP TABLE when other thread was waiting for a table that was locked bug not droped

into mysql.com:/space/my/mysql-4.0

  Fix a hang on the adaptive hash S-latch if an application program uses mysql_use_result() and performs queries on two connections at the same time

   packaging
 - enclosed some variables in quotes for safeguarding
 - add a license file (GPL or MySQLEULA) to the package so it will be
   displayed during installation (needs to be tested)

  Print a more precise error message if log files or data files are of a size different from what is specified in my.cnf

+ fix for #70 
+ test result fix for LOAD DATA LOCAL bug #82

  Print trx rollback progress info in crash recovery

into serg.mysql.com:/usr/home/serg/Abk/mysql-4.0

remove variable rli->log_pos_current.

("Event too big" etc), stop this thread instead of going on
with the next event, which would certainly lead to slave's data
corruption.

LOAD DATA LOCAL INFILE was not replicated correctly

   Monty)