The AI manifest and SC manifest tags shown here are out of date. More up-to-date is here: http://docs.sun.com/app/docs/doc/820-6566/js2ai
On Wed, 8 Dec 2010 17:49:27 -0700 (MST), [email protected] wrote: > Hi Lao Tsao, > No, using JumpStart is not supported; one must use the Solaris > Automated Installer. A resource explaining the differences can be found > at: > http://wikis.sun.com/display/OpenSolarisInfo/Solaris+JumpStart+to+OpenSolaris+Automated+Installation > > Thank you, > Clay > > On Wed, 8 Dec 2010, "LaoTsao 老曹 Ph. D." wrote: > >> hi >> may be someone ask before, the answer is no >> >> can one use s10 jumpstart to install s11x? >> TIA >> >> >> On 12/8/2010 4:49 PM, [email protected] wrote: >>> Send caiman-discuss mailing list submissions to >>> [email protected] >>> >>> To subscribe or unsubscribe via the World Wide Web, visit >>> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss >>> or, via email, send a message with subject or body 'help' to >>> [email protected] >>> >>> You can reach the person managing the list at >>> [email protected] >>> >>> When replying, please edit your Subject line so it is more specific >>> than "Re: Contents of caiman-discuss digest..." >>> >>> >>> Today's Topics: >>> >>> 1. Re: RFE: Finish Script hook (Scott Dickson) >>> 2. Re: RFE: Finish Script hook (Ethan Quach) >>> 3. Re: RFE: Finish Script hook (Shawn Walker) >>> 4. Re: Logging AI progress to the console? (Seth Goldberg) >>> 5. Re: RFE: Finish Script hook (Dave Miner) >>> >>> >>> ---------------------------------------------------------------------- >>> >>> Message: 1 >>> Date: Wed, 08 Dec 2010 16:32:46 -0500 >>> From: Scott Dickson<[email protected]> >>> To: Dave Miner<[email protected]> >>> Cc: caiman-discuss<[email protected]> >>> Subject: Re: [caiman-discuss] RFE: Finish Script hook >>> Message-ID:<[email protected]> >>> Content-Type: text/plain; charset="utf-8"; Format="flowed" >>> >>> >>> >>> On 12/ 8/10 03:21 PM, Dave Miner wrote: >>>> On 12/ 8/10 02:48 PM, Scott Dickson wrote: >>>>> Looking at AI (and even bootable AI), finish scripts are sort of a >>>>> hassle. >>>>> >>>>> It appears that if I want to have my own finish scripts, there's a lot >>>>> of overhead: I have to bundle it all up into a package, complete with >>>>> SMF manifest and activations, put it into my own repository, make >>>>> sure I >>>>> install that package, and *then* do whatever I wanted the finish >>>>> script >>>>> to do. Seems a lot. >>>>> >>>>> What about having an almost empty package that I can add, for the sake >>>>> of discussion service/finish-script, that includes the SMF >>>>> infrastructure to make it execute at first boot (and only first boot), >>>>> along with a named exit that I can use for the payload. So, this >>>>> package >>>>> provides a null script called /etc/init.d/finish-script, for example. >>>>> I >>>>> can then either put my code there or make it call my code. >>>>> >>>>> This really reduces the overhead in terms of development for adoption. >>>>> Having do build my own packages, using the distro constructor, or >>>>> anything like that is way too burdensome. >>>>> >>>>> Or have I missed something really simple here? >>>>> >>>> Scott, we've been discussing ways we might make this process easier. >>>> One thing I don't understand is how you're proposing to deliver the >>>> contents of your hypothetical /etc/init.d/finish-script to an AI >>>> client? >>>> >>>> Constructing an SMF manifest and IPS package is really not that >>>> difficult, though I agree it's daunting at first to figure it out from >>>> the pretty general documentation that SMF and pkg provide. I'm >>>> looking to provide a pretty simple cookbook approach real soon that >>>> should shorten the distance to happiness while we consider >>>> enhancements that could make this >>> A lot of the customers I talk to already have an NFS infrastructure that >>> they use to deliver the finish scripts, the packages they load, etc. >>> But that doesn't really help here. Clearly, I had no thought through >>> the entire process. >>> >>> I suppose my notion was that I would want to leverage existing >>> infrastructure as much as possible. >>> >>> I guess this very quickly gets to a chicken& egg scenario. Even with a >>> well known name for the hook, as you asked, how to get that content to >>> the system. And presuming the NFS world or something strange like that >>> is almost always going to fail to suffice. >>> >>> This really isn't an easy problem. Folks often have very complicated >>> scenarios. Perhaps an easy, canned cookbook to set up a minimal repo on >>> whatever system they would have used for their finish scripts would be >>> the best bet. >>> >>> The thing I keep coming back to is the simpler this is, the more it >>> wears down the adoption hurdle. If I have to figure out all of this >>> just to install a server in my environment, it's going to really slow >>> down folks adoption. >>> >>> --SCott >>>> easier. >>>> >>>> Dave >> > > > -- > Limited filtering has been provided due to external email forwarding. > For details please review: http://www.onlymyemail.com/faqs/forwarding.html _______________________________________________ caiman-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
