From owner-freebsd-questions Tue Dec 5 2:38:45 2000 From owner-freebsd-questions@FreeBSD.ORG Tue Dec 5 02:38:42 2000 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 8882D37B400 for ; Tue, 5 Dec 2000 02:38:41 -0800 (PST) Received: from [195.11.243.26] (helo=Debug) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 143FUd-0001AR-00; Tue, 05 Dec 2000 10:38:39 +0000 To: Mike Meyer , Paul Herman , Dmitry Karasik , From: Cliff Sarginson Subject: Re: NGROUPS_MAX in sys/syslimits.h Date: Tue, 5 Dec 2000 10:38:39 GMT X-Mailer: www.webmail.nl.demon.net X-Sender: postmaster@btvs.demon.nl X-Originating-IP: 192.250.24.58 Message-Id: Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What is needed here is Access Control Lists, which exist on many Unices. This is the solution to your problem ! Does BSD support these ? Cliff > Paul Herman types: > > On Mon, 4 Dec 2000, Mike Meyer wrote: > > > > Mike> Which begs the question - why do you need so many groups? There may > > > > Mike> be a better solution to the problem that's causing that than kernel > > > > Mike> groups. > > > > > > > > 21 is not many - but of course, it depends what are you conting :) > > > > Our current configuration is that every user possesses a group > > > > with same name. > > > > > > You're right - 21 isn't many. But that number will change every time > > > you add a user, and your solution to the problem doesn't scale well. > > I never understood the reasoning behind each user having their own > > group (with their login name). Does anyone use this to their > > advantage? A huge "user" or "users" group that each user belongs to > > was always the way to go for me. > > If there's no natural grouping of users, doing this makes it possible > for a user to share their files with other users without sharing with > everyone or creating a new group. On the other hand, if you want to > share different sets of files with two groups of other users, you need > multiple groups anyway. To make proper use of this, you need a too > users can use to edit "their" /etc/group entry. Possibly a linux > distro has such a tool. > > The thing is, doing this with one large group doesn't solve Dmitry's > problem, which is that he wants to be able to access the files without > giving everyone else access to them. > > -- > Mike Meyer http://www.mired.org/home/mwm/ > Independent WWW/Unix/FreeBSD consultant, email for more information. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message