public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Don't use UIDs and GIDs below 100 without QA approval
Date: Thu, 11 Nov 2021 13:10:52 +0100	[thread overview]
Message-ID: <844d85bc625fb6d6eeaea502457430c2ad011594.camel@gentoo.org> (raw)
In-Reply-To: <ur1bmvroh@gentoo.org>

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

El jue, 11-11-2021 a las 12:48 +0100, Ulrich Mueller escribió:
> > > > > > On Thu, 11 Nov 2021, Florian Schmaus wrote:
> 
> > > We could:
> > > - Open some part of the range between 500 and 1000. For example,
> > > 500..799, which would leave 200 IDs for dynamic allocation.
> 
> > +1, since I am not aware of any significant downsides doing so.
> 
> > Could you elaborate why the range 500-799 only leaves us with 200 IDs?
> 
> We still need some range for dynamic allocation. Currently that is
> 500..999, and would be reduced to 800..999. That seems to be on the low
> side already.
> 
> In any case, 300 additional IDs may not be future proof at the rate
> we're currently allocating them. So I wonder if we shouldn't move to
> above 60000 immediately, or alternatively, give up the whole concept.
> 
> Ulrich

Personally I would move to >60000 and keep the 300 additional IDs for the case
some software really really needs them 

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2021-11-11 12:11 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 [this message]
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

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=844d85bc625fb6d6eeaea502457430c2ad011594.camel@gentoo.org \
    --to=pacho@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