mass chmod chown...

[Lindsay Holmwood]

On Sat, 17 Jul 2004 16:09:30 +0200
Alexander Dalloz <alexander.dalloz at uni-bielefeld.de> wrote:

> > And you would do something similar for the files.  Normally you would
> > want the directories to be executable, but the files to not be
> > executable so you would do the directories and files differently on the
> > chmod command.
> 
> Exactly. I did not make that clear enough in my posting, thanks Jeff.
> That was the deeper meaning of why better use the "find" command instead
> of using a "chmod -R", because the later affects all things below the
> given directory, while the former affects only those type of objects (I
> mean directories, files, character devices, block devices ...) you
> specifiy with the "type" parameter.

Of course, you could always use chmod -R (a/u/g/o)+X <directory name>, which
only sets executable permissions on files that already have them as well as
directories.

Lindsay


-- 
Lindsay Holmwood
asymmetrics.net
holmwoodl at iinet.net.au
http://www.asymmetrics.net/~auxesis/