1 |
Paul de Vrieze <pauldv@g.o> writes: |
2 |
|
3 |
> On Saturday 31 May 2003 10:53, Martin Lesser wrote: |
4 |
> > IMO a clearer approach could be: |
5 |
> > |
6 |
> > 1. The predefined entries in /etc/passwd should be reduced to exactly 1 |
7 |
> > entry for root, all other (system-)users could be created dynamicly |
8 |
> > by the ebuilds without assigning a fixed uid/gid. |
9 |
> Almost agreed, users like nobody and others are also required in |
10 |
> baselayout, but the idea is ok. |
11 |
|
12 |
You're right: users daemon, man etc. are required for a running system |
13 |
but i.e. user man could also be checked/added by the ebuild for man or |
14 |
man-pages. Almost every system-user could be added by the appropriate |
15 |
ebuild so one gets a really 'clean' passwd where only the real used |
16 |
users appear. Ok, one had to run etc-update more often when setting up |
17 |
new services, but that's not bad at all. |
18 |
|
19 |
> > 2. The current ebuilds which assign _fixed_ uids/gids could be fixed so |
20 |
> > they don't use the appropriate useradd/groupadd options any longer. |
21 |
> They should be indeed. |
22 |
|
23 |
I got a perhaps helpful list of 44 ebuilds where fixed uid's are used |
24 |
with |
25 |
|
26 |
# find /usr/portage -name '*ebuild' | \ |
27 |
xargs grep 'useradd .*-u *[0-9]' | \ |
28 |
sort -u | cut -f1 -d':' | cut -f4- -d'/' |
29 |
|
30 |
Not sure whether this result is complete. |
31 |
|
32 |
Should lintool also check the use of fixed uid's and report this as |
33 |
error? |
34 |
|
35 |
And coming back to my original question concerning nullmailer: I will |
36 |
create my ebuild without a fixed uid/gid and hope that it will not |
37 |
collide with any other ebuild used in future. |
38 |
|
39 |
Martin |
40 |
|
41 |
|
42 |
-- |
43 |
gentoo-dev@g.o mailing list |