Re: groups
>>"Colin" == Colin Watson <cjwatson@debian.org> writes:
Colin> I don't know why it was originally adopted, but I can tell you
Colin> why I think it's a good idea. If you're working on a shared
Colin> project with another user, you'll want to make sure those
Colin> files are group-writeable. If you have all users in the same
Colin> group, then it's not safe for any user to have umask 002 by
Colin> default, because everybody will be able to write to all the
Colin> files in their home directory. On the other hand, they'll have
Colin> to remember to use umask 002 when working on shared files,
Colin> because otherwise those files will only be writeable by them.
Colin> With one group per user, umask 002 is safe. All the files in
Colin> your home directory can be group-writeable, and it makes no
Colin> difference - but when you go to work on a shared project you
Colin> don't have to remember to switch the umask over.
This is indeed one of the reasons, perhaps the one that tipped
the balance when this was being decided (and redebated and
redebated).
manoj
--
Navvies channel water, fletchers fashion arrows, and carpenters work
on wood, but the good disciple themselves. 145
Manoj Srivastava <srivasta@debian.org> <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
Reply to:
- References:
- groups
- From: Greg Murphy <slackwares_slacker@yahoo.com>
- Re: groups
- From: Colin Watson <cjwatson@debian.org>