public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Eray Aslan <eras@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Don't use UIDs and GIDs below 100 without QA approval
Date: Mon, 29 Nov 2021 17:17:22 +0300	[thread overview]
Message-ID: <YaTg8sOSkWgpi8VA@rog.a21an.org> (raw)
In-Reply-To: <ulf18r3v7@gentoo.org>

On Sun, Nov 28, 2021 at 11:06:36AM +0100, Ulrich Mueller 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.)

In the static allocation option, the rate of increase is the rate of new
ID-needing software ported to the tree minus - optimistically - the rate
of treecleaning similar software.  Optimistic because I am not sure how
much, or at what point, do we want to re-use treecleaned IDs.

In the dynamic case, we dont care about the global status and are really
bound by the max number of sysem IDs installed in a single system.
Local maximum is rather stable and in any case is a lot smaller than
global maximum.  Plus in this age of containers and namespaces, this
isnt really a problem even if it did grow over time, i.e. even if
unbounded, we have tools to manage it.

-- 
Eray


      parent reply	other threads:[~2021-11-29 14:17 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
2021-11-28 20:42             ` Gordon Pettey
2021-11-28 20:52               ` William Hubbs
2021-11-29 14:17         ` Eray Aslan [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=YaTg8sOSkWgpi8VA@rog.a21an.org \
    --to=eras@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