Xref: utzoo comp.unix.shell:1132 comp.unix.admin:727 comp.unix.questions:27678 Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!ittc!fpb From: fpb@ittc.wec.com (Frank P. Bresz) Newsgroups: comp.unix.shell,comp.unix.admin,comp.unix.questions Subject: Re: Setting (Recursively) Modes on Files Message-ID: Date: 21 Dec 90 17:57:44 GMT Sender: news@ittc.wec.com Followup-To: comp.unix.shell Distribution: usa Organization: Westinghouse, ITTC, Pgh, PA. Lines: 45 Yesterday I said : >>Hi, >> I often have the case where I want to open up an area of a >>directory to group access. However I am using SCCS and have many files >>that should remain read only. A mindless >> chmod -R g+w . >> Trashes the sanctity of SCCS by making some things group writable >>while they aren't user writable. >> How can I cleanly execute this command? >> awk/sed/sh/find (or whatever) accepted >> Please no PERL or CSH. >> SunOS4.1 (but please don't make it specific to that platform) Well the answer from Gene Spafford was the exact answer I was looking for : >chmod -R g=u . >will set the group protections for all files and directories to the >the same as the owner protections.... is that what you wanted? > >--spaf Thanks a lot Gene, for a neat concise answer. I guess I didn't quite get the meaning of = and the phrase : The letters u, g, or o indicate that permission is to be taken from the current mode for the user-class. This is being sent to try and stem the tidal wave of answers. -- | () () () | Frank P. Bresz | Westinghouse Electric Corporation | \ /\ / | fpb@ittc.wec.com | ITTC Simulators Department | \/ \/ | uunet!ittc!fpb | Those who can, do. Those who can't, simulate. | ---------- | +1 412 733 6749 | My opinions are mine, WEC don't want 'em.