Darren Reed wrote:
In putting together PSARC/2009/332 and looking at the
changes required to libraries and installation, I'm
being given a choice about whether or not the project
number for "svc.inetd" is important.
The man page for project(4) says this:
projid The project's unique numerical ID (PROJID)
within the system. The maximum value of the
projid field is MAXPROJID. Project IDs below
100 are reserved for the use of the operating
system.
I suspect that this is a carryover from usernames, uids
and /etc/passwd in that so far as I can tell, the project
id's are not important in the same way that a uid is.
Whilst it is convenient to have project numbers be the
same everywhere, there's no operational requirement.
Unlike files, where the uid is a property that can be
saved/restored/copied, the project id for "user.root"
could be different on every system and there would be
no interoperability or behavioural problems.
The man page isn't stating a requirment that project numbers be the
same everywhere, it is simply reserving space for the operating
system... and reserving space for our users. Project configuration
can be read from a directory service just like users and groups, so
letting a client define project ids beyond 100 means you can have
collisions between it and the networked environment in which it's
placed.
It might be the case that fixed project IDs were an anachronism best
replaced by a dynamic, system-local ID mechanism, but unfortunately
it's probably too late to change that.
2) As part of the work for PSARC/2009/332, I'm putting
together a "i.project" file to add the "svc.inetd"
project to existing /etc/project files when people
do an upgrade. The obvious thing to do is to add it
to the file in a way that makes it identical to the
/etc/project that gets committed. But there is no
operational need that I can see for that to happen.
Have you determined how this will work under IPS?
Dave
_______________________________________________
opensolaris-code mailing list
opensolaris-code@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code