Subject: Re: Permissions on directories.
To: Todd Vierling <firstname.lastname@example.org>
From: Jonathan Stone <jonathan@DSG.Stanford.EDU>
Date: 10/20/1998 17:48:58
>Well, for those who _do_ care, here's a not so beautiful patch that adds a
>compile time option. I'd like to propose sysctling it and adding it to
Ack. pfft. If you _have_ to do this, despite what kre says, please
make it a mount option (so it applies per filesystem), not a sysctl.
Otherwise the quota interactions are just _horrible_.
at least if it's per-mount a sysadmin can try and make sane choices
about how this mixes with quotas on a filesystem-by-filesystem basis.
>When FFS_USE_EGID is compiled in the kernel, if the user is a member of the
>parent directory's group, or the directory is setgid, the new inode will be
>created with the directory's group. Otherwise, the new inode will use the
>user's egid. This seemed to me like the best tradeoff between the two.
EGID is backwards. I'd use "dirgid" or "grpid" (wasnt that what SunOS
used?) but make the default be whatever POSIX says, if that's
different from BSD practice, and BSD otherwise.
If we go down this route, I dont see why it shouldn't apply to all
local filesystems that have group-IDs. I dunno about nonlocal
(NFS,...) though : if the client's mount flags disagree with the
server's local mount flags, who should win?