public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: 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 11:06:36 +0100	[thread overview]
Message-ID: <ulf18r3v7@gentoo.org> (raw)
In-Reply-To: <YaMB94DNDzKQBjl6@linux1.home> (William Hubbs's message of "Sat, 27 Nov 2021 22:13:43 -0600")

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

>>>>> On Sun, 28 Nov 2021, William Hubbs wrote:

> On Mon, Nov 15, 2021 at 09:36:32AM +0300, Eray Aslan wrote:
>> 1/ Static allocation does not really solve a problem. Not really not
>> nowadays
>> 2/ We cant keep adding new IDs to a distribution as new software gets
>> added - one side is unbounded.  This is losing game.

Not sure. In practice, the number of packages is limited. (And if the
argument was valid, it would apply to dynamic alloction too.)

>> Switching back to dynamic allocation seems to be the best option.

> I realize I'm very late to this party, but +1 from me also.

> We should use dynamic uid/git assignment by default and maybe provide
> a way to force certain uids/gids to be constant if users want this.

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].

In any case, let's cross that bridge when we reach it. For now, we're
good with 250 additional IDs.

Ulrich

[1] https://www.gentoo.org/glep/glep-0081.html#rationale
[2] https://archives.gentoo.org/gentoo-dev/message/33903763d46d193a25e4c03c4851bfc3

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

  reply	other threads:[~2021-11-28 10:06 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 [this message]
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
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=ulf18r3v7@gentoo.org \
    --to=ulm@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