From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/policy-guide:master commit in: /
Date: Mon, 15 Nov 2021 13:10:05 +0000 (UTC) [thread overview]
Message-ID: <1636981770.b1ce71b478e916e3b55da5235ef285d35a8ac31e.ulm@gentoo> (raw)
commit: b1ce71b478e916e3b55da5235ef285d35a8ac31e
Author: Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Sun Nov 14 20:38:50 2021 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Mon Nov 15 13:09:30 2021 +0000
URL: https://gitweb.gentoo.org/proj/policy-guide.git/commit/?id=b1ce71b4
user-group: Update according to today's Council decision
Also change the order from downwards to upwards, so that we start
allocation in the new range 500..749 progressing upwards.
For the existing range 101..499 order doesn't really matter, because
it is practically full (as of today, 15 free UIDs and no free GIDs).
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
user-group.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/user-group.rst b/user-group.rst
index 09944a5..320d2e4 100644
--- a/user-group.rst
+++ b/user-group.rst
@@ -23,12 +23,12 @@ UIDs and GIDs in range 0..100 are reserved for important system
accounts. New assignments in that range need to be explicitly approved
by the QA lead, in response to a justified request from the developer.
-The range 101..499 is provided for regular use by packages.
+The range 101..749 is provided for regular use by packages.
The assignments from this range follow the following rules:
1. A developer can select an arbitrary free UID/GID from this range.
- If in doubt, it is recommended to select successive numbers from 499
- downwards.
+ If in doubt, it is recommended to select successive numbers from 101
+ upwards.
2. Unless there is a very good reason not to, matching users and groups
should use the same number. It is acceptable to leave gaps
next reply other threads:[~2021-11-15 13:10 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 13:10 Ulrich Müller [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-13 4:07 [gentoo-commits] proj/policy-guide:master commit in: / Sam James
2025-07-13 4:07 Sam James
2024-05-18 12:59 Ulrich Müller
2023-09-01 10:31 Michał Górny
2023-08-17 21:46 Ulrich Müller
2023-08-17 20:56 Ulrich Müller
2023-01-18 17:28 Ulrich Müller
2023-01-14 18:46 Sam James
2023-01-14 18:46 Sam James
2023-01-14 18:46 Sam James
2023-01-14 18:46 Sam James
2023-01-14 18:34 Ulrich Müller
2023-01-14 17:31 Ulrich Müller
2023-01-14 16:45 Ulrich Müller
2023-01-14 16:45 Ulrich Müller
2023-01-14 16:45 Ulrich Müller
2022-04-29 11:15 Ulrich Müller
2022-04-24 8:20 Ulrich Müller
2021-11-15 4:19 Sam James
2021-08-15 6:31 Michał Górny
2021-01-26 18:48 Ulrich Müller
2021-01-26 18:43 Ulrich Müller
2020-11-06 22:24 Michał Górny
2020-09-13 7:00 Michał Górny
2020-03-05 7:59 Michał Górny
2020-03-02 5:22 Michał Górny
2020-02-25 15:16 Michał Górny
2020-02-21 11:07 Michał Górny
2020-02-21 11:07 Michał Górny
2020-01-26 4:46 Michał Górny
2020-01-22 3:33 Michał Górny
2020-01-22 3:33 Michał Górny
2020-01-22 3:33 Michał Górny
2020-01-21 16:49 Michał Górny
2020-01-21 16:46 Michał Górny
2020-01-19 20:10 Michał Górny
2020-01-19 20:10 Michał Górny
2020-01-19 10:52 Michał Górny
2020-01-19 10:52 Michał Górny
2020-01-19 10:52 Michał Górny
2020-01-13 19:33 Michał Górny
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=1636981770.b1ce71b478e916e3b55da5235ef285d35a8ac31e.ulm@gentoo \
--to=ulm@gentoo.org \
--cc=gentoo-commits@lists.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