From: Barry Shaw <baz@scms.waikato.ac.nz>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] enewgroup and enewuser suggestion
Date: Tue, 25 May 2004 08:59:27 +1200 [thread overview]
Message-ID: <40B2622F.6050200@scms.waikato.ac.nz> (raw)
A while back I asked about reserved UIDs and GIDs and Mike mentioned
that there was something in the works:
> ive worked out the details with nick about portage support i just
> havent passed it on to a few core people for comments so that i
> can write the GLEP
> -mike
The recent CVS upgrade brought this up again as it adds a new group and
user 'cvs' using enewgroup and enewuser (the UID and GID are selected
based on the next one available).
Given the fact that sites with large user bases will often have many
UIDs/GIDs that aren't continuous, it would be a good idea if these
functions were coded to check for the existence of a file that contained
reserved (or allowed) ranges of UIDs/GIDs. This would allow maximum
generality in portage, whilst giving end users maximum flexibility.
I'm willing to code this if its deemed a useful idea.
Baz
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2004-05-24 20:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-24 20:59 Barry Shaw [this message]
2004-05-24 21:05 ` [gentoo-dev] enewgroup and enewuser suggestion rob
2004-05-24 21:35 ` Mike Frysinger
2004-05-24 21:53 ` Barry Shaw
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=40B2622F.6050200@scms.waikato.ac.nz \
--to=baz@scms.waikato.ac.nz \
--cc=gentoo-dev@lists.gentoo.org \
/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