On 11/11/10 06:34 PM, Dave Miner wrote: > On 11/ 9/10 12:32 PM, Darren Kenny wrote: >> Hi Karen, >> >> Thanks for the review. >> >> On 10/25/10 11:55 PM, Karen Tung wrote: >>> Hi Darren, >>> >>> Very nice and clear spec, I do have a few comments: >>> >>> - The engine provides the ability to stop/resume. I know that's probably >>> not a normal use case for the AI application. Is there any plan to >>> provide that as a private feature somehow for the AI developers or >>> those debugging AI to save sometime? >> >> It's certainly very likely since I'm sure Matt and myself could use it too, >> should I be documenting this in the design, or just in a README? >> >>> >>> - Section 3.3: dry-run: will it be supported at all? If so, how? >> >> Forgot about dry-run - certainly if checkpoints support it - but I wonder how >> much is feasible in dry-run mode only when doing an install - especially >> around >> the TI stage... >> >> AFAIR some checkpoints (via the Engine) support dry-run, so it should be >> possible to use that, shouldn't it? >> >> Still, it's a developer feature rather than end-user, isn't it? >> >> I may look at adding a 'developer' appendix if it's useful - what do you >> think? >> > > In the JumpStart world, the pfinstall engine was documented so that > users could use it to validate their profiles against various system > configurations. We'd probably want a way to do something like that, > though I'm not wedded to that particular approach. >
Wouldn't that be similar to the auto-install -i option which stops before TI? We are planning on implementing all the existing options. Darren. _______________________________________________ caiman-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
