Danek Duvall wrote:
On Thu, Aug 06, 2009 at 08:21:09AM -0400, Anurag S. Maskey wrote:
I am not worried about when the project integrates. I think the
ips team (or some other group) takes care of adding the new
users, groups, etc.
No it isn't the ips team or some other team. As I said that is
your responsibility as the project team to add it to the base
passwd/shadow/group files in ON.
Yes, we've already made the changes to files in usr/src/Adm/sun/.
The IPS user actions cause those updates to be added.
I am very confused here.
At the moment, Nevada is still the target. That means that for putback,
you need to update the passwd file in ON, as well as i.passwd, to make sure
that the new user gets added to the system on install/upgrade. Similarly
for the group file, and the RBAC databases.
Also at the moment, while OpenSolaris is being constructed out of a fully
built Nevada WOS, every time someone updates one of these files, the pkg(5)
team (Comay, primarily) has to update the appropriate import file in the
pkg(5) gate to do the same thing -- add a new user or group action in the
right package, or update the fully-built RBAC database file.
This latter is what you're trying to do, specifically so that you can test
an OpenSolaris install and upgrade with your bits. It is, I think, way
more than most project teams attempt, but it's certainly appreciated.
The primary user of nwam phase 1 is using OpenSolaris. So, we're trying
to test how upgrading from phase 0/0.5 will go for these users. We also
need to test install. The current target for the project is 2010.02,
which means before build 125. So, things may be easier in the future,
but we need to test our project now (other than with BFUs).
My ips source is at changeset 1291. I and the NWAM team would greatly
appreciate if any one of you experts took a look at NWAM's webrev and
generated specific files/instructions on how to get the authorizations
into the repository as of my changeset. I already got the users, groups
in there. If not, then I'm just going to have to put up a one page
instructions detailing the changes to users, auths before running
image-update. Yes, good things are coming in the future ......
Anurag
In the long run, though, you won't have to make updates in two places --
you'll add user and group actions directly into pkg(5)-style package
manifests in whatever consolidation you're working in, and won't have to
update a central file in ON (any centralization of user and group data will
likely need to become a function of the ARCs), and you'll just add a
fragment of an RBAC database into the appropriate directory (as I described
yesterday; this is almost working today).
Danek
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
