(Suggested by Tomas Ulin as part of review for WL2278)

into mysql.com:/home/stewart/Documents/MySQL/5.0/ndb-dynamic-ports-impl4

When a node restarts it starts over again with fetching the configuration
-  It is not sure that it can use the "old dynamically allocated port number" again.
-  It should however try to reuse the old one, if not possible it should
allocate a new one. One has to be able to distinguish between portnumbers
specified originally in the config, and ones that has been dynamically added
(the latter may be changed if "busy", but the first cannot be changed).

We use negative portnumbers for ports that are ok to change.

into mysql.com:/home/stewart/Documents/MySQL/5.0/ndb-dynamic-ports-impl3

into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0-ndb

it's a struct now.

into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0-ndb

into mysql.com:/usr/local/home/marty/MySQL/mysql-5.0-ndb

into mysql.com:/usr/local/home/marty/MySQL/mysql-5.0

into mysql.com:/usr/local/home/marty/MySQL/mysql-5.0

into mysql.com:/home/jonas/src/mysql-5.0

into mysql.com:/home/jonas/src/mysql-5.0

a note, not a warning or error.

into mysql.com:/home/jonas/src/mysql-4.1

into mysql.com:/home/kostja/work/mysql-5.0-root

(Bug#7428) (renamed: hash_reset -> my_hash_reset)

into mysql.com:/home/jonas/src/mysql-5.0-ndb

into mysql.com:/home/jonas/src/mysql-5.0

into mysql.com:/home/jonas/src/mysql-5.0

into mysql.com:/home/jonas/src/mysql-4.1

into mysql.com:/usr/local/home/marty/MySQL/mysql-5.0

into mysql.com:/home/jwinstead2/mysql-5.0-clean

into mysql.com:/home/jwinstead2/mysql-4.1-clean

into mysql.com:/home/jwinstead2/mysql-4.1-clean

  Did some more split TABLE to TABLE and TABLE_SHARE