If I recall the original question and circumstances, this was not a filer on the verge of running into a major problem unless this guy got an answer fast... and I'm quite sure no mater how extensive the tree was/is that he was trying to remove would have been done by now using a normal rm -rf versus waiting for more than a day to get the "quickest" solution on the planet.
Sometimes people make problems more complicated than they need to be.
-Christopher
In the immortal words of Chris Kotacka (arch@concentric.net):
And by the time all that is typed, or other proposed solutions are compiled, etc... a normal rm -rf Blah & would complete...
Not even _close_. rm -rf will take orders of magnitude longer than the perl solution, even if you type out the perl with one finger on a dvorak keyboard. Consult your local source code archive for clues as to why.
-n
------------------------------------------------------------memory@blank.org "Reality is that which, when you stop believing in it, doesn't go away." (PKD) http://www.blank.org/memory/------------------------------------------------