public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] rfc: allow -1 for ACCT_USER_ID and ACCT_GROUP_ID in ::gentoo
Date: Tue, 30 Nov 2021 19:32:45 -0600	[thread overview]
Message-ID: <YabQvdYWmoFvz/4O@linux1.home> (raw)
In-Reply-To: <utuftrh0p@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]

On Tue, Nov 30, 2021 at 12:59:18PM +0100, Ulrich Mueller wrote:
> >>>>> On Tue, 30 Nov 2021, James Cloos wrote:
> 
> >>>>> "UM" == Ulrich Mueller <ulm@gentoo.org> writes:
> UM> Also, why would one allocate UIDs in the 500..999 range (1000 is fine,
> UM> actually)? Gentoo always had UID_MIN=1000 and SYS_UID_MAX=999.
> 
> > why do you thing gentoo is everyone's first or only dist on their
> > network?
> 
> > or even on any given box?
> 
> I was specifically asking about Gentoo infra there.
> 
> > forcing existing boxen to change just because a new dist is added
> > is also unacceptable.
> 
> > for me though, it would be enough if there is something i can add to
> > make.conf to ensure that the acct-user and acct-group builds avoid the
> > ranges i already use.
> 
> > that may also work for others.
> 
> UIDs in the range SYS_UID_MIN..SYS_UID_MAX (i.e. 101..999) were always
> used for dynamic allocation of system accounts. GLEP 81 hasn't really
> changed anything there, except that the ebuild will now suggest an ID to
> try first.

This is the part of this that I don't understand. If we aren't enforcing
an ID, why do we care which ID to try first? It seems to be an
unnecessary step since users can pick the IDs they want by putting
settings in make.conf.

William

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  parent reply	other threads:[~2021-12-01  1:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-28 22:31 [gentoo-dev] rfc: allow -1 for ACCT_USER_ID and ACCT_GROUP_ID in ::gentoo William Hubbs
2021-11-28 23:26 ` Michael Orlitzky
2021-11-28 23:39   ` Sam James
2021-11-29  0:06     ` Michael Orlitzky
2021-11-29  5:05       ` Sam James
2021-11-29 13:25         ` Michael Orlitzky
2021-11-29  4:07 ` Michał Górny
2021-11-29  6:58   ` Alec Warner
2021-11-29 10:24     ` Ulrich Mueller
2021-11-30  0:49       ` James Cloos
2021-11-30 11:59         ` Ulrich Mueller
2021-11-30 21:08           ` James Cloos
2021-12-01  1:32           ` William Hubbs [this message]
2021-12-01  1:42             ` Michael Orlitzky
2021-12-01  6:16             ` Jaco Kroon
2021-12-01  6:45               ` Alec Warner
2021-12-01  7:51                 ` Jaco Kroon
2021-12-01 12:22                 ` Michael Orlitzky
2021-12-01 16:52             ` A Schenck
2021-11-30  0:55       ` Alec Warner

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=YabQvdYWmoFvz/4O@linux1.home \
    --to=williamh@gentoo.org \
    --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