Re: [gentoo-dev] [RFC] Revisiting GLEP 81 (acct-*) policies (reviews, cross-distro syncing)

[Ulrich Mueller <ulm@gentoo.org>]

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

>>>>> On Mon, 09 Dec 2019, Thomas Deutschmann wrote:

> Make complete SYS_UID_MIN - SYS_UID_MAX range available for GLEP 81.

> The only argument/reason I am aware of, "but 501-999 could be used by
> system" (Dynamic allocation by user.eclass), isn't strong enough from my
> POV because system administrator can already pick something between
> SYS_UID_MIN-MAX so system must be already capable of dealing with such
> scenarios. So why do you think this range must be reserved? Isn't
> blocking 501-999 just another random choice?

> Therefor I would change the recommendation to pick highest free number.
> I.e. it should be recommended to pick the lowest free UID/GID pair
> instead (just to avoid fragmentation and keep 501+ free as long as
> possible).

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.

If the range below 500 should fill up completely, we can always
reconsider.

Ulrich

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