Ethan,
A little later than requested, but comments on this update.
An overall nit is that this could use some spell-checking. More typos
than I'm used to :-)
5.2.6: I'm concerned about the "supported scripting types" statement.
This would seem to imply that we'll keep perl 5 (some variant thereof)
part of the installation media. Imminent package refactoring will
remove its historical entanglement with the system core, I believe, so
its presence isn't a given, and I'm somewhat reluctant to commit here.
Python's mildly problematic because of our dependency on it; upgrade to
some later version may put 2.6 on the undesirable list, but I guess
that's something we'd have to address at a larger scale. Perhaps a more
limited commitment initially that excludes perl and is explicit that
only ksh93 is supported of the shells would be advisable?
5.2.6.2: It would be nice to be able to do some testing without having
to boot an AI client. Would it be possible (and sufficient) to package
up the aimanifest command, the aiuser account, and some sort of aitest
command that could run the script in the same sort of environment
(including the environment variables from 5.2.7) as auto-install would?
Seems like this would help you with development, actually :-)
5.2.7: In the SI_MANIFEST_SCRIPT description, is the location the URL?
5.3: Just idly thinking, but would it be helpful to the user to sort out
a way to return both a script and a manifest to the client based on
criteria and thus provide both automatically, so you could do partial
derivation more easily without the "aimanifest load" having to figure
out a URL? Not sure if this creates more problems than it solves, but
thought I'd bring it up.
Dave
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
