From Sarah.Jelinek@sun.com Wed May 23 17:01:04 2007
Received: from sunmail4.Singapore.Sun.COM (sunmail4.Singapore.Sun.COM [129.158.71.19])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l4O013CA016903
	for <psarc-ext@sac.sfbay.Sun.COM>; Wed, 23 May 2007 17:01:04 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail4.Singapore.Sun.COM (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id l4NNxmic010529
	for <@sunmail3mpk.sfbay.sun.com:psarc-ext@sun.com>; Thu, 24 May 2007 07:59:49 +0800 (SGT)
Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by
 nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0JII00D05QNNDC00@nwk-avmta-2.sfbay.sun.com> for psarc-ext@sun.com
 (ORCPT psarc-ext@sun.com); Wed, 23 May 2007 16:59:47 -0700 (PDT)
Received: from brmea-mail-4.sun.com ([192.18.98.36])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JII00ALMQNMQV40@nwk-avmta-2.sfbay.sun.com> for
 psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed,
 23 May 2007 16:59:46 -0700 (PDT)
Received: from fe-amer-01.sun.com ([192.18.108.175])
	by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l4NNxklw009944	for
 <psarc-ext@sun.com>; Wed, 23 May 2007 23:59:46 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 id <0JII00B01QBM0H00@mail-amer.sun.com>
 (original mail from Sarah.Jelinek@Sun.COM)
 for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed,
 23 May 2007 17:59:45 -0600 (MDT)
Received: from [192.9.61.46] by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 with ESMTPSA id <0JII00IRSQNBT7V2@mail-amer.sun.com> for psarc-ext@sun.com
 (ORCPT psarc-ext@sun.com); Wed, 23 May 2007 17:59:37 -0600 (MDT)
Date: Wed, 23 May 2007 17:59:34 -0600
From: Sarah Jelinek <Sarah.Jelinek@sun.com>
Subject: Fast track review - PSARC/2007/284 Dwarf Caiman,
 New Solaris Install GUI
Sender: Sarah.Jelinek@sun.com
To: psarc-ext@sun.com
Reply-to: Sarah.Jelinek@sun.com
Message-id: <4654D566.1090101@sun.com>
MIME-version: 1.0
Content-type: multipart/mixed; boundary="Boundary_(ID_k/c/7NJlsp8LLz0/1t2t5w)"
X-PMX-Version: 5.2.0.264296
User-Agent: Thunderbird 2.0b2 (X11/20070326)
Status: RO
Content-Length: 12073

This is a multi-part message in MIME format.

--Boundary_(ID_k/c/7NJlsp8LLz0/1t2t5w)
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT

Hi All,

I am sponsoring the following fast track for myself. It times out on 
5/30/2007. It is related to the umbrella case, PSARC/2007/039, Caiman: 
New Solaris Install Experience, which is scheduled for inception review 
next Wed, 5/30/2007.

This fast track represents the first installment of projects that will 
comprise the full Caiman experience.

The attached spec, and  other materials as noted are posted in the case 
directory as well.

Regards,
Sarah Jelinek

--Boundary_(ID_k/c/7NJlsp8LLz0/1t2t5w)
Content-type: text/plain; name=dwarf_caiman.txt
Content-transfer-encoding: 7BIT
Content-disposition: inline; filename=dwarf_caiman.txt

Name(s) of person (s) answer questions?

        Sarah Jelinek

1. What specifically is the proposal that we are reviewing?

	Fast track request for PSARC/2007/284.

	The 1st project, in a series of planned projects, for the New	
	Solaris Installer(NSI) program, formerly known as Caiman. 

	This project, Dwarf Caiman, will deliver a subset
	of the overall NSI program plans as outlined in PSARC/2007/039, 
	suitable for the graphical installation path for the Solaris Express
	Developer Edition release. 

	This project is also related to the Solaris Express Developer Edition
	project that was presented in PSARC/2006/687. 


2. Project Summary:

	Dwarf Caiman is the first of many Solaris install projects aimed
	at fulfilling the strategy outlined in: 

http://www.opensolaris.org/os/community/install/files/install_strategy.pdf. 

	This project is not intended to replace the general Solaris installer 
	GUI, nor does it modify the existing character and command-line 
	interfaces.

	It provides a streamlined installation experience with a totally
	new look and feel for the graphical user interface. The focus
	is on branding and usability of the GUI. It also provides the 
	beginnings of the New Solaris Installer architecture.

	Specific details as to what features Dwarf Caiman will
	provide are listed below.

	We are requesting a minor release binding.

3.0 Technical details

3.1 Project Requirements

	3.1.1 General:
		1. x86 platform support only. Sparc bits will be built, but
		   there is no boot support for Developer Edition on sparc.

		2. DVD distribution only.

		3. Support for installation and upgrade from the SUNWCXall
		   metacluster only. No software selection offered.

		4. No additional product install offered.
		   
	3.1.2 Initial Install:
		1. Solaris Initial Installation targets supported:
			a) Whole disks only
			b) Behaviors:

				-Disk chosen by user will be, by default, 
				partitioned as 1 Solaris2 fdisk partition.

				-If user chooses the non-default option of 
				partitioning the disk chosen, the existing 
				Solaris2 partition, if it exists will be used 
				as the installation target by default.

				-The disk chosen can be repartitioned to 
				include only 1 Solaris2 fdisk partition.

				-All existing non-Solaris2 fdisk partitions 
				will be preserved if there is adequate 
			        space in the Solaris2 partition for 
				installation if the user makes no
				changes that would change the start block or
				length of the existing partitions.

			c) filesystem layout:

				-Solaris fdisk partition will be resliced with 
				default filesystem layout. Default layout will
				be as follows: 
					TBD*


			d) Existing User Data:
				-There will be no option for the user to select 
				 slices to preserve with initial installation.

		2. Other user selections offered with initial install:
			a) See GUI mockup as noted in [1].

	3.1.2.1 Initial install scenario examples
		1. The user allows default selections for all of the
		   installation process. This results in:
			-The disk target chosen being partitioned as 1 Solaris2
			 fdisk partition.

			-Default filesystems configured for the Solaris
			 installation.
		
			-All existing data on disk chosen is overwritten.

		2. The user selects to utilize the existing fdisk partitions
		   on the selected disk target. This results in:
			-The installation of Solaris will occur on the
			 existing Solaris2 fdisk partition. Any 
			 previous data on this partition will be 
			 overwritten.
		
			-All other partition data will be untouched.
	
			-Default filesystems will be configured for 
			 the Solaris installation.

		3. The user selects to customize the fdisk partition
		   layout on the selected disk target by enlarging
		   the existing Solaris2 fdisk partition, which is
		   partition 2. This results in:
			-The installation of Solaris will occur on this
			 resized Solaris2 fdisk partition.

			-Partition 1 will remain unchanged. Any data
			 that exists on this partition will remain 
			 accessible.
		
			-Partitions 3 and 4, if they exist, and if
			 they are of the allowed partition types
			 Solaris can create, will be
			 rewritten with a new start block and length. 
			 All existing data on the original partitions will
			 not be accessible due to the change of the fdisk
			 partition data for these.

			-If Partitons 3 and 4 are fdisk types that Solaris
			 cannot currently create, we will delete the old
			 partitions to create the new partition 2, 
			 and the remaining space on the disk will be
			 left unallocated. The user can change this after
			 utilizing the partition tool of their choice.

			-Default filesystem will be configured for the
			 Solaris installation.

	3.1.3 Upgrade:
		1. Solaris Upgrade targets supported:
			a) Solaris root slice in a VTOC labeled fdisk partition 
			b) Attributes:

				-Within slices discovered, partition tags 
				 labeled 'root' and 'unassigned' (the latter, 
				 for the cases of freshly installed 
				 Solaris' and LUs that have not yet been 
				 activated)

				-root slice must mount successfully

				-/var, if installed on a separate slice, 
				 as found in /etc/vfstab, must mount
				 successfully.

				-/var/sadm/softinfo/INST_RELEASE file is
				 present and readable.

				-/var/sadm/system/CLUSTER file is 
				 present and readable.

				-/var/sadm/system/.clustertoc file is
			 	present and readable.

				-/boot/solaris/bootenv.rc on X86 is
				present.
	
				-All non-global zones associated with 
				the root must be upgradable.

				-/usr packages present

				-Solaris version must be one of a previous
				 SXDE build.  It will also allow upgrade from 
				 Solaris Express Community Edition releases
				 that coincide with the SXDE releases.
				

		2. Solaris upgrade targets not supported:
			a) Solaris instance whose root resides on SVM 

			b) Solaris instance has non-global zones configured that
	  		   are on an SVM metadevice

			c) Solaris instance has non-global zones with ZFS root

	3.1.3.1 Solaris Upgrade Scenario examples

		1. User chooses valid upgrade target. Size of root is
		   sufficient to handle the upgrade. This results in:
			-Upgrade is performed.

			-All existing data is preserved.

			-No fdisk partition data is modified.

		2. User chooses invalid upgrade target. This results in:
			-Message displayed as to why the target is not
			 a valid upgrade target. A warning symbol will
			 have been displayed for this listed target
			 so that the user should be aware of its status.

			-No changes occur.

	3.1.4 The SunStudio and NetBeans tools:

		1. Initial Install:

			a) Installation behavior and scripts are provided by
			   the Developer tools team. 

			b) During initial install Sun Studio 12 will be 
			   installed.

			c) During intial install Sun Studio 12 will install
			   NetBeans 5.5.1 as it currently ships this
			   version.

			d) NetBeans 5.5 will also be installed since
			   NetBeans users are supposed to use this version, 
			   and not 5.5.1.

		2. Upgrade: 
			a) Upgrade behavior and scripts are provided by 
			   tools team.

			b) If supported tools are currently installed on 
			   system, they will not be upgraded to Sun 
			   Studio 12. 

			c) If tools not currently installed on system, Sun 
			   Studio 12 will be installed during upgrade.


4.0 Interfaces

4.1 EXPORTED INTERFACES:
                          Proposed            Specified       Former Stability
Interface                 Stability           in what         Classification
Name                      Classification      document?       or Other Comments
------------------------------------------------------------------------------
Dwarf GUI		 Uncommitted		[1],[9]	

liborchestrator.so.1	 Project Private	[2]	

libtd.so.1		 Project Private	[3]	

soldevx			 Committed		PSARC/2006/687	Boot property
								set by GRUB
								menu



4.2 IMPORTED INTERFACES:
                          Proposed            Specified       Former Stability
Interface                 Stability           in what         Classification
Name                      Classification      document?       or Other Comments
------------------------------------------------------------------------------
libdiskmgt.so.1					LSARC/2004/743  Consolidation
								Private**
					
libnvpair.so.1					[4], [5], [6]   Committed
								(Evolving)

libsvm.so.1				 	[7], [8]	Consolidation
							        Private***

libdevinfo.so.1					PSARC/1997/127	Committed
								(Evolving)

Developer tools scripts				PSARC/2006/687  Committed


4.3 Interface Notes:

**Contract submitted to owning team, ZFS. Received approval from Dave Brittle,
  RM for ZFS. Contract in case materials, PSARC/2007/284.

***Contract already secured with SVM team. See [7] and [8] below. 

5. Misc 

	5.1 UIRB review
		We have currently filed a case as noted in [9] below
		for UIRB review. The expectation is that while this
		review is not required at this time for Dwarf Caiman,
		since the UI is specifically targeted at developers and
		not system administrators, we will be conducting UIRB
		reviews for every release of the new Installer.

		It is expected that this initial UIRB review will be handled
		via email.

	5.2 Memory Requirements
		The current memory requirements to boot and install
		Solaris Express Developer Edition 1 and 2 is 768MB. This
		is due to several factors:
			-The need for Java to be loaded in to ramdisk
			 the current Developer Express Java GUI.
			-The size of the miniroot due to additional
			 required packages.

		For Dwarf Caiman we are actively trying to reduce the
		minimum size required for memory by the following:
			-Remove the need for Java: 
				-The Dwarf GUI is implemented
				 using Gnome and in C. 

				-We will not require the existing Solaris 
				 Install 'launcher' code to install the 
				 Sun Studio tools. The 'launcher' is
				 implemented with Java.
	
				-Created a separate root archive for the
				 Dwarf Caiman bits to allow for trimming
				 of unnecessary packages for this installation
				 path.
		
		No testing has been done to validate that these steps will
		reduce the memory requirement.  The addition of
		new Gnome packages required for the Dwarf GUI along with
		the addition of any new miniroot packages in support
		of new features such as Xen may mean we don't see a 
		substantial reduction in the memory requirements.

6. Documentation:

[1] Xdesign Dwarf Caiman GUI Mockup:
http://xdesign.sfbay/projects/solaris/subprojects/install/design/dwarf/

[2] Dwarf Caiman Orchestrator design document:
http://opensolaris.org/os/project/caiman/files/dwarf_caiman_design.pdf

[3] Dwarf Caiman Target Discovery design document:
http://opensolaris.org/os/project/caiman/files/dwarf_td_design.pdf

[4] PSARC/2000/212 - libnvpair - A Name Value Pairs library

[5] PSARC/2003/121 - Extension to libnvpair

[6] PSARC/2003/252 - Another libnvpair extension

[7] PSARC/2000/049 - Solaris logical volume manager upgrade

[8] PSARC/2001/341 - SVM -Upgrade Contract Interfaces 

[9] UIRB/2007/264 - http://sac.sfbay.sun.com/Archives/CaseLog/rb/UIRB/2007/264/,
		    Dwarf Caiman UIRB Review Materials


--Boundary_(ID_k/c/7NJlsp8LLz0/1t2t5w)--

From Michael.Riley@sun.com Wed May 23 17:40:35 2007
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l4O0eYiR017386
	for <psarc-ext@sac.sfbay.sun.com>; Wed, 23 May 2007 17:40:34 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail5.uk.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l4O0dHOP012795
	for <@sunmail3mpk.sfbay.sun.com:psarc-ext@sun.com>; Thu, 24 May 2007 01:39:20 +0100 (BST)
Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by
 nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0JII00F0JSHJH100@nwk-avmta-2.sfbay.sun.com> for psarc-ext@sun.com
 (ORCPT psarc-ext@sun.com); Wed, 23 May 2007 17:39:19 -0700 (PDT)
Received: from nwk-ea-fw-1.sun.com ([10.4.134.6]) by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JII00APGSHIQU80@nwk-avmta-2.sfbay.sun.com> for
 psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed,
 23 May 2007 17:39:18 -0700 (PDT)
Received: from d1-sfbay-10.sun.com ([192.18.39.120])
	by nwk-ea-fw-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l4O0dIJo001167	for
 <psarc-ext@sun.com>; Wed, 23 May 2007 17:39:18 -0700 (PDT)
Received: from conversion-daemon.d1-sfbay-10.sun.com by d1-sfbay-10.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 id <0JII00J01SC97900@d1-sfbay-10.sun.com>
 (original mail from Michael.Riley@Sun.COM)
 for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed,
 23 May 2007 17:39:18 -0700 (PDT)
Received: from [129.148.19.22] by d1-sfbay-10.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 with ESMTPSA id <0JII006RWSHGHC43@d1-sfbay-10.sun.com> for psarc-ext@sun.com
 (ORCPT psarc-ext@sun.com); Wed, 23 May 2007 17:39:17 -0700 (PDT)
Date: Wed, 23 May 2007 17:39:12 -0700
From: Mike Riley <Michael.Riley@sun.com>
Subject: Re: Fast track review - PSARC/2007/284 Dwarf Caiman,
 New Solaris Install GUI
In-reply-to: <4654D566.1090101@sun.com>
Sender: Michael.Riley@sun.com
To: Sarah.Jelinek@sun.com
Cc: psarc-ext@sun.com
Message-id: <4654DEB0.1050301@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.2.0.264296
References: <4654D566.1090101@sun.com>
User-Agent: Thunderbird 1.5.0.7 (X11/20060915)
Status: RO
Content-Length: 13357

Hi Sarah,

I had a couple of questions after reading this.

1) Is only Solaris2 fdisk partitions supported by this?  According to the 
dwarf_td_design.pdf document it sounds like it is supposed to also support the 
older Solaris partition type by validating the contents to verify it is not a 
Linux swap partition.  You seem to outline those steps under item 1 of section 
3.1.3 for Upgrades, but every time and fdisk partition is mentioned you say it 
must be a Solaris2 type.

2) I applaud that it has the capability to resize a Solaris fdisk partition as 
described in 3.1.2.1, item #3.  But why is this capability not provided as part 
of the Upgrade as well?  That is usually the case where you might need to expand 
an existing Solaris partition, as opposed to the Initial install where you are 
offering that ability.

Mike

Sarah Jelinek wrote:
> Hi All,
> 
> I am sponsoring the following fast track for myself. It times out on 
> 5/30/2007. It is related to the umbrella case, PSARC/2007/039, Caiman: 
> New Solaris Install Experience, which is scheduled for inception review 
> next Wed, 5/30/2007.
> 
> This fast track represents the first installment of projects that will 
> comprise the full Caiman experience.
> 
> The attached spec, and  other materials as noted are posted in the case 
> directory as well.
> 
> Regards,
> Sarah Jelinek
> 
> 
> ------------------------------------------------------------------------
> 
> Name(s) of person (s) answer questions?
> 
>         Sarah Jelinek
> 
> 1. What specifically is the proposal that we are reviewing?
> 
> 	Fast track request for PSARC/2007/284.
> 
> 	The 1st project, in a series of planned projects, for the New	
> 	Solaris Installer(NSI) program, formerly known as Caiman. 
> 
> 	This project, Dwarf Caiman, will deliver a subset
> 	of the overall NSI program plans as outlined in PSARC/2007/039, 
> 	suitable for the graphical installation path for the Solaris Express
> 	Developer Edition release. 
> 
> 	This project is also related to the Solaris Express Developer Edition
> 	project that was presented in PSARC/2006/687. 
> 
> 
> 2. Project Summary:
> 
> 	Dwarf Caiman is the first of many Solaris install projects aimed
> 	at fulfilling the strategy outlined in: 
> 
> http://www.opensolaris.org/os/community/install/files/install_strategy.pdf. 
> 
> 	This project is not intended to replace the general Solaris installer 
> 	GUI, nor does it modify the existing character and command-line 
> 	interfaces.
> 
> 	It provides a streamlined installation experience with a totally
> 	new look and feel for the graphical user interface. The focus
> 	is on branding and usability of the GUI. It also provides the 
> 	beginnings of the New Solaris Installer architecture.
> 
> 	Specific details as to what features Dwarf Caiman will
> 	provide are listed below.
> 
> 	We are requesting a minor release binding.
> 
> 3.0 Technical details
> 
> 3.1 Project Requirements
> 
> 	3.1.1 General:
> 		1. x86 platform support only. Sparc bits will be built, but
> 		   there is no boot support for Developer Edition on sparc.
> 
> 		2. DVD distribution only.
> 
> 		3. Support for installation and upgrade from the SUNWCXall
> 		   metacluster only. No software selection offered.
> 
> 		4. No additional product install offered.
> 		   
> 	3.1.2 Initial Install:
> 		1. Solaris Initial Installation targets supported:
> 			a) Whole disks only
> 			b) Behaviors:
> 
> 				-Disk chosen by user will be, by default, 
> 				partitioned as 1 Solaris2 fdisk partition.
> 
> 				-If user chooses the non-default option of 
> 				partitioning the disk chosen, the existing 
> 				Solaris2 partition, if it exists will be used 
> 				as the installation target by default.
> 
> 				-The disk chosen can be repartitioned to 
> 				include only 1 Solaris2 fdisk partition.
> 
> 				-All existing non-Solaris2 fdisk partitions 
> 				will be preserved if there is adequate 
> 			        space in the Solaris2 partition for 
> 				installation if the user makes no
> 				changes that would change the start block or
> 				length of the existing partitions.
> 
> 			c) filesystem layout:
> 
> 				-Solaris fdisk partition will be resliced with 
> 				default filesystem layout. Default layout will
> 				be as follows: 
> 					TBD*
> 
> 
> 			d) Existing User Data:
> 				-There will be no option for the user to select 
> 				 slices to preserve with initial installation.
> 
> 		2. Other user selections offered with initial install:
> 			a) See GUI mockup as noted in [1].
> 
> 	3.1.2.1 Initial install scenario examples
> 		1. The user allows default selections for all of the
> 		   installation process. This results in:
> 			-The disk target chosen being partitioned as 1 Solaris2
> 			 fdisk partition.
> 
> 			-Default filesystems configured for the Solaris
> 			 installation.
> 		
> 			-All existing data on disk chosen is overwritten.
> 
> 		2. The user selects to utilize the existing fdisk partitions
> 		   on the selected disk target. This results in:
> 			-The installation of Solaris will occur on the
> 			 existing Solaris2 fdisk partition. Any 
> 			 previous data on this partition will be 
> 			 overwritten.
> 		
> 			-All other partition data will be untouched.
> 	
> 			-Default filesystems will be configured for 
> 			 the Solaris installation.
> 
> 		3. The user selects to customize the fdisk partition
> 		   layout on the selected disk target by enlarging
> 		   the existing Solaris2 fdisk partition, which is
> 		   partition 2. This results in:
> 			-The installation of Solaris will occur on this
> 			 resized Solaris2 fdisk partition.
> 
> 			-Partition 1 will remain unchanged. Any data
> 			 that exists on this partition will remain 
> 			 accessible.
> 		
> 			-Partitions 3 and 4, if they exist, and if
> 			 they are of the allowed partition types
> 			 Solaris can create, will be
> 			 rewritten with a new start block and length. 
> 			 All existing data on the original partitions will
> 			 not be accessible due to the change of the fdisk
> 			 partition data for these.
> 
> 			-If Partitons 3 and 4 are fdisk types that Solaris
> 			 cannot currently create, we will delete the old
> 			 partitions to create the new partition 2, 
> 			 and the remaining space on the disk will be
> 			 left unallocated. The user can change this after
> 			 utilizing the partition tool of their choice.
> 
> 			-Default filesystem will be configured for the
> 			 Solaris installation.
> 
> 	3.1.3 Upgrade:
> 		1. Solaris Upgrade targets supported:
> 			a) Solaris root slice in a VTOC labeled fdisk partition 
> 			b) Attributes:
> 
> 				-Within slices discovered, partition tags 
> 				 labeled 'root' and 'unassigned' (the latter, 
> 				 for the cases of freshly installed 
> 				 Solaris' and LUs that have not yet been 
> 				 activated)
> 
> 				-root slice must mount successfully
> 
> 				-/var, if installed on a separate slice, 
> 				 as found in /etc/vfstab, must mount
> 				 successfully.
> 
> 				-/var/sadm/softinfo/INST_RELEASE file is
> 				 present and readable.
> 
> 				-/var/sadm/system/CLUSTER file is 
> 				 present and readable.
> 
> 				-/var/sadm/system/.clustertoc file is
> 			 	present and readable.
> 
> 				-/boot/solaris/bootenv.rc on X86 is
> 				present.
> 	
> 				-All non-global zones associated with 
> 				the root must be upgradable.
> 
> 				-/usr packages present
> 
> 				-Solaris version must be one of a previous
> 				 SXDE build.  It will also allow upgrade from 
> 				 Solaris Express Community Edition releases
> 				 that coincide with the SXDE releases.
> 				
> 
> 		2. Solaris upgrade targets not supported:
> 			a) Solaris instance whose root resides on SVM 
> 
> 			b) Solaris instance has non-global zones configured that
> 	  		   are on an SVM metadevice
> 
> 			c) Solaris instance has non-global zones with ZFS root
> 
> 	3.1.3.1 Solaris Upgrade Scenario examples
> 
> 		1. User chooses valid upgrade target. Size of root is
> 		   sufficient to handle the upgrade. This results in:
> 			-Upgrade is performed.
> 
> 			-All existing data is preserved.
> 
> 			-No fdisk partition data is modified.
> 
> 		2. User chooses invalid upgrade target. This results in:
> 			-Message displayed as to why the target is not
> 			 a valid upgrade target. A warning symbol will
> 			 have been displayed for this listed target
> 			 so that the user should be aware of its status.
> 
> 			-No changes occur.
> 
> 	3.1.4 The SunStudio and NetBeans tools:
> 
> 		1. Initial Install:
> 
> 			a) Installation behavior and scripts are provided by
> 			   the Developer tools team. 
> 
> 			b) During initial install Sun Studio 12 will be 
> 			   installed.
> 
> 			c) During intial install Sun Studio 12 will install
> 			   NetBeans 5.5.1 as it currently ships this
> 			   version.
> 
> 			d) NetBeans 5.5 will also be installed since
> 			   NetBeans users are supposed to use this version, 
> 			   and not 5.5.1.
> 
> 		2. Upgrade: 
> 			a) Upgrade behavior and scripts are provided by 
> 			   tools team.
> 
> 			b) If supported tools are currently installed on 
> 			   system, they will not be upgraded to Sun 
> 			   Studio 12. 
> 
> 			c) If tools not currently installed on system, Sun 
> 			   Studio 12 will be installed during upgrade.
> 
> 
> 4.0 Interfaces
> 
> 4.1 EXPORTED INTERFACES:
>                           Proposed            Specified       Former Stability
> Interface                 Stability           in what         Classification
> Name                      Classification      document?       or Other Comments
> ------------------------------------------------------------------------------
> Dwarf GUI		 Uncommitted		[1],[9]	
> 
> liborchestrator.so.1	 Project Private	[2]	
> 
> libtd.so.1		 Project Private	[3]	
> 
> soldevx			 Committed		PSARC/2006/687	Boot property
> 								set by GRUB
> 								menu
> 
> 
> 
> 4.2 IMPORTED INTERFACES:
>                           Proposed            Specified       Former Stability
> Interface                 Stability           in what         Classification
> Name                      Classification      document?       or Other Comments
> ------------------------------------------------------------------------------
> libdiskmgt.so.1					LSARC/2004/743  Consolidation
> 								Private**
> 					
> libnvpair.so.1					[4], [5], [6]   Committed
> 								(Evolving)
> 
> libsvm.so.1				 	[7], [8]	Consolidation
> 							        Private***
> 
> libdevinfo.so.1					PSARC/1997/127	Committed
> 								(Evolving)
> 
> Developer tools scripts				PSARC/2006/687  Committed
> 
> 
> 4.3 Interface Notes:
> 
> **Contract submitted to owning team, ZFS. Received approval from Dave Brittle,
>   RM for ZFS. Contract in case materials, PSARC/2007/284.
> 
> ***Contract already secured with SVM team. See [7] and [8] below. 
> 
> 5. Misc 
> 
> 	5.1 UIRB review
> 		We have currently filed a case as noted in [9] below
> 		for UIRB review. The expectation is that while this
> 		review is not required at this time for Dwarf Caiman,
> 		since the UI is specifically targeted at developers and
> 		not system administrators, we will be conducting UIRB
> 		reviews for every release of the new Installer.
> 
> 		It is expected that this initial UIRB review will be handled
> 		via email.
> 
> 	5.2 Memory Requirements
> 		The current memory requirements to boot and install
> 		Solaris Express Developer Edition 1 and 2 is 768MB. This
> 		is due to several factors:
> 			-The need for Java to be loaded in to ramdisk
> 			 the current Developer Express Java GUI.
> 			-The size of the miniroot due to additional
> 			 required packages.
> 
> 		For Dwarf Caiman we are actively trying to reduce the
> 		minimum size required for memory by the following:
> 			-Remove the need for Java: 
> 				-The Dwarf GUI is implemented
> 				 using Gnome and in C. 
> 
> 				-We will not require the existing Solaris 
> 				 Install 'launcher' code to install the 
> 				 Sun Studio tools. The 'launcher' is
> 				 implemented with Java.
> 	
> 				-Created a separate root archive for the
> 				 Dwarf Caiman bits to allow for trimming
> 				 of unnecessary packages for this installation
> 				 path.
> 		
> 		No testing has been done to validate that these steps will
> 		reduce the memory requirement.  The addition of
> 		new Gnome packages required for the Dwarf GUI along with
> 		the addition of any new miniroot packages in support
> 		of new features such as Xen may mean we don't see a 
> 		substantial reduction in the memory requirements.
> 
> 6. Documentation:
> 
> [1] Xdesign Dwarf Caiman GUI Mockup:
> http://xdesign.sfbay/projects/solaris/subprojects/install/design/dwarf/
> 
> [2] Dwarf Caiman Orchestrator design document:
> http://opensolaris.org/os/project/caiman/files/dwarf_caiman_design.pdf
> 
> [3] Dwarf Caiman Target Discovery design document:
> http://opensolaris.org/os/project/caiman/files/dwarf_td_design.pdf
> 
> [4] PSARC/2000/212 - libnvpair - A Name Value Pairs library
> 
> [5] PSARC/2003/121 - Extension to libnvpair
> 
> [6] PSARC/2003/252 - Another libnvpair extension
> 
> [7] PSARC/2000/049 - Solaris logical volume manager upgrade
> 
> [8] PSARC/2001/341 - SVM -Upgrade Contract Interfaces 
> 
> [9] UIRB/2007/264 - http://sac.sfbay.sun.com/Archives/CaseLog/rb/UIRB/2007/264/,
> 		    Dwarf Caiman UIRB Review Materials


From alan.coopersmith@sun.com Wed May 23 18:01:32 2007
Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l4O11WiH018140
	for <psarc-ext@sac.sfbay.sun.com>; Wed, 23 May 2007 18:01:32 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l4O1087U009330
	for <@newsunmail1brm.central.sun.com:psarc-ext@sun.com>; Wed, 23 May 2007 19:00:09 -0600 (MDT)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0JII00H3NTGIRM00@brm-avmta-1.central.sun.com> for psarc-ext@sun.com
 (ORCPT psarc-ext@sun.com); Wed, 23 May 2007 19:00:18 -0600 (MDT)
Received: from sfbaymail1sca.SFBay.Sun.COM ([129.145.154.35])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JII004IVTGHAW70@brm-avmta-1.central.sun.com> for
 psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed,
 23 May 2007 19:00:17 -0600 (MDT)
Received: from [129.146.108.211] (almas.SFBay.Sun.COM [129.146.108.211])
	by sfbaymail1sca.SFBay.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,v2.2)
 with ESMTP id l4O10G6h013059; Wed, 23 May 2007 18:00:16 -0700 (PDT)
Date: Wed, 23 May 2007 18:00:16 -0700
From: Alan Coopersmith <alan.coopersmith@sun.com>
Subject: Re: Fast track review - PSARC/2007/284 Dwarf Caiman,
 New Solaris Install GUI
In-reply-to: <4654D566.1090101@sun.com>
To: Sarah.Jelinek@sun.com
Cc: psarc-ext@sun.com
Message-id: <4654E3A0.6080200@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.2.0.264296
References: <4654D566.1090101@sun.com>
User-Agent: Thunderbird 2.0.0.0 (X11/20070423)
Status: RO
Content-Length: 284

Sarah Jelinek wrote:
> 				-Solaris fdisk partition will be resliced with 
> 				default filesystem layout. Default layout will
> 				be as follows: 
> 					TBD*

TBD?

-- 
	-Alan Coopersmith-           alan.coopersmith@sun.com
	 Sun Microsystems, Inc. - X Window System Engineering


From carlsonj@phorcys.east.sun.com Wed May 23 18:11:08 2007
Received: from sunmail4.Singapore.Sun.COM (sunmail4.Singapore.Sun.COM [129.158.71.19])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l4O1B7FK019149
	for <psarc-ext@sac.sfbay.Sun.COM>; Wed, 23 May 2007 18:11:08 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by sunmail4.Singapore.Sun.COM (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id l4O19j7V028264;
	Thu, 24 May 2007 09:09:50 +0800 (SGT)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0JII00405TWBLR00@nwk-avmta-1.sfbay.Sun.COM>; Wed,
 23 May 2007 18:09:47 -0700 (PDT)
Received: from phorcys.east.sun.com ([129.148.174.143])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JII00MUWTWA9O10@nwk-avmta-1.sfbay.Sun.COM>; Wed,
 23 May 2007 18:09:47 -0700 (PDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id l4O19k61005156; Wed,
 23 May 2007 21:09:46 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l4O19kpd005153; Wed,
 23 May 2007 21:09:46 -0400 (EDT)
Date: Wed, 23 May 2007 21:09:46 -0400
From: James Carlson <james.d.carlson@sun.com>
Subject: Re: Fast track review - PSARC/2007/284 Dwarf Caiman,
 New Solaris Install GUI
In-reply-to: <4654E3A0.6080200@sun.com>
To: Alan Coopersmith <Alan.Coopersmith@sun.com>
Cc: Sarah.Jelinek@sun.com, psarc-ext@sun.com
Message-id: <18004.58842.252088.97436@gargle.gargle.HOWL>
MIME-version: 1.0
X-Mailer: VM 7.01 under Emacs 21.3.1
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.2.0.264296
References: <4654D566.1090101@sun.com> <4654E3A0.6080200@sun.com>
Status: RO
Content-Length: 520

Alan Coopersmith writes:
> Sarah Jelinek wrote:
> > 				-Solaris fdisk partition will be resliced with 
> > 				default filesystem layout. Default layout will
> > 				be as follows: 
> > 					TBD*
> 
> TBD?

Indeed.  Was this intended as the materials for an inception review or
as a fast-track?

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

From Sarah.Jelinek@Sun.COM Thu May 24 06:35:41 2007
Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l4ODZfCh000293
	for <psarc-ext@sac.sfbay.sun.com>; Thu, 24 May 2007 06:35:41 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l4ODYQAe007578
	for <@newsunmail1brm.central.sun.com:psarc-ext@sun.com>; Thu, 24 May 2007 06:34:27 -0700 (PDT)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0JIJ00505SDDO600@brm-avmta-1.central.sun.com> for psarc-ext@sun.com
 (ORCPT psarc-ext@sun.com); Thu, 24 May 2007 07:34:25 -0600 (MDT)
Received: from brmea-mail-2.sun.com ([192.18.98.43])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JIJ001LUSDDMZ20@brm-avmta-1.central.sun.com> for
 psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Thu,
 24 May 2007 07:34:25 -0600 (MDT)
Received: from fe-amer-04.sun.com ([192.18.108.178])
	by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l4ODYONr029544	for
 <psarc-ext@sun.com>; Thu, 24 May 2007 13:34:24 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 id <0JIJ00H01RSB1800@mail-amer.sun.com>
 (original mail from Sarah.Jelinek@Sun.COM)
 for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Thu,
 24 May 2007 07:34:24 -0600 (MDT)
Received: from [192.9.61.46] by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 with ESMTPSA id <0JIJ00DJVSDBES63@mail-amer.sun.com> for psarc-ext@sun.com
 (ORCPT psarc-ext@sun.com); Thu, 24 May 2007 07:34:24 -0600 (MDT)
Date: Thu, 24 May 2007 07:34:23 -0600
From: Sarah Jelinek <Sarah.Jelinek@Sun.COM>
Subject: Re: Fast track review - PSARC/2007/284 Dwarf Caiman,
 New Solaris Install GUI
In-reply-to: <4654E3A0.6080200@sun.com>
Sender: Sarah.Jelinek@Sun.COM
To: Alan Coopersmith <Alan.Coopersmith@Sun.COM>
Cc: psarc-ext@Sun.COM
Reply-to: Sarah.Jelinek@Sun.COM
Message-id: <4655945F.9020305@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.2.0.264296
References: <4654D566.1090101@sun.com> <4654E3A0.6080200@sun.com>
User-Agent: Thunderbird 2.0b2 (X11/20070326)
Status: RO
Content-Length: 638



Alan Coopersmith wrote:
> Sarah Jelinek wrote:
>>                 -Solaris fdisk partition will be resliced with 
>>                 default filesystem layout. Default layout will
>>                 be as follows:                     TBD*
>
> TBD?
>
Yeah...sorry about that. I will update this today. We have been having 
ongoing discussions about this and I think we finally came to an 
agreement, in principle, on how we want to do this. I woke up at 3am and 
realized I left this in the fast track document and had forgotten to 
update this section before submitting.

I will update this doc today and resend it.

thanks,
sarah
****

From Sarah.Jelinek@sun.com Thu May 24 14:44:45 2007
Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l4OLijYw011735
	for <psarc-ext@sac.sfbay.sun.com>; Thu, 24 May 2007 14:44:45 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l4OLhSfA020689
	for <@newsunmail1brm.central.sun.com:psarc-ext@sun.com>; Thu, 24 May 2007 14:43:30 -0700 (PDT)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0JIK0070ZF0IW000@brm-avmta-1.central.sun.com> for psarc-ext@sun.com
 (ORCPT psarc-ext@sun.com); Thu, 24 May 2007 15:43:30 -0600 (MDT)
Received: from brmea-mail-1.sun.com ([192.18.98.31])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JIK003K2F0BQ420@brm-avmta-1.central.sun.com> for
 psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Thu,
 24 May 2007 15:43:23 -0600 (MDT)
Received: from fe-amer-05.sun.com ([192.18.108.179])
	by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l4OLhNMc014657	for
 <psarc-ext@sun.com>; Thu, 24 May 2007 21:43:23 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 id <0JIK00301EY95200@mail-amer.sun.com>
 (original mail from Sarah.Jelinek@Sun.COM)
 for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Thu,
 24 May 2007 15:43:23 -0600 (MDT)
Received: from [192.9.61.46] by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 with ESMTPSA id <0JIK003USF09LSS0@mail-amer.sun.com> for psarc-ext@sun.com
 (ORCPT psarc-ext@sun.com); Thu, 24 May 2007 15:43:22 -0600 (MDT)
Date: Thu, 24 May 2007 15:43:21 -0600
From: Sarah Jelinek <Sarah.Jelinek@sun.com>
Subject: Fast track review - PSARC/2007/284 Dwarf Caiman,
 New Solaris Install GUI - updated spec
Sender: Sarah.Jelinek@sun.com
To: psarc-ext@sun.com
Reply-to: Sarah.Jelinek@sun.com
Message-id: <465606F9.90604@sun.com>
MIME-version: 1.0
Content-type: multipart/mixed; boundary="Boundary_(ID_izPTmSzVz360gFgLA92rgg)"
X-PMX-Version: 5.2.0.264296
User-Agent: Thunderbird 2.0b2 (X11/20070326)
Status: RO
Content-Length: 13122

This is a multi-part message in MIME format.

--Boundary_(ID_izPTmSzVz360gFgLA92rgg)
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT

Hi All,

I have updated the fast track spec for the Dwarf Caiman project to 
include the default filesystem layout data. I have posted this in the 
case materials as well. This is the only change made to the original 
spec I sent yesterday.

thanks,
sarah


--Boundary_(ID_izPTmSzVz360gFgLA92rgg)
Content-type: text/plain; name=dwarf_caiman.txt.updated
Content-transfer-encoding: 7BIT
Content-disposition: inline; filename=dwarf_caiman.txt.updated

Name(s) of person (s) answer questions?

        Sarah Jelinek

Date:
	5/24/07, revised version of original fast track spec.

1. What specifically is the proposal that we are reviewing?

	Fast track request for PSARC/2007/284.

	The 1st project, in a series of planned projects, for the New	
	Solaris Installer(NSI) program, formerly known as Caiman. 

	This project, Dwarf Caiman, will deliver a subset
	of the overall NSI program plans as outlined in PSARC/2007/039, 
	suitable for the graphical installation path for the Solaris Express
	Developer Edition release. 

	This project is also related to the Solaris Express Developer Edition
	project that was presented in PSARC/2006/687. 


2. Project Summary:

	Dwarf Caiman is the first of many Solaris install projects aimed
	at fulfilling the strategy outlined in: 

http://www.opensolaris.org/os/community/install/files/install_strategy.pdf. 

	This project is not intended to replace the general Solaris installer 
	GUI, nor does it modify the existing character and command-line 
	interfaces.

	It provides a streamlined installation experience with a totally
	new look and feel for the graphical user interface. The focus
	is on branding and usability of the GUI. It also provides the 
	beginnings of the New Solaris Installer architecture.

	Specific details as to what features Dwarf Caiman will
	provide are listed below.

	We are requesting a minor release binding.

3.0 Technical details

3.1 Project Requirements

	3.1.1 General:
		1. x86 platform support only. Sparc bits will be built, but
		   there is no boot support for Developer Edition on sparc.

		2. DVD distribution only.

		3. Support for installation and upgrade from the SUNWCXall
		   metacluster only. No software selection offered.

		4. No additional product install offered.
		   
	3.1.2 Initial Install:
		1. Solaris Initial Installation targets supported:
			a) Whole disks only
			b) Behaviors:

				-Disk chosen by user will be, by default, 
				partitioned as 1 Solaris2 fdisk partition.

				-If user chooses the non-default option of 
				partitioning the disk chosen, the existing 
				Solaris2 partition, if it exists will be used 
				as the installation target by default.

				-The disk chosen can be repartitioned to 
				include only 1 Solaris2 fdisk partition.

				-All existing non-Solaris2 fdisk partitions 
				will be preserved if there is adequate 
			        space in the Solaris2 partition for 
				installation if the user makes no
				changes that would change the start block or
				length of the existing partitions.

			c) filesystem layout:

				1. Proposed layout:

				Solaris fdisk partition will be resliced with 
				default filesystem layout. Default layout will
				be as follows: 

				 - Disk size < 8 GB, Install will not be 
				   allowed.

				 - Disk size between 8 GB and 10 GB:
				   swap = 0.5 GB, /export/home is 0.5 GB and 
				   root = 7GB	

				- Disk size between  10 GB - 20 GB:
				  swap = 1 GB, 
				  root is 75 % of the disk with minimum 8 GB 
				  and maximum 15 GB, rest is /export/home

				- Disk size between 20 GB - 30 GB:
				  swap = 2GB, 
				  root =30% &&
				  second_root=30% (with minimum of 8 GB) 
				  rest is /export/home

				- Disk sizes greater than 30 GB:
				  swap = 2 GB, 
				  root = 30%  &&
				  second_root=30% (with minimum of 8 GB and 
				  maximum of 15 GB) 
				  rest is /export/home

			2. Examples:

			a) 10 GB disk/partition will have 1 GB swap, 
			1 GB /export/home and 8 GB root (/).

			b) 15 GB disk/partition will have 1 GB swap, 
			2.8 GB /export/home and 11.2 GB root (/).


			c) 20 GB disk/partition will have 1 GB swap, 
			4 GB /export/home,  15 GB for root

			d) 25 GB disk/partition will have 2 GB swap, 
			6 GB /export/home, 8.5 GB each for root and second_root

			e) 30 GB disk/partition will have 2 GB swap, 
			8 GB /export/home, 10 GB each for root and second_root 	


			d) Existing User Data:
				-There will be no option for the user to select 
				 slices to preserve with initial installation.

		2. Other user selections offered with initial install:
			a) See GUI mockup as noted in [1].

	3.1.2.1 Initial install scenario examples
		1. The user allows default selections for all of the
		   installation process. This results in:
			-The disk target chosen being partitioned as 1 Solaris2
			 fdisk partition.

			-Default filesystems configured for the Solaris
			 installation.
		
			-All existing data on disk chosen is overwritten.

		2. The user selects to utilize the existing fdisk partitions
		   on the selected disk target. This results in:
			-The installation of Solaris will occur on the
			 existing Solaris2 fdisk partition. Any 
			 previous data on this partition will be 
			 overwritten.
		
			-All other partition data will be untouched.
	
			-Default filesystems will be configured for 
			 the Solaris installation.

		3. The user selects to customize the fdisk partition
		   layout on the selected disk target by enlarging
		   the existing Solaris2 fdisk partition, which is
		   partition 2. This results in:
			-The installation of Solaris will occur on this
			 resized Solaris2 fdisk partition.

			-Partition 1 will remain unchanged. Any data
			 that exists on this partition will remain 
			 accessible.
		
			-Partitions 3 and 4, if they exist, and if
			 they are of the allowed partition types
			 Solaris can create, will be
			 rewritten with a new start block and length. 
			 All existing data on the original partitions will
			 not be accessible due to the change of the fdisk
			 partition data for these.

			-If Partitons 3 and 4 are fdisk types that Solaris
			 cannot currently create, we will delete the old
			 partitions to create the new partition 2, 
			 and the remaining space on the disk will be
			 left unallocated. The user can change this after
			 utilizing the partition tool of their choice.

			-Default filesystem will be configured for the
			 Solaris installation.

	3.1.3 Upgrade:
		1. Solaris Upgrade targets supported:
			a) Solaris root slice in a VTOC labeled fdisk partition 
			b) Attributes:

				-Within slices discovered, partition tags 
				 labeled 'root' and 'unassigned' (the latter, 
				 for the cases of freshly installed 
				 Solaris' and LUs that have not yet been 
				 activated)

				-root slice must mount successfully

				-/var, if installed on a separate slice, 
				 as found in /etc/vfstab, must mount
				 successfully.

				-/var/sadm/softinfo/INST_RELEASE file is
				 present and readable.

				-/var/sadm/system/CLUSTER file is 
				 present and readable.

				-/var/sadm/system/.clustertoc file is
			 	present and readable.

				-/boot/solaris/bootenv.rc on X86 is
				present.
	
				-All non-global zones associated with 
				the root must be upgradable.

				-/usr packages present

				-Solaris version must be one of a previous
				 SXDE build.  It will also allow upgrade from 
				 Solaris Express Community Edition releases
				 that coincide with the SXDE releases.
				

		2. Solaris upgrade targets not supported:
			a) Solaris instance whose root resides on SVM 

			b) Solaris instance has non-global zones configured that
	  		   are on an SVM metadevice

			c) Solaris instance has non-global zones with ZFS root

	3.1.3.1 Solaris Upgrade Scenario examples

		1. User chooses valid upgrade target. Size of root is
		   sufficient to handle the upgrade. This results in:
			-Upgrade is performed.

			-All existing data is preserved.

			-No fdisk partition data is modified.

		2. User chooses invalid upgrade target. This results in:
			-Message displayed as to why the target is not
			 a valid upgrade target. A warning symbol will
			 have been displayed for this listed target
			 so that the user should be aware of its status.

			-No changes occur.

	3.1.4 The SunStudio and NetBeans tools:

		1. Initial Install:

			a) Installation behavior and scripts are provided by
			   the Developer tools team. 

			b) During initial install Sun Studio 12 will be 
			   installed.

			c) During intial install Sun Studio 12 will install
			   NetBeans 5.5.1 as it currently ships this
			   version.

			d) NetBeans 5.5 will also be installed since
			   NetBeans users are supposed to use this version, 
			   and not 5.5.1.

		2. Upgrade: 
			a) Upgrade behavior and scripts are provided by 
			   tools team.

			b) If supported tools are currently installed on 
			   system, they will not be upgraded to Sun 
			   Studio 12. 

			c) If tools not currently installed on system, Sun 
			   Studio 12 will be installed during upgrade.


4.0 Interfaces

4.1 EXPORTED INTERFACES:
                          Proposed            Specified       Former Stability
Interface                 Stability           in what         Classification
Name                      Classification      document?       or Other Comments
------------------------------------------------------------------------------
Dwarf GUI		 Uncommitted		[1],[9]	

liborchestrator.so.1	 Project Private	[2]	

libtd.so.1		 Project Private	[3]	

soldevx			 Committed		PSARC/2006/687	Boot property
								set by GRUB
								menu



4.2 IMPORTED INTERFACES:
                          Proposed            Specified       Former Stability
Interface                 Stability           in what         Classification
Name                      Classification      document?       or Other Comments
------------------------------------------------------------------------------
libdiskmgt.so.1					LSARC/2004/743  Consolidation
								Private**
					
libnvpair.so.1					[4], [5], [6]   Committed
								(Evolving)

libsvm.so.1				 	[7], [8]	Consolidation
							        Private***

libdevinfo.so.1					PSARC/1997/127	Committed
								(Evolving)

Developer tools scripts				PSARC/2006/687  Committed


4.3 Interface Notes:

**Contract submitted to owning team, ZFS. Received approval from Dave Brittle,
  RM for ZFS. Contract in case materials, PSARC/2007/284.

***Contract already secured with SVM team. See [7] and [8] below. 

5. Misc 

	5.1 UIRB review
		We have currently filed a case as noted in [9] below
		for UIRB review. The expectation is that while this
		review is not required at this time for Dwarf Caiman,
		since the UI is specifically targeted at developers and
		not system administrators, we will be conducting UIRB
		reviews for every release of the new Installer.

		It is expected that this initial UIRB review will be handled
		via email.

	5.2 Memory Requirements
		The current memory requirements to boot and install
		Solaris Express Developer Edition 1 and 2 is 768MB. This
		is due to several factors:
			-The need for Java to be loaded in to ramdisk
			 the current Developer Express Java GUI.
			-The size of the miniroot due to additional
			 required packages.

		For Dwarf Caiman we are actively trying to reduce the
		minimum size required for memory by the following:
			-Remove the need for Java: 
				-The Dwarf GUI is implemented
				 using Gnome and in C. 

				-We will not require the existing Solaris 
				 Install 'launcher' code to install the 
				 Sun Studio tools. The 'launcher' is
				 implemented with Java.
	
				-Created a separate root archive for the
				 Dwarf Caiman bits to allow for trimming
				 of unnecessary packages for this installation
				 path.
		
		No testing has been done to validate that these steps will
		reduce the memory requirement.  The addition of
		new Gnome packages required for the Dwarf GUI along with
		the addition of any new miniroot packages in support
		of new features such as Xen may mean we don't see a 
		substantial reduction in the memory requirements.

6. Documentation:

[1] Xdesign Dwarf Caiman GUI Mockup:
http://xdesign.sfbay/projects/solaris/subprojects/install/design/dwarf/

[2] Dwarf Caiman Orchestrator design document:
http://opensolaris.org/os/project/caiman/files/dwarf_caiman_design.pdf

[3] Dwarf Caiman Target Discovery design document:
http://opensolaris.org/os/project/caiman/files/dwarf_td_design.pdf

[4] PSARC/2000/212 - libnvpair - A Name Value Pairs library

[5] PSARC/2003/121 - Extension to libnvpair

[6] PSARC/2003/252 - Another libnvpair extension

[7] PSARC/2000/049 - Solaris logical volume manager upgrade

[8] PSARC/2001/341 - SVM -Upgrade Contract Interfaces 

[9] UIRB/2007/264 - http://sac.sfbay.sun.com/Archives/CaseLog/rb/UIRB/2007/264/,
		    Dwarf Caiman UIRB Review Materials


--Boundary_(ID_izPTmSzVz360gFgLA92rgg)--

From Sarah.Jelinek@sun.com Thu May 24 14:59:08 2007
Received: from sunmail4.Singapore.Sun.COM (sunmail4.Singapore.Sun.COM [129.158.71.19])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l4OLx7cM012407
	for <psarc-ext@sac.sfbay.Sun.COM>; Thu, 24 May 2007 14:59:08 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail4.Singapore.Sun.COM (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id l4OLvbwX011828
	for <@sunmail3mpk.sfbay.sun.com:psarc-ext@sun.com>; Fri, 25 May 2007 05:57:52 +0800 (SGT)
Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by
 nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0JIK00903FOFTZ00@nwk-avmta-2.sfbay.sun.com> for psarc-ext@sun.com
 (ORCPT psarc-ext@sun.com); Thu, 24 May 2007 14:57:51 -0700 (PDT)
Received: from brmea-mail-3.sun.com ([192.18.98.34])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JIK002OTFOFPJA0@nwk-avmta-2.sfbay.sun.com> for
 psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Thu,
 24 May 2007 14:57:51 -0700 (PDT)
Received: from fe-amer-03.sun.com ([192.18.108.177])
	by brmea-mail-3.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l4OLvp34009757	for
 <psarc-ext@sun.com>; Thu, 24 May 2007 21:57:51 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 id <0JIK00901FLWAZ00@mail-amer.sun.com>
 (original mail from Sarah.Jelinek@Sun.COM)
 for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Thu,
 24 May 2007 15:57:51 -0600 (MDT)
Received: from [192.9.61.46] by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 with ESMTPSA id <0JIK003HTFOCNCD0@mail-amer.sun.com> for psarc-ext@sun.com
 (ORCPT psarc-ext@sun.com); Thu, 24 May 2007 15:57:50 -0600 (MDT)
Date: Thu, 24 May 2007 15:57:48 -0600
From: Sarah Jelinek <Sarah.Jelinek@sun.com>
Subject: Re: Fast track review - PSARC/2007/284 Dwarf Caiman,
 New Solaris Install GUI
In-reply-to: <4654DEB0.1050301@sun.com>
Sender: Sarah.Jelinek@sun.com
To: Mike Riley <Michael.Riley@sun.com>
Cc: psarc-ext@sun.com
Reply-to: Sarah.Jelinek@sun.com
Message-id: <46560A5C.5000709@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.2.0.264296
References: <4654D566.1090101@sun.com> <4654DEB0.1050301@sun.com>
User-Agent: Thunderbird 2.0b2 (X11/20070326)
Status: RO
Content-Length: 17480

Hi Mike,

Mike Riley wrote:
> Hi Sarah,
>
> I had a couple of questions after reading this.
>
> 1) Is only Solaris2 fdisk partitions supported by this?  According to 
> the dwarf_td_design.pdf document it sounds like it is supposed to also 
> support the older Solaris partition type by validating the contents to 
> verify it is not a Linux swap partition.  You seem to outline those 
> steps under item 1 of section 3.1.3 for Upgrades, but every time and 
> fdisk partition is mentioned you say it must be a Solaris2 type.
>
Only Solaris2 partitions are supported for initial installation of 
Solaris. The support of Linux swap is intended for us to not overwrite 
linux swap, which is the same number as the old Solaris partition, with 
Solaris if it really is linux swap. The outcome will be a Solaris2 
partition during initial install.

For upgrades we will upgrade the existing instance of Solaris, which we 
find via a different algorithm than the fdisk partition type. Please 
note that we are only allowing upgrade from a previous Solaris Express 
Developer Edition release, basically our current development release of 
Nevada starting with build 58, so there should be no old Solaris type 
partitions we have to deal with for upgrade.

> 2) I applaud that it has the capability to resize a Solaris fdisk 
> partition as described in 3.1.2.1, item #3.  But why is this 
> capability not provided as part of the Upgrade as well?  That is 
> usually the case where you might need to expand an existing Solaris 
> partition, as opposed to the Initial install where you are offering 
> that ability.
>
Because expansion of a partition can result in a loss of data in 
subsequent partitions. With upgrade we are not suppose to destroy any 
existing data on the users machine, and to allow a resize would require 
us to move existing data to avoid this. We have opted not to provide 
this type of capability for Dwarf, as it is fairly involved for us to do 
this. For initial installs, if the user does enlarge an existing 
partition we warn them data will be lost in subsequent partitions. I 
agree in principle that a user would likely be wanting to increase 
partition size along with potentially slice size with an upgrade, we 
just are not offering that capability with Dwarf.

We are hoping that the defaults we chose for the filesystem layout, as I 
noted in the updated spec, will negate the need for a user to expand the 
root slice to upgrade. And, with the next project we will deliver we 
will be moving to ZFS as root, which means a whole different layout 
mechanism.

sarah


> Mike
>
> Sarah Jelinek wrote:
>> Hi All,
>>
>> I am sponsoring the following fast track for myself. It times out on 
>> 5/30/2007. It is related to the umbrella case, PSARC/2007/039, 
>> Caiman: New Solaris Install Experience, which is scheduled for 
>> inception review next Wed, 5/30/2007.
>>
>> This fast track represents the first installment of projects that 
>> will comprise the full Caiman experience.
>>
>> The attached spec, and  other materials as noted are posted in the 
>> case directory as well.
>>
>> Regards,
>> Sarah Jelinek
>>
>>
>> ------------------------------------------------------------------------
>>
>> Name(s) of person (s) answer questions?
>>
>>         Sarah Jelinek
>>
>> 1. What specifically is the proposal that we are reviewing?
>>
>>     Fast track request for PSARC/2007/284.
>>
>>     The 1st project, in a series of planned projects, for the New   
>>     Solaris Installer(NSI) program, formerly known as Caiman.
>>     This project, Dwarf Caiman, will deliver a subset
>>     of the overall NSI program plans as outlined in PSARC/2007/039, 
>>     suitable for the graphical installation path for the Solaris Express
>>     Developer Edition release.
>>     This project is also related to the Solaris Express Developer 
>> Edition
>>     project that was presented in PSARC/2006/687.
>>
>> 2. Project Summary:
>>
>>     Dwarf Caiman is the first of many Solaris install projects aimed
>>     at fulfilling the strategy outlined in:
>> http://www.opensolaris.org/os/community/install/files/install_strategy.pdf. 
>>
>>     This project is not intended to replace the general Solaris 
>> installer     GUI, nor does it modify the existing character and 
>> command-line     interfaces.
>>
>>     It provides a streamlined installation experience with a totally
>>     new look and feel for the graphical user interface. The focus
>>     is on branding and usability of the GUI. It also provides the 
>>     beginnings of the New Solaris Installer architecture.
>>
>>     Specific details as to what features Dwarf Caiman will
>>     provide are listed below.
>>
>>     We are requesting a minor release binding.
>>
>> 3.0 Technical details
>>
>> 3.1 Project Requirements
>>
>>     3.1.1 General:
>>         1. x86 platform support only. Sparc bits will be built, but
>>            there is no boot support for Developer Edition on sparc.
>>
>>         2. DVD distribution only.
>>
>>         3. Support for installation and upgrade from the SUNWCXall
>>            metacluster only. No software selection offered.
>>
>>         4. No additional product install offered.
>>                3.1.2 Initial Install:
>>         1. Solaris Initial Installation targets supported:
>>             a) Whole disks only
>>             b) Behaviors:
>>
>>                 -Disk chosen by user will be, by default, 
>>                 partitioned as 1 Solaris2 fdisk partition.
>>
>>                 -If user chooses the non-default option of 
>>                 partitioning the disk chosen, the existing 
>>                 Solaris2 partition, if it exists will be used 
>>                 as the installation target by default.
>>
>>                 -The disk chosen can be repartitioned to 
>>                 include only 1 Solaris2 fdisk partition.
>>
>>                 -All existing non-Solaris2 fdisk partitions 
>>                 will be preserved if there is adequate 
>>                     space in the Solaris2 partition for 
>>                 installation if the user makes no
>>                 changes that would change the start block or
>>                 length of the existing partitions.
>>
>>             c) filesystem layout:
>>
>>                 -Solaris fdisk partition will be resliced with 
>>                 default filesystem layout. Default layout will
>>                 be as follows:                     TBD*
>>
>>
>>             d) Existing User Data:
>>                 -There will be no option for the user to select 
>>                  slices to preserve with initial installation.
>>
>>         2. Other user selections offered with initial install:
>>             a) See GUI mockup as noted in [1].
>>
>>     3.1.2.1 Initial install scenario examples
>>         1. The user allows default selections for all of the
>>            installation process. This results in:
>>             -The disk target chosen being partitioned as 1 Solaris2
>>              fdisk partition.
>>
>>             -Default filesystems configured for the Solaris
>>              installation.
>>        
>>             -All existing data on disk chosen is overwritten.
>>
>>         2. The user selects to utilize the existing fdisk partitions
>>            on the selected disk target. This results in:
>>             -The installation of Solaris will occur on the
>>              existing Solaris2 fdisk partition. Any              
>> previous data on this partition will be              overwritten.
>>        
>>             -All other partition data will be untouched.
>>     
>>             -Default filesystems will be configured for              
>> the Solaris installation.
>>
>>         3. The user selects to customize the fdisk partition
>>            layout on the selected disk target by enlarging
>>            the existing Solaris2 fdisk partition, which is
>>            partition 2. This results in:
>>             -The installation of Solaris will occur on this
>>              resized Solaris2 fdisk partition.
>>
>>             -Partition 1 will remain unchanged. Any data
>>              that exists on this partition will remain              
>> accessible.
>>        
>>             -Partitions 3 and 4, if they exist, and if
>>              they are of the allowed partition types
>>              Solaris can create, will be
>>              rewritten with a new start block and length. 
>>              All existing data on the original partitions will
>>              not be accessible due to the change of the fdisk
>>              partition data for these.
>>
>>             -If Partitons 3 and 4 are fdisk types that Solaris
>>              cannot currently create, we will delete the old
>>              partitions to create the new partition 2,              
>> and the remaining space on the disk will be
>>              left unallocated. The user can change this after
>>              utilizing the partition tool of their choice.
>>
>>             -Default filesystem will be configured for the
>>              Solaris installation.
>>
>>     3.1.3 Upgrade:
>>         1. Solaris Upgrade targets supported:
>>             a) Solaris root slice in a VTOC labeled fdisk partition 
>>             b) Attributes:
>>
>>                 -Within slices discovered, partition tags 
>>                  labeled 'root' and 'unassigned' (the latter, 
>>                  for the cases of freshly installed                  
>> Solaris' and LUs that have not yet been                  activated)
>>
>>                 -root slice must mount successfully
>>
>>                 -/var, if installed on a separate slice, 
>>                  as found in /etc/vfstab, must mount
>>                  successfully.
>>
>>                 -/var/sadm/softinfo/INST_RELEASE file is
>>                  present and readable.
>>
>>                 -/var/sadm/system/CLUSTER file is                  
>> present and readable.
>>
>>                 -/var/sadm/system/.clustertoc file is
>>                  present and readable.
>>
>>                 -/boot/solaris/bootenv.rc on X86 is
>>                 present.
>>     
>>                 -All non-global zones associated with                 
>> the root must be upgradable.
>>
>>                 -/usr packages present
>>
>>                 -Solaris version must be one of a previous
>>                  SXDE build.  It will also allow upgrade from 
>>                  Solaris Express Community Edition releases
>>                  that coincide with the SXDE releases.
>>                
>>
>>         2. Solaris upgrade targets not supported:
>>             a) Solaris instance whose root resides on SVM
>>             b) Solaris instance has non-global zones configured that
>>                  are on an SVM metadevice
>>
>>             c) Solaris instance has non-global zones with ZFS root
>>
>>     3.1.3.1 Solaris Upgrade Scenario examples
>>
>>         1. User chooses valid upgrade target. Size of root is
>>            sufficient to handle the upgrade. This results in:
>>             -Upgrade is performed.
>>
>>             -All existing data is preserved.
>>
>>             -No fdisk partition data is modified.
>>
>>         2. User chooses invalid upgrade target. This results in:
>>             -Message displayed as to why the target is not
>>              a valid upgrade target. A warning symbol will
>>              have been displayed for this listed target
>>              so that the user should be aware of its status.
>>
>>             -No changes occur.
>>
>>     3.1.4 The SunStudio and NetBeans tools:
>>
>>         1. Initial Install:
>>
>>             a) Installation behavior and scripts are provided by
>>                the Developer tools team.
>>             b) During initial install Sun Studio 12 will be 
>>                installed.
>>
>>             c) During intial install Sun Studio 12 will install
>>                NetBeans 5.5.1 as it currently ships this
>>                version.
>>
>>             d) NetBeans 5.5 will also be installed since
>>                NetBeans users are supposed to use this version, 
>>                and not 5.5.1.
>>
>>         2. Upgrade:             a) Upgrade behavior and scripts are 
>> provided by                tools team.
>>
>>             b) If supported tools are currently installed on 
>>                system, they will not be upgraded to Sun 
>>                Studio 12.
>>             c) If tools not currently installed on system, Sun 
>>                Studio 12 will be installed during upgrade.
>>
>>
>> 4.0 Interfaces
>>
>> 4.1 EXPORTED INTERFACES:
>>                           Proposed            Specified       Former 
>> Stability
>> Interface                 Stability           in what         
>> Classification
>> Name                      Classification      document?       or 
>> Other Comments
>> ------------------------------------------------------------------------------ 
>>
>> Dwarf GUI         Uncommitted        [1],[9]   
>>
>> liborchestrator.so.1     Project Private    [2]   
>>
>> libtd.so.1         Project Private    [3]   
>>
>> soldevx             Committed        PSARC/2006/687    Boot property
>>                                 set by GRUB
>>                                 menu
>>
>>
>>
>> 4.2 IMPORTED INTERFACES:
>>                           Proposed            Specified       Former 
>> Stability
>> Interface                 Stability           in what         
>> Classification
>> Name                      Classification      document?       or 
>> Other Comments
>> ------------------------------------------------------------------------------ 
>>
>> libdiskmgt.so.1                    LSARC/2004/743  Consolidation
>>                                 Private**
>>                    
>> libnvpair.so.1                    [4], [5], [6]   Committed
>>                                 (Evolving)
>>
>> libsvm.so.1                     [7], [8]    Consolidation
>>                                     Private***
>>
>> libdevinfo.so.1                    PSARC/1997/127    Committed
>>                                 (Evolving)
>>
>> Developer tools scripts                PSARC/2006/687  Committed
>>
>>
>> 4.3 Interface Notes:
>>
>> **Contract submitted to owning team, ZFS. Received approval from Dave 
>> Brittle,
>>   RM for ZFS. Contract in case materials, PSARC/2007/284.
>>
>> ***Contract already secured with SVM team. See [7] and [8] below.
>> 5. Misc
>>     5.1 UIRB review
>>         We have currently filed a case as noted in [9] below
>>         for UIRB review. The expectation is that while this
>>         review is not required at this time for Dwarf Caiman,
>>         since the UI is specifically targeted at developers and
>>         not system administrators, we will be conducting UIRB
>>         reviews for every release of the new Installer.
>>
>>         It is expected that this initial UIRB review will be handled
>>         via email.
>>
>>     5.2 Memory Requirements
>>         The current memory requirements to boot and install
>>         Solaris Express Developer Edition 1 and 2 is 768MB. This
>>         is due to several factors:
>>             -The need for Java to be loaded in to ramdisk
>>              the current Developer Express Java GUI.
>>             -The size of the miniroot due to additional
>>              required packages.
>>
>>         For Dwarf Caiman we are actively trying to reduce the
>>         minimum size required for memory by the following:
>>             -Remove the need for Java:                 -The Dwarf GUI 
>> is implemented
>>                  using Gnome and in C.
>>                 -We will not require the existing Solaris 
>>                  Install 'launcher' code to install the 
>>                  Sun Studio tools. The 'launcher' is
>>                  implemented with Java.
>>     
>>                 -Created a separate root archive for the
>>                  Dwarf Caiman bits to allow for trimming
>>                  of unnecessary packages for this installation
>>                  path.
>>        
>>         No testing has been done to validate that these steps will
>>         reduce the memory requirement.  The addition of
>>         new Gnome packages required for the Dwarf GUI along with
>>         the addition of any new miniroot packages in support
>>         of new features such as Xen may mean we don't see a         
>> substantial reduction in the memory requirements.
>>
>> 6. Documentation:
>>
>> [1] Xdesign Dwarf Caiman GUI Mockup:
>> http://xdesign.sfbay/projects/solaris/subprojects/install/design/dwarf/
>>
>> [2] Dwarf Caiman Orchestrator design document:
>> http://opensolaris.org/os/project/caiman/files/dwarf_caiman_design.pdf
>>
>> [3] Dwarf Caiman Target Discovery design document:
>> http://opensolaris.org/os/project/caiman/files/dwarf_td_design.pdf
>>
>> [4] PSARC/2000/212 - libnvpair - A Name Value Pairs library
>>
>> [5] PSARC/2003/121 - Extension to libnvpair
>>
>> [6] PSARC/2003/252 - Another libnvpair extension
>>
>> [7] PSARC/2000/049 - Solaris logical volume manager upgrade
>>
>> [8] PSARC/2001/341 - SVM -Upgrade Contract Interfaces
>> [9] UIRB/2007/264 - 
>> http://sac.sfbay.sun.com/Archives/CaseLog/rb/UIRB/2007/264/,
>>             Dwarf Caiman UIRB Review Materials
>
> _______________________________________________
> opensolaris-arc mailing list
> opensolaris-arc@opensolaris.org

From michael.riley@sun.com Fri May 25 10:56:06 2007
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l4PHu6bN003468
	for <psarc-ext@sac.sfbay.sun.com>; Fri, 25 May 2007 10:56:06 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by sunmail5.uk.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l4PHsjOu022854;
	Fri, 25 May 2007 18:54:48 +0100 (BST)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0JIL00E1BZ3BWT00@nwk-avmta-1.sfbay.Sun.COM>; Fri,
 25 May 2007 10:54:47 -0700 (PDT)
Received: from brmea-mail-1.sun.com ([192.18.98.31])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JIL00ECNZ3AG0E0@nwk-avmta-1.sfbay.Sun.COM>; Fri,
 25 May 2007 10:54:46 -0700 (PDT)
Received: from relay1.sun.com (relay1.sun.com [150.143.103.14] (may be forged))
	by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l4PHjanm028416; Fri,
 25 May 2007 17:54:45 +0000 (GMT)
Received: from mms03es.sun.com ([150.143.104.54] [150.143.104.54])
 by relay1.sun.com with ESMTP id BT-MMP-1814559; Fri,
 25 May 2007 17:54:45 +0000 (Z)
Received: from relay01i.sun.com
 (ip70.net150143-60.block3.us.syntegra.com [150.143.60.70])
 by mms03es.sun.com with ESMTP id BT-MMP-384174; Fri,
 25 May 2007 17:54:45 +0000 (Z)
Received: from fed1rmmtao107.cox.net ([68.230.241.39] [68.230.241.39])
 by relay0i.sun.com with ESMTP id BT-MMP-1206935; Fri,
 25 May 2007 17:54:45 +0000 (Z)
Received: from fed1rmimpo02.cox.net ([70.169.32.72])
 by fed1rmmtao107.cox.net (InterMail vM.7.05.02.00 201-2174-114-20060621)
 with ESMTP id
 <20070525174444.DNRD12190.fed1rmmtao107.cox.net@fed1rmimpo02.cox.net>; Fri,
 25 May 2007 13:44:44 -0400
Received: from [127.0.0.1] ([68.108.178.101])	by fed1rmimpo02.cox.net with
 bizsmtp	id 3Vkj1X00j2Bf2CL0000000; Fri, 25 May 2007 13:44:44 -0400
Date: Fri, 25 May 2007 10:42:47 -0700
From: Mike Riley <michael.riley@sun.com>
Subject: Re: Fast track review - PSARC/2007/284 Dwarf Caiman,
 New Solaris Install GUI
In-reply-to: <46560A5C.5000709@sun.com>
To: Sarah.Jelinek@sun.com
Cc: psarc-ext@sun.com
Message-id: <46572017.9020207@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.2.0.264296
References: <4654D566.1090101@sun.com> <4654DEB0.1050301@sun.com>
 <46560A5C.5000709@sun.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
Status: RO
Content-Length: 3350

Sarah Jelinek wrote:
> Hi Mike,
> 
> Mike Riley wrote:
>> Hi Sarah,
>>
>> I had a couple of questions after reading this.
>>
>> 1) Is only Solaris2 fdisk partitions supported by this?  According to 
>> the dwarf_td_design.pdf document it sounds like it is supposed to also 
>> support the older Solaris partition type by validating the contents to 
>> verify it is not a Linux swap partition.  You seem to outline those 
>> steps under item 1 of section 3.1.3 for Upgrades, but every time and 
>> fdisk partition is mentioned you say it must be a Solaris2 type.
>>
> Only Solaris2 partitions are supported for initial installation of 
> Solaris. The support of Linux swap is intended for us to not overwrite 
> linux swap, which is the same number as the old Solaris partition, with 
> Solaris if it really is linux swap. The outcome will be a Solaris2 
> partition during initial install.
> 
> For upgrades we will upgrade the existing instance of Solaris, which we 
> find via a different algorithm than the fdisk partition type. Please 
> note that we are only allowing upgrade from a previous Solaris Express 
> Developer Edition release, basically our current development release of 
> Nevada starting with build 58, so there should be no old Solaris type 
> partitions we have to deal with for upgrade.

I was not aware that Solaris Express could not be installed in an old 
Solaris partition.  I know that Solaris 10 can use one when upgrading from 
an older release of Solaris, and you can go into fdisk to change the type.

>> 2) I applaud that it has the capability to resize a Solaris fdisk 
>> partition as described in 3.1.2.1, item #3.  But why is this 
>> capability not provided as part of the Upgrade as well?  That is 
>> usually the case where you might need to expand an existing Solaris 
>> partition, as opposed to the Initial install where you are offering 
>> that ability.
>>
> Because expansion of a partition can result in a loss of data in 
> subsequent partitions. With upgrade we are not suppose to destroy any 
> existing data on the users machine, and to allow a resize would require 
> us to move existing data to avoid this. We have opted not to provide 
> this type of capability for Dwarf, as it is fairly involved for us to do 
> this. For initial installs, if the user does enlarge an existing 
> partition we warn them data will be lost in subsequent partitions. I 
> agree in principle that a user would likely be wanting to increase 
> partition size along with potentially slice size with an upgrade, we 
> just are not offering that capability with Dwarf.

I can understand that, but I would prefer we at least give the user a chance 
to allow the expansion if they wish to do so.  Also, if there is no other 
partition data after the existing Solaris partition, you would not be 
destroying any data by expanding the Solaris partition.

> We are hoping that the defaults we chose for the filesystem layout, as I 
> noted in the updated spec, will negate the need for a user to expand the 
> root slice to upgrade. And, with the next project we will deliver we 
> will be moving to ZFS as root, which means a whole different layout 
> mechanism.

Your defaults seem sensible for this version.  I typically modify them 
anyhow, as do most experienced users, but these seem fine for new Solaris users.

Mike


From gww@eng.sun.com Tue May 29 08:28:22 2007
Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l4TFSMNt000758
	for <psarc-ext@sac.sfbay.sun.com>; Tue, 29 May 2007 08:28:22 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l4TFR3Rq027373
	for <@sunmail3mpk.sfbay.sun.com:psarc-ext@sun.com>; Tue, 29 May 2007 08:27:04 -0700 (PDT)
Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by
 nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0JIT0021N6X3VI00@nwk-avmta-2.sfbay.sun.com> for psarc-ext@sun.com
 (ORCPT psarc-ext@sun.com); Tue, 29 May 2007 08:27:03 -0700 (PDT)
Received: from engmail3mpk.sfbay.Sun.COM ([129.146.11.26])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JIT00FBF6X02UF0@nwk-avmta-2.sfbay.sun.com> for
 psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue,
 29 May 2007 08:27:00 -0700 (PDT)
Received: from marduk.eng.sun.com (marduk.SFBay.Sun.COM [129.146.108.224])
	by engmail3mpk.sfbay.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,v2.2)
 with ESMTP id l4TFQxP9017969; Tue, 29 May 2007 08:26:59 -0700 (PDT)
Received: from marduk.eng.sun.com (localhost [127.0.0.1])
	by marduk.eng.sun.com (8.13.6+Sun/8.12.11) with ESMTP id l4TFTC9O023013; Tue,
 29 May 2007 08:29:12 -0700 (PDT)
Received: (from gww@localhost)
	by marduk.eng.sun.com (8.13.6+Sun/8.12.11/Submit) id l4TFTCV0023012; Tue,
 29 May 2007 08:29:12 -0700 (PDT)
Date: Tue, 29 May 2007 08:29:12 -0700 (PDT)
From: Gary Winiger <gww@eng.sun.com>
Subject: Re: Fast track review - PSARC/2007/284 Dwarf Caiman,
 New Solaris Install GUI - updated spec
To: Sarah.Jelinek@sun.com, psarc-ext@sun.com
Message-id: <200705291529.l4TFTCV0023012@marduk.eng.sun.com>
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.2.0.264296
Status: RO
Content-Length: 361

> 3.1 Project Requirements
> 
> 	3.1.1 General:
> 		1. x86 platform support only. Sparc bits will be built, but
> 		   there is no boot support for Developer Edition on sparc.

	I understand the emphasis here and have no issue with it.
	I'd also like to understand why SPARC isn't architecturally
	supportable.  And if the intent is for future support.

Gary..

From Sarah.Jelinek@sun.com Tue May 29 08:43:34 2007
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l4TFhX5Y001896
	for <psarc-ext@sac.sfbay.sun.com>; Tue, 29 May 2007 08:43:33 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by sunmail5.uk.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l4TFg7VS003334
	for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Tue, 29 May 2007 16:42:14 +0100 (BST)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0JIT00B0D7MCSL00@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com
 (ORCPT psarc-ext@sun.com); Tue, 29 May 2007 08:42:12 -0700 (PDT)
Received: from brmea-mail-2.sun.com ([192.18.98.43])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JIT00LR97MBN4B0@nwk-avmta-1.sfbay.Sun.COM> for
 psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue,
 29 May 2007 08:42:12 -0700 (PDT)
Received: from fe-amer-04.sun.com ([192.18.108.178])
	by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l4TFgBNn002865	for
 <psarc-ext@sun.com>; Tue, 29 May 2007 15:42:11 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 id <0JIT000017IYQ400@mail-amer.sun.com>
 (original mail from Sarah.Jelinek@Sun.COM)
 for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue,
 29 May 2007 09:42:11 -0600 (MDT)
Received: from [192.9.61.46] by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 with ESMTPSA id <0JIT00DV27MAEW13@mail-amer.sun.com>; Tue,
 29 May 2007 09:42:11 -0600 (MDT)
Date: Tue, 29 May 2007 09:42:09 -0600
From: Sarah Jelinek <Sarah.Jelinek@sun.com>
Subject: Re: Fast track review - PSARC/2007/284 Dwarf Caiman,
 New Solaris Install GUI - updated spec
In-reply-to: <200705291529.l4TFTCV0023012@marduk.eng.sun.com>
Sender: Sarah.Jelinek@sun.com
To: Gary Winiger <gww@eng.sun.com>
Cc: psarc-ext@sun.com
Reply-to: Sarah.Jelinek@sun.com
Message-id: <465C49D1.9080700@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.2.0.264296
References: <200705291529.l4TFTCV0023012@marduk.eng.sun.com>
User-Agent: Thunderbird 2.0b2 (X11/20070326)
Status: RO
Content-Length: 1262



Gary Winiger wrote:
>> 3.1 Project Requirements
>>
>> 	3.1.1 General:
>> 		1. x86 platform support only. Sparc bits will be built, but
>> 		   there is no boot support for Developer Edition on sparc.
>>     
>
> 	I understand the emphasis here and have no issue with it.
> 	I'd also like to understand why SPARC isn't architecturally
> 	supportable.  And if the intent is for future support.
>   
SPARC is architecturally supportable. And the Dwarf bits will be built 
on both platforms. A decision was made by the developer edition planning 
team to not concentrate on SPARC for the developer edition releases at 
this time, so we have not developed boot support, i.e a SPARC developer 
edition boot flag for these releases. Along with this, the tools bits 
are not included on the SPARC DVD at this time. This decision is based 
on the fact that we would require multi-DVD install support if we added 
the tools as we are running out of space on the SPARC DVD.

As for SPARC support for developer edition, at this time there is no 
plan for this. This decision is left to the developer edition planning 
team. However, with Caiman in general we do plan SPARC support in 
particular when Caiman starts to replace more of the existing installer 
paths.

sarah

From wyllys.ingersoll@sun.com Tue May 29 10:37:17 2007
Received: from sunmail4.Singapore.Sun.COM (sunmail4.Singapore.Sun.COM [129.158.71.19])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l4THbGOP006705
	for <psarc-ext@sac.sfbay.Sun.COM>; Tue, 29 May 2007 10:37:17 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail4.Singapore.Sun.COM (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id l4THZshu021592
	for <@sunmail3mpk.sfbay.sun.com:psarc-ext@sun.com>; Wed, 30 May 2007 01:35:57 +0800 (SGT)
Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by
 nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0JIT00805CVU3T00@nwk-avmta-2.sfbay.sun.com> for psarc-ext@sun.com
 (ORCPT psarc-ext@sun.com); Tue, 29 May 2007 10:35:54 -0700 (PDT)
Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.59])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JIT003DXCVU4PA0@nwk-avmta-2.sfbay.sun.com> for
 psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue,
 29 May 2007 10:35:54 -0700 (PDT)
Received: from [10.7.251.182] (punchin-wyllys.SFBay.Sun.COM [10.7.251.182])
	by jurassic-x4600.sfbay.sun.com (8.14.1+Sun/8.14.1)
 with ESMTP id l4THZqhb900815
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <psarc-ext@sun.com>; Tue, 29 May 2007 10:35:54 -0700 (PDT)
Date: Tue, 29 May 2007 13:35:52 -0400
From: Wyllys Ingersoll <wyllys.ingersoll@sun.com>
Subject: Re: Fast track review - PSARC/2007/284 Dwarf Caiman,
 New Solaris Install GUI - updated spec
In-reply-to: <465606F9.90604@sun.com>
To: psarc-ext@sun.com
Message-id: <465C6478.9090607@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.2.0.264296
References: <465606F9.90604@sun.com>
User-Agent: Thunderbird 2.0.0.0 (X11/20070508)
Status: RO
Content-Length: 888


...
	3.1.4 The SunStudio and NetBeans tools:

		1. Initial Install:

			a) Installation behavior and scripts are provided by
			   the Developer tools team.

			b) During initial install Sun Studio 12 will be
			   installed.

			c) During intial install Sun Studio 12 will install
			   NetBeans 5.5.1 as it currently ships this
			   version.

			d) NetBeans 5.5 will also be installed since
			   NetBeans users are supposed to use this version,
			   and not 5.5.1.
...

Regarding item 'd':  huh?   Is NetBeans 5.5.1 being un-installed to clear the way
for NetBeans 5.5 or do both end up on the system?  Does Studio 12 work OK with
5.5 or does it require 5.5.1 for some operations.   It seems kind of silly that
on one hand we have a product that installs 5.5.1 and then we try to route
around it with this project.  We should get our NetBeans and SunStudio story
straight.

-Wyllys

From Sarah.Jelinek@Sun.COM Tue May 29 15:48:25 2007
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l4TMmOkq014609
	for <psarc-ext@sac.sfbay.sun.com>; Tue, 29 May 2007 15:48:25 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail5.uk.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l4TMl4Wu017400
	for <@newsunmail1brm.central.sun.com:psarc-ext@sun.com>; Tue, 29 May 2007 23:47:05 +0100 (BST)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0JIT00M07RAFLS00@brm-avmta-1.central.sun.com> for psarc-ext@sun.com
 (ORCPT psarc-ext@Sun.COM); Tue, 29 May 2007 16:47:03 -0600 (MDT)
Received: from brmea-mail-2.sun.com ([192.18.98.43])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JIT004PERAFUR80@brm-avmta-1.central.sun.com> for
 psarc-ext@sun.com (ORCPT psarc-ext@Sun.COM); Tue,
 29 May 2007 16:47:03 -0600 (MDT)
Received: from fe-amer-04.sun.com ([192.18.108.178])
	by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l4TMl3Wg016022	for
 <psarc-ext@Sun.COM>; Tue, 29 May 2007 22:47:03 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 id <0JIT00L01RA7XP00@mail-amer.sun.com>
 (original mail from Sarah.Jelinek@Sun.COM)
 for psarc-ext@Sun.COM (ORCPT psarc-ext@Sun.COM); Tue,
 29 May 2007 16:47:03 -0600 (MDT)
Received: from [192.9.61.46] by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 with ESMTPSA id <0JIT00DKGRAEEN65@mail-amer.sun.com> for psarc-ext@Sun.COM
 (ORCPT psarc-ext@Sun.COM); Tue, 29 May 2007 16:47:03 -0600 (MDT)
Date: Tue, 29 May 2007 16:46:57 -0600
From: Sarah Jelinek <Sarah.Jelinek@Sun.COM>
Subject: Re: Fast track review - PSARC/2007/284 Dwarf Caiman,
 New Solaris Install GUI - updated spec
In-reply-to: <465C6478.9090607@sun.com>
Sender: Sarah.Jelinek@Sun.COM
To: Wyllys Ingersoll <Wyllys.Ingersoll@Sun.COM>
Cc: psarc-ext@Sun.COM
Reply-to: Sarah.Jelinek@Sun.COM
Message-id: <465CAD61.7020904@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.2.0.264296
References: <465606F9.90604@sun.com> <465C6478.9090607@sun.com>
User-Agent: Thunderbird 2.0b2 (X11/20070326)
Status: RO
Content-Length: 1868

Hi Wyllys,

Thanks for the review.

> ...
> 	3.1.4 The SunStudio and NetBeans tools:
>
> 		1. Initial Install:
>
> 			a) Installation behavior and scripts are provided by
> 			   the Developer tools team.
>
> 			b) During initial install Sun Studio 12 will be
> 			   installed.
>
> 			c) During intial install Sun Studio 12 will install
> 			   NetBeans 5.5.1 as it currently ships this
> 			   version.
>
> 			d) NetBeans 5.5 will also be installed since
> 			   NetBeans users are supposed to use this version,
> 			   and not 5.5.1.
> ...
>
> Regarding item 'd':  huh?   Is NetBeans 5.5.1 being un-installed to clear the way
> for NetBeans 5.5 or do both end up on the system?  
Both end up on the system. The NetBeans tools deliver 5.5, SunStudio 
delivers 5.5.1 as it has dependencies on this version.
> Does Studio 12 work OK with
> 5.5 or does it require 5.5.1 for some operations.   
It requires 5.5.1.
> It seems kind of silly that
> on one hand we have a product that installs 5.5.1 and then we try to route
> around it with this project.  We should get our NetBeans and SunStudio story
> straight.
>
>   
We aren't trying to route around it. It is the configuration of the 
SunStudio product today. Currently, the Solaris installer gets a script 
and some tar files from the tools team and we call the script to do the 
installation for us. I agree that we need to get our NetBeans and 
SunStudio story straight, but this product is delivered outside of the 
install groups domain. We have asked the tools team to provide pkgs so 
that we can clean things up appropriately and upgrade correctly as well. 
It is unclear whether these will be available by the time Dwarf 
integrates so I noted the current behavior. I hope it will get 
straightened out before we deliver Dwarf. This is the current developer 
express tools installation behavior, FYI.

sarah

From James.McPherson@sun.com Tue May 29 16:50:28 2007
Received: from sunmail4.Singapore.Sun.COM (sunmail4.Singapore.Sun.COM [129.158.71.19])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l4TNoRir015840
	for <psarc-ext@sac.sfbay.Sun.COM>; Tue, 29 May 2007 16:50:28 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by sunmail4.Singapore.Sun.COM (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id l4TNn4RA013397
	for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Wed, 30 May 2007 07:49:08 +0800 (SGT)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0JIT00B09U5SDB00@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com
 (ORCPT psarc-ext@sun.com); Tue, 29 May 2007 16:49:04 -0700 (PDT)
Received: from sineb-mail-1.sun.com ([192.18.19.6])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JIT009XBU5RGL00@nwk-avmta-1.sfbay.Sun.COM> for
 psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue,
 29 May 2007 16:49:04 -0700 (PDT)
Received: from fe-apac-06.sun.com
 (fe-apac-06.sun.com [192.18.19.177] (may be forged))
	by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l4TNn2YW029098	for
 <psarc-ext@sun.com>; Tue, 29 May 2007 23:49:03 +0000 (GMT)
Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 id <0JIT00401U0LBI00@mail-apac.sun.com>
 (original mail from James.McPherson@Sun.COM)
 for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed,
 30 May 2007 07:49:02 +0800 (SGT)
Received: from [129.150.153.2] by mail-apac.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 with ESMTPSA id <0JIT002TNU5O90GG@mail-apac.sun.com> for psarc-ext@sun.com
 (ORCPT psarc-ext@sun.com); Wed, 30 May 2007 07:49:02 +0800 (SGT)
Date: Wed, 30 May 2007 09:48:59 +1000
From: "James C. McPherson" <James.McPherson@sun.com>
Subject: Re: Fast track review - PSARC/2007/284 Dwarf Caiman,
 New Solaris Install GUI - updated spec
In-reply-to: <465C6478.9090607@sun.com>
Sender: James.McPherson@sun.com
To: Sarah Jelinek <Sarah.Jelinek@sun.com>
Cc: psarc-ext@sun.com
Reply-to: James.McPherson@sun.com
Message-id: <465CBBEB.70400@Sun.COM>
Organization: Sun Microsystems
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=UTF-8
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.2.0.264296
References: <465606F9.90604@sun.com> <465C6478.9090607@sun.com>
User-Agent: Thunderbird 2.0b2 (X11/20070123)
Status: RO
Content-Length: 596

Wyllys Ingersoll wrote:
> ...
> 	3.1.4 The SunStudio and NetBeans tools:
> 
> 		1. Initial Install:
> 
> 			a) Installation behavior and scripts are provided by
> 			   the Developer tools team.
> 
> 			b) During initial install Sun Studio 12 will be
> 			   installed.

Hi Sarah,
to the best of my knowledge you cannot build the Nevada
gate (and thus OpenSolaris) with Studio 12. I was under
the impression that being able to build OpenSolaris with
an out of the box SXDE installation was a target of the
SXDE releases.



James C. McPherson
--
Solaris kernel software engineer
Sun Microsystems

From Sarah.Jelinek@sun.com Tue May 29 17:01:44 2007
Received: from sunmail4.Singapore.Sun.COM (sunmail4.Singapore.Sun.COM [129.158.71.19])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l4U01gs7016303
	for <psarc-ext@sac.sfbay.Sun.COM>; Tue, 29 May 2007 17:01:43 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by sunmail4.Singapore.Sun.COM (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id l4U00LUI016248
	for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Wed, 30 May 2007 08:00:23 +0800 (SGT)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0JIT00C0VUOKIB00@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com
 (ORCPT psarc-ext@sun.com); Tue, 29 May 2007 17:00:20 -0700 (PDT)
Received: from brmea-mail-2.sun.com ([192.18.98.43])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JIT0099TUOJGO10@nwk-avmta-1.sfbay.Sun.COM> for
 psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue,
 29 May 2007 17:00:19 -0700 (PDT)
Received: from fe-amer-03.sun.com ([192.18.108.177])
	by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l4U00Ihc003275	for
 <psarc-ext@sun.com>; Wed, 30 May 2007 00:00:18 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 id <0JIT00F01TRVVV00@mail-amer.sun.com>
 (original mail from Sarah.Jelinek@Sun.COM)
 for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue,
 29 May 2007 18:00:18 -0600 (MDT)
Received: from [192.9.61.46] by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 with ESMTPSA id <0JIT003GUUOGNC62@mail-amer.sun.com> for psarc-ext@sun.com
 (ORCPT psarc-ext@sun.com); Tue, 29 May 2007 18:00:18 -0600 (MDT)
Date: Tue, 29 May 2007 18:00:16 -0600
From: Sarah Jelinek <Sarah.Jelinek@sun.com>
Subject: Re: Fast track review - PSARC/2007/284 Dwarf Caiman,
 New Solaris Install GUI - updated spec
In-reply-to: <465CBBEB.70400@Sun.COM>
Sender: Sarah.Jelinek@sun.com
To: James.McPherson@sun.com
Cc: psarc-ext@sun.com
Reply-to: Sarah.Jelinek@sun.com
Message-id: <465CBE90.1030807@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.2.0.264296
References: <465606F9.90604@sun.com> <465C6478.9090607@sun.com>
 <465CBBEB.70400@Sun.COM>
User-Agent: Thunderbird 2.0b2 (X11/20070326)
Status: RO
Content-Length: 1139



James C. McPherson wrote:
> Wyllys Ingersoll wrote:
>> ...
>>     3.1.4 The SunStudio and NetBeans tools:
>>
>>         1. Initial Install:
>>
>>             a) Installation behavior and scripts are provided by
>>                the Developer tools team.
>>
>>             b) During initial install Sun Studio 12 will be
>>                installed.
>
> Hi Sarah,
> to the best of my knowledge you cannot build the Nevada
> gate (and thus OpenSolaris) with Studio 12. I was under
> the impression that being able to build OpenSolaris with
> an out of the box SXDE installation was a target of the
> SXDE releases.
Well.. that would be bad if you can't build OpenSolaris with SunStudio 
12. Certainly, one of our goals is to build OpenSolaris out of the box. 
I am not aware if this is the case or not, I cannot imagine we would 
deliver a set of tools that didn't give us what we needed, but I will 
check on this.

thanks,
sarah
****
>
>
>
> James C. McPherson
> -- 
> Solaris kernel software engineer
> Sun Microsystems
> _______________________________________________
> opensolaris-arc mailing list
> opensolaris-arc@opensolaris.org

From Sarah.Jelinek@Sun.COM Wed May 30 05:43:20 2007
Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l4UChKkO026998
	for <psarc-ext@sac.sfbay.sun.com>; Wed, 30 May 2007 05:43:20 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l4UCg1SV025494
	for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Wed, 30 May 2007 05:42:01 -0700 (PDT)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0JIU00L0BTY1RK00@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com
 (ORCPT psarc-ext@sun.com); Wed, 30 May 2007 05:42:01 -0700 (PDT)
Received: from brmea-mail-4.sun.com ([192.18.98.36])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JIU005OVTY0ZID0@nwk-avmta-1.sfbay.Sun.COM> for
 psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed,
 30 May 2007 05:42:01 -0700 (PDT)
Received: from fe-amer-02.sun.com ([192.18.108.176])
	by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l4UCg0le029528	for
 <psarc-ext@sun.com>; Wed, 30 May 2007 12:42:00 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 id <0JIU00101TOCN100@mail-amer.sun.com>
 (original mail from Sarah.Jelinek@Sun.COM)
 for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed,
 30 May 2007 06:42:00 -0600 (MDT)
Received: from [192.9.61.46] by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 with ESMTPSA id <0JIU00JJPTXZSWK4@mail-amer.sun.com> for psarc-ext@sun.com
 (ORCPT psarc-ext@sun.com); Wed, 30 May 2007 06:42:00 -0600 (MDT)
Date: Wed, 30 May 2007 06:41:59 -0600
From: Sarah Jelinek <Sarah.Jelinek@Sun.COM>
Subject: Re: Fast track review - PSARC/2007/284 Dwarf Caiman,
 New Solaris Install GUI - updated spec
In-reply-to: <465CBBEB.70400@Sun.COM>
Sender: Sarah.Jelinek@Sun.COM
To: James.McPherson@Sun.COM
Cc: psarc-ext@Sun.COM
Reply-to: Sarah.Jelinek@Sun.COM
Message-id: <465D7117.9050209@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.2.0.264296
References: <465606F9.90604@sun.com> <465C6478.9090607@sun.com>
 <465CBBEB.70400@Sun.COM>
User-Agent: Thunderbird 2.0b2 (X11/20070326)
Status: RO
Content-Length: 2014

Hi James,

Apparently you are correct, SunStudio 12 cannot successfully build the 
most recent OpenSolaris bits. I validated this with the tools team. 
There are apparently some warnings that are generated during the build, 
which the tools team believe are erroneous, but the build rules don't 
allow the build to proceed with these warnings. For the next release, 
08/06 Developer Edition, SunStudio 12 is the version they will be 
delivering. My hope is that they will get this fixed prior to Dwarf 
releasing. I have also asked them to reconsider the decision to deliver 
12 in light of this issue.

The one thing we can do is include in the release notes that users who 
want to stay with SunStudio 11 and who are upgrading, simply do not 
remove 11 before upgrading to the next developer edition release. 
SunStudio 11 does build OpenSolaris correctly. As noted in my ARC case 
if 11 is installed on the system being upgraded then 12 will not be 
installed. This doesn't help the initial install consumers but helps a 
subset of our target audience.

I will continue to track this issue for Dwarf and try to get a better 
resolution. Thank you for bringing this to my attention.

sarah
****

James C. McPherson wrote:
> Wyllys Ingersoll wrote:
>> ...
>>     3.1.4 The SunStudio and NetBeans tools:
>>
>>         1. Initial Install:
>>
>>             a) Installation behavior and scripts are provided by
>>                the Developer tools team.
>>
>>             b) During initial install Sun Studio 12 will be
>>                installed.
>
> Hi Sarah,
> to the best of my knowledge you cannot build the Nevada
> gate (and thus OpenSolaris) with Studio 12. I was under
> the impression that being able to build OpenSolaris with
> an out of the box SXDE installation was a target of the
> SXDE releases.
>
>
>
> James C. McPherson
> -- 
> Solaris kernel software engineer
> Sun Microsystems
> _______________________________________________
> opensolaris-arc mailing list
> opensolaris-arc@opensolaris.org

From Sarah.Jelinek@sun.com Wed May 30 05:53:42 2007
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l4UCrfFt027038
	for <psarc-ext@sac.sfbay.sun.com>; Wed, 30 May 2007 05:53:42 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail5.uk.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l4UCqKR7008003
	for <@newsunmail1brm.central.sun.com:psarc-ext@sun.com>; Wed, 30 May 2007 13:52:21 +0100 (BST)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0JIU00107UF8A400@brm-avmta-1.central.sun.com> for psarc-ext@sun.com
 (ORCPT psarc-ext@sun.com); Wed, 30 May 2007 06:52:20 -0600 (MDT)
Received: from brmea-mail-4.sun.com ([192.18.98.36])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JIU000FRUF7P0F0@brm-avmta-1.central.sun.com> for
 psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed,
 30 May 2007 06:52:19 -0600 (MDT)
Received: from fe-amer-03.sun.com ([192.18.108.177])
	by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l4UCqJmQ002913	for
 <psarc-ext@sun.com>; Wed, 30 May 2007 12:52:19 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 id <0JIU00A01TYAQA00@mail-amer.sun.com>
 (original mail from Sarah.Jelinek@Sun.COM)
 for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed,
 30 May 2007 06:52:19 -0600 (MDT)
Received: from [192.9.61.46] by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 with ESMTPSA id <0JIU003SIUF5NC92@mail-amer.sun.com> for psarc-ext@sun.com
 (ORCPT psarc-ext@sun.com); Wed, 30 May 2007 06:52:18 -0600 (MDT)
Date: Wed, 30 May 2007 06:52:16 -0600
From: Sarah Jelinek <Sarah.Jelinek@sun.com>
Subject: Re: Fast track review - PSARC/2007/284 Dwarf Caiman,
 New Solaris Install GUI - updated spec
In-reply-to: <465D7117.9050209@sun.com>
Sender: Sarah.Jelinek@sun.com
To: Sarah.Jelinek@sun.com
Cc: James.McPherson@sun.com, psarc-ext@sun.com
Reply-to: Sarah.Jelinek@sun.com
Message-id: <465D7380.1000809@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.2.0.264296
References: <465606F9.90604@sun.com> <465C6478.9090607@sun.com>
 <465CBBEB.70400@Sun.COM> <465D7117.9050209@sun.com>
User-Agent: Thunderbird 2.0b2 (X11/20070326)
Status: RO
Content-Length: 2945

Actually, one other thought... perhaps we could include 2 compilers, 11 
and 12+ as we release new developer edition versions. So, that the 
current CBE can be included along with the newest version of SunStudio 
for application compilation, which is why I believe we deliver these. 
The major issues are: 1) do we have enough space on the DVD to include 
both and 2) the disk space required for the installation with additional 
tools. Even just putting the CBE on the DVD we deliver without 
necessarily automatically installing it would make it easier for users 
to get it if they want.

The unfortunate thing about this is that the original release of 
developer edition included the CBE we use to build OpenSolaris, and now 
we are introducing a new version that won't. This will be unexpected to 
our consumers.

sarah
****

Sarah Jelinek wrote:
> Hi James,
>
> Apparently you are correct, SunStudio 12 cannot successfully build the 
> most recent OpenSolaris bits. I validated this with the tools team. 
> There are apparently some warnings that are generated during the 
> build, which the tools team believe are erroneous, but the build rules 
> don't allow the build to proceed with these warnings. For the next 
> release, 08/06 Developer Edition, SunStudio 12 is the version they 
> will be delivering. My hope is that they will get this fixed prior to 
> Dwarf releasing. I have also asked them to reconsider the decision to 
> deliver 12 in light of this issue.
>
> The one thing we can do is include in the release notes that users who 
> want to stay with SunStudio 11 and who are upgrading, simply do not 
> remove 11 before upgrading to the next developer edition release. 
> SunStudio 11 does build OpenSolaris correctly. As noted in my ARC case 
> if 11 is installed on the system being upgraded then 12 will not be 
> installed. This doesn't help the initial install consumers but helps a 
> subset of our target audience.
>
> I will continue to track this issue for Dwarf and try to get a better 
> resolution. Thank you for bringing this to my attention.
>
> sarah
> ****
>
> James C. McPherson wrote:
>> Wyllys Ingersoll wrote:
>>> ...
>>>     3.1.4 The SunStudio and NetBeans tools:
>>>
>>>         1. Initial Install:
>>>
>>>             a) Installation behavior and scripts are provided by
>>>                the Developer tools team.
>>>
>>>             b) During initial install Sun Studio 12 will be
>>>                installed.
>>
>> Hi Sarah,
>> to the best of my knowledge you cannot build the Nevada
>> gate (and thus OpenSolaris) with Studio 12. I was under
>> the impression that being able to build OpenSolaris with
>> an out of the box SXDE installation was a target of the
>> SXDE releases.
>>
>>
>>
>> James C. McPherson
>> -- 
>> Solaris kernel software engineer
>> Sun Microsystems
>> _______________________________________________
>> opensolaris-arc mailing list
>> opensolaris-arc@opensolaris.org
>

From Marcel.Telka@sun.com Wed May 30 06:12:35 2007
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l4UDCYsc027471
	for <psarc-ext@sac.sfbay.sun.com>; Wed, 30 May 2007 06:12:34 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by sunmail5.uk.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l4UDBClA014269
	for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Wed, 30 May 2007 14:11:14 +0100 (BST)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0JIU0010FVAOK500@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com
 (ORCPT psarc-ext@sun.com); Wed, 30 May 2007 06:11:12 -0700 (PDT)
Received: from gmp-ea-fw-1.sun.com ([129.156.42.6])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JIU00MYXVANV630@nwk-avmta-1.sfbay.Sun.COM> for
 psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed,
 30 May 2007 06:11:12 -0700 (PDT)
Received: from d1-emea-09.sun.com ([192.18.2.119])
	by gmp-ea-fw-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l4UDBAXp015014	for
 <psarc-ext@sun.com>; Wed, 30 May 2007 13:11:10 +0000 (GMT)
Received: from conversion-daemon.d1-emea-09.sun.com by d1-emea-09.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 id <0JIU00601V848600@d1-emea-09.sun.com>
 (original mail from Marcel.Telka@Sun.COM)
 for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed,
 30 May 2007 14:11:10 +0100 (BST)
Received: from [129.157.71.66] by d1-emea-09.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 with ESMTPSA id <0JIU005S0VALM0X5@d1-emea-09.sun.com> for psarc-ext@sun.com
 (ORCPT psarc-ext@sun.com); Wed, 30 May 2007 14:11:10 +0100 (BST)
Date: Wed, 30 May 2007 15:11:05 +0200
From: Marcel Telka <Marcel.Telka@sun.com>
Subject: Re: Fast track review - PSARC/2007/284 Dwarf Caiman,
 New Solaris	Install GUI - updated spec
In-reply-to: <465D7117.9050209@sun.com>
Sender: Marcel.Telka@sun.com
To: Sarah.Jelinek@sun.com
Cc: James.McPherson@sun.com, psarc-ext@sun.com
Message-id: <1180530665.20484.29.camel@tortuga>
MIME-version: 1.0
X-Mailer: Evolution 2.10.1
Content-type: text/plain
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.2.0.264296
References: <465606F9.90604@sun.com> <465C6478.9090607@sun.com>
 <465CBBEB.70400@Sun.COM> <465D7117.9050209@sun.com>
Status: RO
Content-Length: 2240

On Wed, 2007-05-30 at 06:41 -0600, Sarah Jelinek wrote:
> Hi James,
> 
> Apparently you are correct, SunStudio 12 cannot successfully build the 
> most recent OpenSolaris bits. I validated this with the tools team. 
> There are apparently some warnings that are generated during the build, 
> which the tools team believe are erroneous, but the build rules don't 
> allow the build to proceed with these warnings. For the next release, 
> 08/06 Developer Edition, SunStudio 12 is the version they will be 

08/06? I think there should be 08/07...

> delivering. My hope is that they will get this fixed prior to Dwarf 
> releasing. I have also asked them to reconsider the decision to deliver 
> 12 in light of this issue.
> 
> The one thing we can do is include in the release notes that users who 
> want to stay with SunStudio 11 and who are upgrading, simply do not 
> remove 11 before upgrading to the next developer edition release. 
> SunStudio 11 does build OpenSolaris correctly. As noted in my ARC case 
> if 11 is installed on the system being upgraded then 12 will not be 
> installed. This doesn't help the initial install consumers but helps a 
> subset of our target audience.
> 
> I will continue to track this issue for Dwarf and try to get a better 
> resolution. Thank you for bringing this to my attention.
> 
> sarah
> ****
> 
> James C. McPherson wrote:
> > Wyllys Ingersoll wrote:
> >> ...
> >>     3.1.4 The SunStudio and NetBeans tools:
> >>
> >>         1. Initial Install:
> >>
> >>             a) Installation behavior and scripts are provided by
> >>                the Developer tools team.
> >>
> >>             b) During initial install Sun Studio 12 will be
> >>                installed.
> >
> > Hi Sarah,
> > to the best of my knowledge you cannot build the Nevada
> > gate (and thus OpenSolaris) with Studio 12. I was under
> > the impression that being able to build OpenSolaris with
> > an out of the box SXDE installation was a target of the
> > SXDE releases.
> >
> >
> >
> > James C. McPherson
> > -- 
> > Solaris kernel software engineer
> > Sun Microsystems
> > _______________________________________________
> > opensolaris-arc mailing list
> > opensolaris-arc@opensolaris.org
-- 
Marcel Telka


From Sarah.Jelinek@sun.com Wed May 30 06:17:53 2007
Received: from sunmail4.Singapore.Sun.COM (sunmail4.Singapore.Sun.COM [129.158.71.19])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l4UDHq9r027490
	for <psarc-ext@sac.sfbay.Sun.COM>; Wed, 30 May 2007 06:17:53 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail4.Singapore.Sun.COM (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id l4UDGNBQ017327
	for <@sunmail3mpk.sfbay.sun.com:psarc-ext@sun.com>; Wed, 30 May 2007 21:16:32 +0800 (SGT)
Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by
 nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0JIU00K13VJHC600@nwk-avmta-2.sfbay.sun.com> for psarc-ext@sun.com
 (ORCPT psarc-ext@sun.com); Wed, 30 May 2007 06:16:29 -0700 (PDT)
Received: from brmea-mail-1.sun.com ([192.18.98.31])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JIU00A0WVJHHD70@nwk-avmta-2.sfbay.sun.com> for
 psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed,
 30 May 2007 06:16:29 -0700 (PDT)
Received: from fe-amer-06.sun.com ([192.18.108.180])
	by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l4UDGTmk009098	for
 <psarc-ext@sun.com>; Wed, 30 May 2007 13:16:29 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 id <0JIU00401VGAVT00@mail-amer.sun.com>
 (original mail from Sarah.Jelinek@Sun.COM)
 for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed,
 30 May 2007 07:16:28 -0600 (MDT)
Received: from [192.9.61.46] by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 with ESMTPSA id <0JIU002TVVJF0RU3@mail-amer.sun.com> for psarc-ext@sun.com
 (ORCPT psarc-ext@sun.com); Wed, 30 May 2007 07:16:28 -0600 (MDT)
Date: Wed, 30 May 2007 07:16:26 -0600
From: Sarah Jelinek <Sarah.Jelinek@sun.com>
Subject: Re: Fast track review - PSARC/2007/284 Dwarf Caiman,
 New Solaris Install GUI - updated spec
In-reply-to: <1180530665.20484.29.camel@tortuga>
Sender: Sarah.Jelinek@sun.com
To: Marcel Telka <Marcel.Telka@sun.com>
Cc: James.McPherson@sun.com, psarc-ext@sun.com
Reply-to: Sarah.Jelinek@sun.com
Message-id: <465D792A.2090006@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.2.0.264296
References: <465606F9.90604@sun.com> <465C6478.9090607@sun.com>
 <465CBBEB.70400@Sun.COM> <465D7117.9050209@sun.com>
 <1180530665.20484.29.camel@tortuga>
User-Agent: Thunderbird 2.0b2 (X11/20070326)
Status: RO
Content-Length: 633



Marcel Telka wrote:
> On Wed, 2007-05-30 at 06:41 -0600, Sarah Jelinek wrote:
>   
>> Hi James,
>>
>> Apparently you are correct, SunStudio 12 cannot successfully build the 
>> most recent OpenSolaris bits. I validated this with the tools team. 
>> There are apparently some warnings that are generated during the build, 
>> which the tools team believe are erroneous, but the build rules don't 
>> allow the build to proceed with these warnings. For the next release, 
>> 08/06 Developer Edition, SunStudio 12 is the version they will be 
>>     
>
> 08/06? I think there should be 08/07...
>
>   
yes, a typo. 08/07 is correct.


From jek3@sun.com Wed May 30 15:02:14 2007
Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l4UM2E35017427
	for <psarc-ext@sac.sfbay.sun.com>; Wed, 30 May 2007 15:02:14 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l4UM0jjm010868;
	Wed, 30 May 2007 15:00:51 -0700 (PDT)
Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by
 nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0JIV00K1HJTEWS00@nwk-avmta-2.sfbay.sun.com>; Wed,
 30 May 2007 15:00:50 -0700 (PDT)
Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.63])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JIV00CGCJTDPZ90@nwk-avmta-2.sfbay.sun.com>; Wed,
 30 May 2007 15:00:49 -0700 (PDT)
Received: from [129.150.12.53]
 (vpn-129-150-12-53.SFBay.Sun.COM [129.150.12.53])	by
 jurassic-x4600.sfbay.sun.com (8.14.1+Sun/8.14.1) with ESMTP id l4UM0jrS332399;
 Wed, 30 May 2007 15:00:45 -0700 (PDT)
Date: Wed, 30 May 2007 12:00:27 -1000
From: Joseph Kowalski <jek3@sun.com>
Subject: Re: Fast track review - PSARC/2007/284 Dwarf Caiman,
 New Solaris Install GUI - updated spec
In-reply-to: <465CBE90.1030807@sun.com>
To: Sarah.Jelinek@sun.com
Cc: James.McPherson@sun.com, psarc-ext@sun.com
Message-id: <465DF3FB.7010507@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.2.0.264296
References: <465606F9.90604@sun.com> <465C6478.9090607@sun.com>
 <465CBBEB.70400@Sun.COM> <465CBE90.1030807@sun.com>
User-Agent: Thunderbird 1.5.0.5 (X11/20060925)
Status: RO
Content-Length: 1470

Sarah Jelinek wrote:
>
>
> James C. McPherson wrote:
>> Hi Sarah,
>> to the best of my knowledge you cannot build the Nevada
>> gate (and thus OpenSolaris) with Studio 12. I was under
>> the impression that being able to build OpenSolaris with
>> an out of the box SXDE installation was a target of the
>> SXDE releases.
> Well.. that would be bad if you can't build OpenSolaris with SunStudio 
> 12. Certainly, one of our goals is to build OpenSolaris out of the 
> box. I am not aware if this is the case or not, I cannot imagine we 
> would deliver a set of tools that didn't give us what we needed, but I 
> will check on this.
Well, its probably not a requirement on the Solaris PAC's radar, but 
whatever SunStudio version delivered with SXDE should also be able to 
build the OpenJDK sources, which although in a different community 
space, are certainly part of the Solaris world.

I've been trying to build OpenJDK on a number of systems.  Most take 
quite a few steps (and some I'm not sure are possible yet).  By far the 
simplest was the last SXDE, which was basically install it, download the 
OpenJDK sources, set a few environment variables and you were off and 
running.  I think this makes Sun and Solaris look very good it the eyes 
of the community.

If this isn't true of the next SXDE, we need to do something about that 
at the PAC level.  I'm not sure it is really this case, but this may be 
our only way to bring it to their attention.

- jek3


From jek3@Sun.COM Wed May 30 15:21:02 2007
Received: from sunmail4.Singapore.Sun.COM (sunmail4.Singapore.Sun.COM [129.158.71.19])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l4UML1PD017869
	for <psarc-ext@sac.sfbay.Sun.COM>; Wed, 30 May 2007 15:21:02 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail4.Singapore.Sun.COM (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id l4UMJa3Q016047;
	Thu, 31 May 2007 06:19:38 +0800 (SGT)
Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by
 nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0JIV00L0LKOPTX00@nwk-avmta-2.sfbay.sun.com>; Wed,
 30 May 2007 15:19:37 -0700 (PDT)
Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.59])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JIV00CPMKOPPZA0@nwk-avmta-2.sfbay.sun.com>; Wed,
 30 May 2007 15:19:37 -0700 (PDT)
Received: from [129.150.12.53]
 (vpn-129-150-12-53.SFBay.Sun.COM [129.150.12.53])	by
 jurassic-x4600.sfbay.sun.com (8.14.1+Sun/8.14.1) with ESMTP id l4UMJa65337865;
 Wed, 30 May 2007 15:19:36 -0700 (PDT)
Date: Wed, 30 May 2007 12:19:19 -1000
From: Joseph Kowalski <jek3@Sun.COM>
Subject: Re: Fast track review - PSARC/2007/284 Dwarf Caiman,
 New Solaris Install GUI - updated spec
In-reply-to: <465D7380.1000809@sun.com>
To: Sarah.Jelinek@Sun.COM
Cc: James.McPherson@Sun.COM, psarc-ext@Sun.COM
Message-id: <465DF867.6020302@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.2.0.264296
References: <465606F9.90604@sun.com> <465C6478.9090607@sun.com>
 <465CBBEB.70400@Sun.COM> <465D7117.9050209@sun.com> <465D7380.1000809@sun.com>
User-Agent: Thunderbird 1.5.0.5 (X11/20060925)
Status: RO
Content-Length: 1392

Sarah Jelinek wrote:
> Actually, one other thought... perhaps we could include 2 compilers, 
> 11 and 12+ as we release new developer edition versions. So, that the 
> current CBE can be included along with the newest version of SunStudio 
> for application compilation, which is why I believe we deliver these. 
> The major issues are: 1) do we have enough space on the DVD to include 
> both and 2) the disk space required for the installation with 
> additional tools. Even just putting the CBE on the DVD we deliver 
> without necessarily automatically installing it would make it easier 
> for users to get it if they want.
>
> The unfortunate thing about this is that the original release of 
> developer edition included the CBE we use to build OpenSolaris, and 
> now we are introducing a new version that won't. This will be 
> unexpected to our consumers.
And OpenJDK...

We should do the obvious and simple thing. Until SunStudio 12 can 
successfully build all of the communities which are perceived as 
originating from Sun, we should continue to bundle SunStudio 11 and have 
it be the default.  If it is somehow worth the effort to include 
SunStudio 12, it should only be as a (recursive?) technology preview.

Unfortunately, I'm having trouble finding the architecture in this.

Since this is an open case, I'm trying to be very PC in my choice of 
words. :-)

KISS!

- jek3


From Sarah.Jelinek@Sun.COM Thu May 31 06:31:29 2007
Received: from sunmail4.Singapore.Sun.COM (sunmail4.Singapore.Sun.COM [129.158.71.19])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l4VDVSAw001474
	for <psarc-ext@sac.sfbay.Sun.COM>; Thu, 31 May 2007 06:31:28 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by sunmail4.Singapore.Sun.COM (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id l4VDU4gn002528
	for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Thu, 31 May 2007 21:30:06 +0800 (SGT)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0JIW0060BQU4AD00@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com
 (ORCPT psarc-ext@sun.com); Thu, 31 May 2007 06:30:04 -0700 (PDT)
Received: from brmea-mail-2.sun.com ([192.18.98.43])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JIW009U4QU1UC80@nwk-avmta-1.sfbay.Sun.COM> for
 psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Thu,
 31 May 2007 06:30:02 -0700 (PDT)
Received: from fe-amer-01.sun.com ([192.18.108.175])
	by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l4VDU1sm019175	for
 <psarc-ext@sun.com>; Thu, 31 May 2007 13:30:01 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 id <0JIW00H01QJZYI00@mail-amer.sun.com>
 (original mail from Sarah.Jelinek@Sun.COM)
 for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Thu,
 31 May 2007 07:30:01 -0600 (MDT)
Received: from [10.7.250.94] by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 with ESMTPSA id <0JIW00I3OQTZT8S2@mail-amer.sun.com>; Thu,
 31 May 2007 07:30:01 -0600 (MDT)
Date: Thu, 31 May 2007 07:29:58 -0600
From: Sarah Jelinek <Sarah.Jelinek@Sun.COM>
Subject: Re: Fast track review - PSARC/2007/284 Dwarf Caiman,
 New Solaris Install GUI - updated spec
In-reply-to: <465DF867.6020302@sun.com>
Sender: Sarah.Jelinek@Sun.COM
To: Joseph Kowalski <jek3@Sun.COM>
Cc: James.McPherson@Sun.COM, psarc-ext@Sun.COM
Reply-to: Sarah.Jelinek@Sun.COM
Message-id: <465ECDD6.5060002@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.2.0.264296
References: <465606F9.90604@sun.com> <465C6478.9090607@sun.com>
 <465CBBEB.70400@Sun.COM> <465D7117.9050209@sun.com> <465D7380.1000809@sun.com>
 <465DF867.6020302@sun.com>
User-Agent: Thunderbird 2.0b2 (X11/20070326)
Status: RO
Content-Length: 2254



Joseph Kowalski wrote:
> Sarah Jelinek wrote:
>> Actually, one other thought... perhaps we could include 2 compilers, 
>> 11 and 12+ as we release new developer edition versions. So, that the 
>> current CBE can be included along with the newest version of 
>> SunStudio for application compilation, which is why I believe we 
>> deliver these. The major issues are: 1) do we have enough space on 
>> the DVD to include both and 2) the disk space required for the 
>> installation with additional tools. Even just putting the CBE on the 
>> DVD we deliver without necessarily automatically installing it would 
>> make it easier for users to get it if they want.
>>
>> The unfortunate thing about this is that the original release of 
>> developer edition included the CBE we use to build OpenSolaris, and 
>> now we are introducing a new version that won't. This will be 
>> unexpected to our consumers.
> And OpenJDK...
>
> We should do the obvious and simple thing. Until SunStudio 12 can 
> successfully build all of the communities which are perceived as 
> originating from Sun, we should continue to bundle SunStudio 11 and 
> have it be the default.  If it is somehow worth the effort to include 
> SunStudio 12, it should only be as a (recursive?) technology preview.
I think the intent is that SXDE is a pre-release vehicle for the Sun 
Studio 12 compilers. Work is being done internally to get this to build 
OpenSolaris. SunStudio 11 will not be installed with an initial 
installation of SXDE2. Users can however download it and install it 
themselves. At a minimum, we need to release note the issues.

The decision to deliver SunStudio 12 was made by the SXDE core planning 
team. I agree that we have a potential issue here but I will point you 
to this team for further discussion related specifically to this. And, 
no, I am not copping out on this... I have made the SXDE core planning 
team aware of the specific technical issues that are preventing 12 from 
building our sources and we are having a conversation regarding what to do.

thanks,
sarah
>
> Unfortunately, I'm having trouble finding the architecture in this.
>
> Since this is an open case, I'm trying to be very PC in my choice of 
> words. :-)
>
> KISS!
>
> - jek3
>

