Gentoo Archives: gentoo-dev

From: Barry Shaw <baz@×××××××××××××××.nz>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Portage Management of UIDs/GIDs
Date: Sat, 29 May 2004 22:32:29
Message-Id: 40B90F79.1010606@scms.waikato.ac.nz
In Reply to: [gentoo-dev] Portage Management of UIDs/GIDs by Mike Frysinger
1 Mike Frysinger wrote:
2 > feedback is welcome ... i got bored last nite so i decided to stop putting it
3 > offf :P
4 > http://www.gentoo.org/proj/en/glep/glep-0027.html
5 > -mike
6 >
7 > --
8 > gentoo-dev@g.o mailing list
9 >
10
11 Looks good Mike, although I'd like to propose an addition. In terms of
12 the local site override its proposed that the ebuild checks for the
13 existance of a /etc/portage/accounts/[group|user]/<name>.xml before
14 adding the account. This prevents gentoo overriding site defaults, but
15 is only useful in the situation where there are only a few site specific
16 accounts that are local to the machine.
17
18 What would be handy is if we could define extra variables that reserve
19 sections of UID and GID space. This would help in situations where
20 there are a large number of accounts that aren't stored in the usual
21 password, shadow and group files (e.g. NIS, LDAP).
22
23 In its simplest form there could be two variables MAX_AUTO_UID and
24 MAX_AUTO_GID that live in /etc/make.conf or the proposed accounts.xml
25 file that set an upper bound on gentoo assigned UIDs and GIDs. A useful
26 default here could be 500 which is the LSB value
27 (http://www.linuxbase.org/spec/refspecs/LSB_1.3.0/gLSB/gLSB/uidrange.html).
28
29 A more complicated implementation could exclude ranges of UIDs and GIDs
30 using something like UIDS_EXCLUDE=xxxx-xxxx, or UIDS_EXCLUDE=>500. In
31 the case of the former variable, by allowing multiple instaces of these,
32 blocks of UID and GID space could be reserved.
33
34 Baz
35
36
37
38
39
40 --
41 gentoo-dev@g.o mailing list

Replies

Subject Author
Re: [gentoo-dev] Portage Management of UIDs/GIDs Mike Frysinger <vapier@g.o>