Looks like your failures happened in driver installation. Do you see a stack trace in the output of "pkg history -l" that corresponds to these? (You'll have to mount the BE you were operating on with beadm, and run "pkg -R /mntpoint ...".)
You clearly had sufficient permissions to remove and add files; the only thing I can think of that would cause an OSError with EACCES is an exec you didn't have sufficient perms for. But add_drv shouldn't have that problem, just that it would exit 1 if you weren't root. You could try trussing the image-update and see what it is that fails. (You probably will want truss -fa.) Also, why are you doing an image-update anyway? It's not guaranteed to work after a bfu -- the way you should be testing bfu archives is to bfu an alternate boot environment, boot to that, and then revert to your normal, non-BFUed environment. Danek _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
