From: Andreas Dilger <adilger@turbolinux.com>
To: Tim Hockin <thockin@sun.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: NGROUP increase - thoughts
Date: Mon, 16 Jul 2001 17:47:49 -0600 (MDT) [thread overview]
Message-ID: <200107162347.f6GNlnLk004959@webber.adilger.int> (raw)
In-Reply-To: <3B5379A9.6A9B11BE@sun.com> "from Tim Hockin at Jul 16, 2001 04:32:57 pm"
You write:
> I'm sure this has been given thought, so I want to probe teh collective
> resources. We need to have users in more than 32 groups. In fact, they
> may need to be a member of MANY more groups than that.
>
> What is the current thinking on this problem? Would it be desirable to
> replace current->groups[NGROUPS] with a poibnter to an array? Thus
> allowing (with libc changes) many more groups?
The real solution is ACLs (if you are talking filesystem permissions).
See acl.bestbits.at, I think, for ext2 ACL/EA patch.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
prev parent reply other threads:[~2001-07-16 23:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-16 23:32 Tim Hockin
2001-07-16 23:47 ` Andreas Dilger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200107162347.f6GNlnLk004959@webber.adilger.int \
--to=adilger@turbolinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thockin@sun.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®