[patch] user-group: Update according to today's Council decision

0001-user-group-Update-according-to-today-s-Council-decis.patch (text/plain), 1.61 KB, created by Ulrich Müller on 2021-11-14 21:26:06 UTC

From d0683634722aefe1365db58fb1494c034b2206ba Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ulrich=20M=C3=BCller?= <[e-mail]>
Date: Sun, 14 Nov 2021 21:38:50 +0100
Subject: [PATCH] user-group: Update according to today's Council decision
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

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 <[e-mail]>
---
 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
-- 
2.33.1