Re: bsd groups

[Ted Ts'o <tytso@mit.edu>]

On Tue, Oct 26, 2010 at 02:05:00PM -0400, wayne cripps wrote:
> 
>   Our department - Computer Science, at Dartmouth College, depends
> on bsd groups for our projects.  Having bsd groups means one less
> thing for the undergrads and their TAs to have to keep track of.
> Since we have used them forever, people are used to that behavior as
> default.

So if people really insist on using it, then we'll keep it.

But one thing which I don't understand; why can't you just set the
setgid bit on the shared spaces?  This causes newly created files to
have the same group id as the directory, and newly created
subdirectories to have the set gid bit.  Set the group id at the top
directory of the project's directory hierarchy, and set the setgid
bit, and all newly created files will inherit the group id of the
directory --- and all newly created subdirectory will inherit the
group id as well as the setgid bit.

This is the System V scheme, which is much more flexible than the BSD
scheme, since you can set control whether you have the BSD behaviour
or the original System V unix behaviour, which is to always use the
primary group ID of the creator.

If you set the setgid bit on all directories (chmod -R g+s /mnt), then
you'll effectively have the same behavior as the grpid mount option.

What we may do is add a pointer to a web page with this explanation so
that people can understand there is a better alternative.  Does this
work for you?

						- Ted