public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Thomas Deutschmann <whissi@gentoo.org>
To: gentoo development <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] [RFC] Revisiting GLEP 81 (acct-*) policies (reviews, cross-distro syncing)
Date: Mon, 9 Dec 2019 19:02:23 +0100	[thread overview]
Message-ID: <125e9b9f-ad37-ea5c-c204-9e2c404132a8@gentoo.org> (raw)
In-Reply-To: <w6g7e351jdm.fsf@kph.uni-mainz.de>


[-- Attachment #1.1: Type: text/plain, Size: 1147 bytes --]

On 2019-12-09 18:47, Ulrich Mueller wrote:
> One problem with that is that at some time user.eclass dynamically
> allocated IDs starting at 101 upwards, and later this was changed to 999
> downwards (at different times for UIDs and GIDs). So for existing
> systems you can expect some range above 101 and some range below 999 to
> be occupied. So it may not be the best idea to start picking IDs from
> 101 upwards, which are most likely to collide.

Sure, but what's the problem here? Or let me rephrase: Which problem do
you try to avoid/address with blocking 501-999 for now?

Like said, if an ID is already taken for any reason on user's system,
that's not a problem. acct-* can handle that... there's nothing like a
collision.

And until user.eclass is completely gone, all packages are migrated to
GLEP 81 and all users have completely reinstalled their Gentoo systems
(most packages used dynamic allocation until GLEP 81), you won't have
"clean", collision free systems with same ID all over the places.


-- 
Regards,
Thomas Deutschmann / Gentoo Linux Developer
C4DD 695F A713 8F24 2AA1 5638 5849 7EE5 1D5D 74A5


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

  reply	other threads:[~2019-12-09 18:02 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-09  8:17 [gentoo-dev] [RFC] Revisiting GLEP 81 (acct-*) policies (reviews, cross-distro syncing) Michał Górny
2019-12-09  9:44 ` Ulrich Mueller
2019-12-09 10:00   ` Ulrich Mueller
2019-12-09 16:54 ` Thomas Deutschmann
2019-12-09 17:47   ` Ulrich Mueller
2019-12-09 18:02     ` Thomas Deutschmann [this message]
2019-12-09 18:48       ` Ulrich Mueller
2019-12-09 20:10         ` Thomas Deutschmann
2019-12-10 14:36           ` Michael Orlitzky
2019-12-09 21:48 ` Alec Warner
2019-12-10  5:28   ` Michał Górny
2019-12-10  5:44 ` Joonas Niilola
2019-12-10 11:47   ` Rich Freeman
2019-12-10 12:26     ` Thomas Deutschmann
2019-12-10 12:44       ` Rich Freeman
2019-12-10 13:25         ` Thomas Deutschmann
2019-12-10 13:48           ` Rich Freeman
2019-12-10 16:05     ` Joonas Niilola
2019-12-10 16:25       ` Michael Orlitzky
2019-12-10 13:34   ` Michał Górny
2019-12-10 16:13     ` Joonas Niilola
2019-12-10 16:17       ` Michał Górny
2019-12-10 14:50 ` Michael Orlitzky
2019-12-10 15:04   ` Michał Górny
2019-12-10 15:54   ` Rich Freeman

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=125e9b9f-ad37-ea5c-c204-9e2c404132a8@gentoo.org \
    --to=whissi@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