None of the legacy code (other than the SVR4 packaging tools) will be opened. There's simply no business case to justify it, and the value of opening the code is negligible--ask those who have to maintain the legacy installer.
Please let me know if you have questions or need more information. Thanks, Eric -- Eric J. Ray Senior Software Engineering Manager Solaris Install Sun Microsystems 303-223-7843 (direct)/x81067 eric.ray at sun.com On May 6, 2009, at 5:41 AM, Mike Gerdts wrote: > On Wed, May 6, 2009 at 2:54 AM, <Casper.Dik at sun.com> wrote: >> >>> On Tue, May 5, 2009 at 6:09 PM, Ellis, Mike <Mike.Ellis at fmr.com> >>> wrote: >>>> PS: At one point the old JumpStart code was encumbered, and the >>>> community wasn't able to assist. I haven't looked at the next-gen >>>> jumpstart framework that was delivered as part of the OpenSolaris >>>> SPARC >>>> preview. Can anyone provide any background/doc-link on that new >>>> JumpStart framework? >>> >>> I think you are looking for the Caiman project. The replacement for >>> jumpstart is the Automated Installer (AI). >>> >>> http://src.opensolaris.org/source/xref/caiman/AI_source/usr/src/ >>> http://www.opensolaris.org/os/project/caiman/auto_install/ >>> >>> This is mostly code developed in the open. I'm not aware of any >>> closed pieces that are specific to the new installer. >> >> >> I don't remember a lot of "closed" parts in the old jumpstart. >> (lu is different) > > Perhaps not closed for the same reasons, but I've not seen the open > sourcing of anything related to installation other than pkgadd/pkgrm > and associated libraries. Perhaps it would be possible to open source > jumpstart but I suspect the motivation of anyone to spend the time to > do so right now is almost none due to the focus on Caiman. >
