Hi Joao!
So, in spite of the concerns raised (valid as they are) I would still vote to go ahead on this one as proposed.
What do people think?
Well, some as yet unstructured rants, off the top of my head... I'd love to see some sort of test-run being performed, e.g. going ahead and putting the result up as the (or an additional) test db? One of the key things might be to make sure that we (you :-) can perform a roll-back, if it turns out that we've messed up things badly... Is there any chance to do some sort of dry-run, and put up some sort of list of cases deserving investigation? Poul's page is a very good thing, indeed, although tackling a different aspect. My reasoning is that whatever can be fixed by humans, in a distributed project, before the brute-force attack would make life easier. Most probably basic rule #1 applies to my comments: use the brain before using the keyboard :-) Wilfried. -------------------------------------------------------------------------- Wilfried Woeber : e-mail: Woeber@CC.UniVie.ac.at Computer Center - ACOnet : Tel: +43 1 4277 - 140 33 Vienna University : Fax: +43 1 4277 - 9 140 Universitaetsstrasse 7 : RIPE-DB (&NIC) Handle: WW144 A-1010 Vienna, Austria, Europe : PGP public key ID 0xF0ACB369 --------------------------------------------------------------------------