No, sorry it is not as simple. When you use mangled names you must assure they will always be mangled the same way during the same connection. So if a file gets deleted and then recreated it must be mangled back the same way! This will make things overly complex and oblige us to keep 2 separate caches at a time and switch between 2 algorithms adding too much complexity and needing a complete retest of the mangling code. That would made it too much work and would be available in time for 2.2.5
The back port have been made only for special cases (people that have programs generating lot of similarly named files in a single directory). The new algorithm will be the default on samba 3 and thats the best balance IMO. /simo who hates html mail ;) On Fri, 2002-05-31 at 14:47, Esh, Andrew wrote: > Why not just use a different hash character for the new code, and keep the > old unhashing code? Old hashed names can still be read, and new hashed names > can still be stored and read. No confusion would take place. > -- Simo Sorce ---------- Una scelta di liberta': Software Libero. A choice of freedom: Free Software. http://www.softwarelibero.it
