IAM
======
Name:           S10C
Submitter:      Gerald Jelinek
Owner:          Rick Matthews
Intern:         Dean Roehrich
Status:         submitted
Exposure:       open

SUMMARY
=======

Use the BrandZ infrastructure to deliver a Solaris 10 (S10) brand for
Solaris.next (S.next).  This will be provided as an adoption and
compatibility aid to enable customers currently running S10 to easily
adopt S.next while also continuing to run their S10 software within
branded zones.  This allows the customer to rapidly switch over to
S.next, creating a win-win situation for Sun and its customers.


ISSUES
======

 PSARC 2009/253:	S10C
 Submitter:	Gerald Jelinek
 Owner:		Rick Matthews
 Intern:		Dean Roehrich
 
 Issues for inception (05/27/2009):
 
 ged-1	As of build 115, SXCE/OpenSolaris/Nevada contain a new audio
 	framework.  (PSARC 2008/318 Boomer) This framework has some
 	potentially incompatible changes which will break certain
 	applications -- particularly the desktop volume control applications.
 	In Boomer we decided that this compatibility was not needed,
 	since the desktop apps were being upgraded to the Boomer interfaces
 	at the same time.   Is the compatibility here an issue for S10C?
 	If so, how will it be addressed.
 
 jdc-1	What happens with lofs mounts in v2v?  Many people are using
 	these to work around limitations in Zones -- for example,
 	adding a writable /usr/local to an otherwise sparse root
 	zone, adding a "global zone name" file, or sharing data
 	between zones.
 
 jdc-2	What sorts of factors should the ARC consider when granting
 	patch/micro release binding?  Are there specific areas where
 	updates to the branding module will be needed?
 
 	(One caution here is that some private interfaces, even those
 	that cross the kernel/user barrier, are changed occasionally
 	without ARC review.  Merely requiring the ARC to note this
 	issue may not be sufficent to be 'safe'; restricting change
 	will also be necessary.)
 
 	(In the past, we've been saved by circumstance: there are very
 	few backports to S9 or older, so even though "patch/micro"
 	authorizes them, they don't happen, and haven't been
 	considered in the past.  Without an enterprise OpenSolaris,
 	S10 is currently different.)
 
 jdc-3	Meem's comments about the non-Crossbow projects (such as
 	Clearview) that affect whole root zones will also need to be
 	addressed in the commitment.
 
 gw-1	What is the list of S10ux "Features" that are not supported?
 	You note zones and TX, and exclusive stacks.  Are there others?


THE NEXT STEP
=============

Return mid summer 2009 for an update