I meant to imply that our (my!) guesses at correct answers are a lot more fun than finding out exactly how any given problem has been definitively solved & documented in the past. That is to say that I can only offer partial answers, which are bound to be mostly wrong ;)
On 11/15/06, Ben Barrett <[EMAIL PROTECTED]> wrote:
Yeah, the non-numerical chmod is much easier to understand, so it'd be something like chmod g+srw dirName (add read/write/sticky for group) and to get all files already in there I think you'd want to chmod -R g+rw dirName (recursively make dir & things in it, readable & writable for group) The group affected is the current group owning the file; it should stay even if that group name changes. Beware, if you're using a more complex access control system, like say the NSA code bundled with Fedora & some others, it will be a very different story, but not necessarily harder -- for those I'd recommend a nice front-end utility to help it make sense & get the right answer :) Google is for those without enough time, eh? The LUG is here for the rest of us. HA, j/k. Ben On 11/15/06, Quentin Hartman < [EMAIL PROTECTED]> wrote: > > On 11/15/06, Rob Hudson < [EMAIL PROTECTED]> wrote: > > How do I set up a directory so that any new files created in its > > subdirectories maintain the group and group write permissions? > > Entering the above sentence into google returned this page as the first > hit: > > http://www.dartmouth.edu/~rc/help/faq/permissions.html<http://www.dartmouth.edu/%7Erc/help/faq/permissions.html> > > search for "groupID" on that page to get the relevant bits. > > :D > > -- > -Regards- > > -Quentin Hartman- > _______________________________________________ > EUGLUG mailing list > euglug@euglug.org > http://www.euglug.org/mailman/listinfo/euglug >
_______________________________________________ EUGLUG mailing list euglug@euglug.org http://www.euglug.org/mailman/listinfo/euglug