Re: NO! chmod strikes!

[Dave Sherohman <esper@sherohman.org>]

On Mon, Jul 09, 2001 at 12:29:40PM -0400, Paul D. Smith wrote:
> %% Dave Carrigan <dave@rudedog.org> writes:
>   >> BTW, the best way to do what you wanted to do is this:
>   >> 
>   >> $ chmod -R o-owx .[!.]*
> 
>   dc> Or even better, ignore the -R in the chmod command and use find:
> 
>   dc>   find . -print0 | xargs -0 chmod r-owx
> 
> Not to be argumentative, but what's better about it?

While I won't presume to judge which is better, there is a difference:

The chmod -R version will affect .foo/bar and ignore foo/.bar (it looks
only at names in the directory where the command is issued) while the
find version will leave .foo/bar alone and change foo/.bar (it looks at
each filename independently).