We've always said (the JET team), if you've already got it working for you there's little point converting to JET. Some customers have moved to it when moving from bootp to dhcp based SPARC and x64 builds, and sometimes JET has workarounds to new "features" in Solaris as they come out, which makes it easier over time, but a lot of the customers I work directly with have their own large, complex and very impressive Jumpstart infrastructures which work perfectly for them. I can grab JET code snippets to quickly help them add/change things in their own infrastructure. If it ain't broke, don't fix it.
Mike Gerdts wrote: > <<snippet>> > >> (And Mike Gerdts, sorry if someone missold JET to you as a PS only thing, >> I've checked the archives of the external JET mailing list, and you never >> asked that list for anything.... we've given away pretty much every module >> once we knew it wouldn't create a support burden, and most of them are >> available in the sun.com/download bundle anyway) >> (http://wikis.sun.com/display/JET ) >> > > Some of this could be history from several years ago - potentially > attached to an N1 SPS POC. Since I already had JASS fully functional > (including postinstall customizations unrelated to security) there > seemed to be very little reason to convert over to JET. Perhaps > incremental updates over the years would have been easier, but outside > of Sun it was hard to guess which one would be easier to deal with in > the long term. I think that I could have found similar levels of > happiness and frustration on each path. > > Mike -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3249 bytes Desc: S/MIME Cryptographic Signature URL: <http://mail.opensolaris.org/pipermail/caiman-discuss/attachments/20090511/92ecf25a/attachment.bin>
