Ethan,
On 05/04/10 14:50, Sue Sohn wrote:
On 04/23/10 19:47, Ethan Quach wrote:
>
> I have posted a revision to the derived manifest design.
>
> (I've removed the pieces about an interactive manifest CLI on
> the server side, as that needs to be a separate design.)
>
>
http://hub.opensolaris.org/bin/download/Project+caiman/DerivedManifests/DerivedManifestsDesignSpec.pdf
>
>
>
> Please review. Comments appreciated.
>
> thanks,
> -ethan
>
>
>
> _______________________________________________
> caiman-discuss mailing list
> [email protected]
> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
[removed items where I had no further comment]
If verify fails during manifest derivation during an install, then I
assume the installation would fail. What information is provided to
the user in that case and where? Will it be apparent from the
install_log as to what happened?
If you're talking about an "aimanifest verify" call from within the script,
no, that wouldn't cause installation to fail. At the point when the script
finishes execution (with success), the DMM is going to validate the
manifest
at that time, and if it fails to validate then, installation process
will stop.
So if someone was called in to look at a machine where the installation has
stopped in this manner, but didn't know that derived manifests has been
involved, what information would be available to figure out what happened?
Sue
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
