From owner-freebsd-hackers Thu Dec 26 22:27:20 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA06326 for hackers-outgoing; Thu, 26 Dec 1996 22:27:20 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id WAA06321 for ; Thu, 26 Dec 1996 22:27:17 -0800 (PST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 0.56 #1) id E0vdVkj-0001hq-00; Thu, 26 Dec 1996 23:26:45 -0700 To: davidn@sdev.usn.blaze.net.au (David Nugent) Subject: Re: multi-group file access techniques / directory hardlinks Cc: owensc@enc.edu (Charles Owens), joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch), freebsd-hackers@freebsd.org (FreeBSD hackers), ben@narcissus.ml.org In-reply-to: Your message of "Fri, 27 Dec 1996 14:00:01 +1100." References: <199612262141.WAA00148@uriah.heep.sax.de> Date: Thu, 26 Dec 1996 23:26:45 -0700 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message David Nugent writes: : Unlike the 200 limit, though, a change here will affects the : kernel, not just userland code. There may not be a way of : making it "unlimited" without some significant redesign which : may break POSIX or other design specifications (I don't know), : but afaik there's no reason that this small limit could be raised : to, say, 64. But beyond a solution that involves lifting it to a : ridiculously high number, whatever limit is set is going to be : arbitrary. NFS v2 has hard limits in the number of groups a user may belong to, if memory serves me correctly. Warner