On Wed, Mar 25, 2009 at 08:05:50AM -0600, Eric J. Ray wrote: > >> I look over the AIinstall document. I can't find some methods > >>like jumpstart postscripts. > >> > > No, at this time those do not exist. That's deliberate. In many (most) > cases, Jumpstart finish scripts exist to work around gaps in the > feature set or implementation. We want to understand what the real > requirements are and build those into the product. > > [...] > > The generic solution is to have a package that uses an SMF first-boot > property to make changes like this. Alternatively, you can use the > Distribution Constructor to create a custom image.
Note that to a customer the two solutions look exactly the same: "I have to write some script and plug it in." In this sense a change to the environment of the script and how to plug it in is merely annoying, not fatal. A very useful enhancement would be to provide for automatic IPS packaging of what-would-have-been-finish-scripts. But also, I think that Casper's points about the desirability of Jumpstart finish scripts should not be dismissed. To me the IPS philosophy of no package scripting is great and to be commended, but it's not clear to me that this philosophy necessarily extends fully to automated installation. Clearly it does to some degree: it's better to run scripts in the context of the booted installed image than in a highly constrained diskless boot environment. But that's not always so. As Casper has pointed out there are many things that one might want to run from the diskless install environment, including completely obviating the IPS image install in the case of AI being used for installing things other than OpenSolaris. Nico --
