1 |
Martin Lesser writes: |
2 |
> Grant Goodyear <g2boojum@g.o> writes: |
3 |
> > Unfortunately, we don't have a good answer to that question just yet. |
4 |
> > The plan is to generate a table of already-taken uid/gid numbers |
5 |
> > ... My best suggestion at the moment is to see what numbers debian is |
6 |
> > using for your package, check to see if they conflict with anything we |
7 |
> > have (take a look at the above "database" as well as the passwd and |
8 |
> > group files at |
9 |
> > http://cvs.gentoo.org/cgi-bin/viewcvs.cgi/gentoo-src/rc-scripts/etc/), |
10 |
> > and go from there. |
11 |
> |
12 |
> 1. Several uid's/gid's differ from other distris (debian i.e. assigns |
13 |
> 2. In /etc/passwd from baselayout there are several users predefined |
14 |
> 3. If one runs openldap for authentification and nss one don't want to |
15 |
> 1. The predefined entries in /etc/passwd should be reduced to exactly 1 |
16 |
> 2. The current ebuilds which assign _fixed_ uids/gids could be fixed so |
17 |
> |
18 |
> I don't see any benefits of developing and/or maintaining a predefined |
19 |
> /etc/passwd with more than exactly one entry for root. |
20 |
|
21 |
/etc/passwd and /etc/group must not be managed by UID/GID! |
22 |
|
23 |
Each package may ask for a set of user names and group names, and the |
24 |
local system administrator can assign whatever UID/GID to these names. |
25 |
|
26 |
Note that dependending on the underliying system, you may have |
27 |
different constraints on these UID/GID. Like having ID<100 for |
28 |
auto-su-able or things like that. |
29 |
|
30 |
For example, tar stores the names of the owner and group of each file |
31 |
in its archives. |
32 |
|
33 |
|
34 |
-- |
35 |
__Pascal_Bourguignon__ http://www.informatimago.com/ |
36 |
---------------------------------------------------------------------- |
37 |
Do not adjust your mind, there is a fault in reality. |
38 |
|
39 |
-- |
40 |
gentoo-dev@g.o mailing list |