From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 25 17:02:34 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BCC4916A496 for ; Tue, 25 Sep 2007 17:02:34 +0000 (UTC) (envelope-from info@rsync.net) Received: from mail.rsync.net (mail.rsync.net [69.43.165.11]) by mx1.freebsd.org (Postfix) with ESMTP id 8BF4813C478 for ; Tue, 25 Sep 2007 17:02:34 +0000 (UTC) (envelope-from info@rsync.net) Received: from mail.rsync.net (mail.rsync.net [69.43.165.11]) by mail.rsync.net (8.12.11/8.12.11) with ESMTP id l8PGp6dN019089 for ; Tue, 25 Sep 2007 09:51:06 -0700 (PDT) (envelope-from info@rsync.net) Received: from localhost (info@localhost) by mail.rsync.net (8.12.11/8.12.11/Submit) with ESMTP id l8PGp6p7019086 for ; Tue, 25 Sep 2007 09:51:06 -0700 (PDT) (envelope-from info@rsync.net) X-Authentication-Warning: mail.rsync.net: info owned process doing -bs Date: Tue, 25 Sep 2007 09:51:06 -0700 (PDT) From: "rsync.net" To: freebsd-hackers@freebsd.org Message-ID: <20070925093722.N21960@mail.rsync.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailman-Approved-At: Wed, 26 Sep 2007 12:41:19 +0000 Subject: kern.ngroups (non) setting ... new bounty ? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 17:02:34 -0000 It has been impossible to change kern.ngroups - at least for several years now. It was not fixed in either 5.x or 6.x : http://lists.freebsd.org/pipermail/freebsd-bugs/2007-January/022140.html It is seemingly a difficult problem: http://www.atm.tut.fi/list-archive/freebsd-stable/msg09969.html [1] However it should be solved - we can't be the only ones out there trying to add a UID to more than 16 groups... ----- The rsync.net code bounties have been fairly successful this year - two of the five projects have been completed, and the large "vmware 6 on FreeBSD" project is now underway. We'd like to add a new bounty for this kern.ngroups issue. We are posting to -hackers today to get some feedback on how long this will take and how much money might reasonably be expected to lure this work. --rsync.net Support [1] Is it indeed true that these programs are broken by not following NGROUPS_MAX from syslimits.h?