Tom Mueller wrote: > Bart, > > Where is image.is_liveroot used? I wasn't able to find a call to it in > the new code. It's not clear what the intention of this method is.
This is actually part of another action I'm working on.... it's not used yet. > Given a user image with a non-root user running the pkg commands, what > is the expected behavior of file and directory actions in the presence > of these actions? they're broken; we could choose to ignore them, I suppose. > > Specifically, the user and group actions will add these entries to the > passwd and group files that are local to the image, and the file and > directory actions will then be able to translate user and group names to > ids during installation of a file/directory, but the action will still > not be able to change the ownership of the file/dir to another user. > (I'm not sure than anything else can be done on this.) > That's ignored anyway. > Maybe it would be appropriate to provide the ability in the file and > directory actions to specify that the file ownership should just be that > of the user that is running pkg. > That's what happens now. For user images, we'll likely just filter out actions that make no sense. Driver, user,group, service, etc are all pretty useless. - Bart -- Bart Smaalders Solaris Kernel Performance [EMAIL PROTECTED] http://blogs.sun.com/barts "You will contribute more with mercurial than with thunderbird." _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
