This seems like much of the right solution. The 2 seperate finds
would be the best if you really are worried about portability as
some systems don't deal with the : or . version of chown, but I think
the chown and chgrp are everywhere. If not, chances are there are
other things that will kill it as well.
Bill Silvert made the following keystrokes:
>Maybe I'm missing something in this, but if chown -R doesn't work,
>what is wrong with
>
>find . -exec chown $USER:$GROUP {} \;
>
>As for the colon vs. period business, there are two approaches;
>one is just the brute force solution
>
>find . -exec chown $USER {} \;
>find . -exec chgrp $GROUP {} \;
>
>and the other, which I have long hoped for, would be a configuration
>program like the one used by GNU which would examine the system and come
>up with the right Makefile and configuration parameters.
>
>--
>Bill Silvert, Habitat Ecology Section, Bedford Institute of Oceanography,
>P. O. Box 1006, Dartmouth, Nova Scotia, CANADA B2Y 4A2, Tel. (902)426-1577
>
References:
-
Chown
From: bill@biome.bio.dfo.ca (Bill Silvert)
|
|
