From: Mike Gilbert <floppym@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Don't use UIDs and GIDs below 100 without QA approval
Date: Sun, 28 Nov 2021 15:34:10 -0500 [thread overview]
Message-ID: <CAJ0EP42ZUZJbUkSvV7E7TfkPSczmarHX9VeJDLtsboUogp8FAQ@mail.gmail.com> (raw)
In-Reply-To: <YaPmDiJeq9ghXyt5@linux1.home>
On Sun, Nov 28, 2021 at 3:26 PM William Hubbs <williamh@gentoo.org> wrote:
>
> On Sun, Nov 28, 2021 at 02:57:39PM -0500, Michael Orlitzky wrote:
> > On 2021-11-28 11:06:36, Ulrich Mueller wrote:
> > >
> > > While the rationale for static allocation that made it into GLEP 81 [1]
> > > is rather weak, several people had argued in favour of it on the mailing
> > > list [2].
> > >
> >
> > We don't even do static allocation. The UIDs and GIDs in the ebuilds
> > are suggestions, meant to benefit the people who will benefit from
> > them, and be ignored by everyone else.
> >
> > There are a few exceptional cases where a user or group needs a
> > specific identifier; but those were always statically allocated and
> > nothing has changed in that regard.
>
> Doesn't the emerge fail if a different user with ACCT_USER_ID already exists on
> the system (unless ACCT_USER_ID is set to -1, which is forbidden by qa policy)?
Not by default. If the eclass finds that ACCT_USER_ID is already
taken, it will allow useradd to assign a different one.
This behavior can be overridden by ebuilds (or a user) by setting
ACCT_USER_ENFORCE_ID.
next prev parent reply other threads:[~2021-11-28 20:34 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 10:59 [gentoo-dev] Don't use UIDs and GIDs below 100 without QA approval Ulrich Mueller
2021-11-11 11:34 ` Florian Schmaus
2021-11-11 11:40 ` Joonas Niilola
2021-11-11 11:48 ` Ulrich Mueller
2021-11-11 12:10 ` Pacho Ramos
2021-11-11 12:32 ` Jaco Kroon
2021-11-11 12:45 ` Ulrich Mueller
2021-11-11 12:13 ` Ionen Wolkens
2021-11-11 14:52 ` Florian Schmaus
2021-11-11 11:49 ` Rich Freeman
2021-11-11 18:31 ` Mike Gilbert
2021-11-11 19:08 ` Ulrich Mueller
2021-11-11 19:18 ` Mike Gilbert
2021-11-11 22:07 ` James Cloos
2021-11-13 10:08 ` Ulrich Mueller
2021-11-14 20:14 ` Ulrich Mueller
2021-11-14 20:15 ` Thomas Deutschmann
2021-11-14 23:37 ` Ulrich Mueller
2021-11-15 6:36 ` Eray Aslan
2021-11-28 4:13 ` William Hubbs
2021-11-28 10:06 ` Ulrich Mueller
2021-11-28 19:06 ` William Hubbs
2021-11-28 19:15 ` Michał Górny
2021-11-28 20:46 ` William Hubbs
2021-11-28 20:56 ` William Hubbs
2021-11-28 19:57 ` Michael Orlitzky
2021-11-28 20:26 ` William Hubbs
2021-11-28 20:34 ` Mike Gilbert [this message]
2021-11-28 20:42 ` Gordon Pettey
2021-11-28 20:52 ` William Hubbs
2021-11-29 14:17 ` Eray Aslan
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=CAJ0EP42ZUZJbUkSvV7E7TfkPSczmarHX9VeJDLtsboUogp8FAQ@mail.gmail.com \
--to=floppym@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