Ethan,
I looked into this, and the name of the file as hosted by the install
server
is not even known to manifest-locator service. The file is ascertained via
a POST request and hence the client never has a handle to the file name
as it lives on the server. If we want to record this name in the
install_log,
we need to make changes to accommodate this. Since this applies to
today's manifest XML file as well, I would like to keep this issue separate
from this design if that's okay with you.
I'm ok with that. Should there be a bug to track that issue?
Note: this does have implications on the AI_MANIFEST_SCRIPT variable
that we want to export as an environment variable. The closest thing we
can export is the URL of the install service that served the manifest
script we're running. Hence I would like to define another env variable
named AI_INSTALL_SERVICE for this. We'll keep AI_MANIFEST_SCRIPT
for the case where a full URL to the script is known (for example the
boot-from-media cases), and can also be used for when the above is
addressed for the manifest from install service discovery case.
You mean the SI_MANIFEST_SCRIPT variable, right? Which means an
SI_INSTALL_SERVICE variable?
Sue
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
