Is there any way to retrieve/dump a manifest that has been added via 
installadm add?

  Something like 'installadm print -m <manifest> -n <svcname>'?

  I know this data is stored in /var/ai/<some number>/AI_data, but that really 
doesn't seem like a good way to get it - especially since that <some number> 
doesn't seem to correspond to anything convenient.

  I'm looking for a few things here:
- If there is some install problem that is manifest related, it would be nice 
to 
be able to see the actual manifest.  Right now, this would require storing the 
original manifest someplace, and knowing its contents.  This could also be 
useful in cases where the files used to make the manifest have been altered, 
but 
user really wants that original back.

- With opensolaris replacing nevada, I see the need to bring manifests forward 
build to build (as build 132 is put on the server, bringing forward all 
manifests from 131 for 132).  Now there may need to be some minor adjustments 
if 
the build number is included in the manifest.  But as things stand now, I don't 
see any way to do this, other than to keep all the manifests that have been 
added someplace - this is trickier if different people end up adding manifests.

  Jumpstart made this quite easy, since all the data for jumpstart was plainly 
stored (nothing getting copied).  It also made things easy in that one didn't 
need to re-add new jumpstart configs for each new build (could keep pointing at 
same jumpstart directory build after build).  Since each new AI is a new 
service, it starts with nothing for manifests, so all the old ones need to get 
added again.





Reply via email to