Thinking aloud a little..

Need to do my homework on distro builder to understand the limits (can they do something which exposes a significant risk for support). I cannot see a problem with Sun supporting other distro's.  I can see a very valid need for a ISV to build an appliance based on OpenSolaris using distro builder and wanting customers to see Sun for support on the supported packages. If the customer writes a contract for support against those bits..

The idea of multiple vendors wanting to provide support is interesting. If someone spins a distro, they may want to ensure they provide support and not have metadata identifying another support provider.

I need to apply some thought..

Brad



Alan Coopersmith wrote:
Brad Vaughan wrote:
  
I would like to get included in the metadata definition a (or some)
attribute(s) associated with service delivery.

So if we could have a bit of information that communicated where to go
and get more detailed information (URL, Vendor Name, Contact Details, or
None).
    

That seems to assume the same bits have the same support level and vendor
no matter who you got them from, or under what support arrangements.

Given the discussions about allowing others to use the Distro Constructor
to make their own distros, is that the right assumption?    If Belenix
uses OpenSolaris packages to make their distro, but substitutes GNOME
with KDE, should their packages still say "Supported by Sun", even if
they're just using the OpenSolaris kernel packages Sun built?

  

--
Brad Vaughan
Software Services
Services Product Group
Sun Microsystems Inc
Phone x81869/+1-408-519-0898
Mobile +1-408-439-1507
Email [EMAIL PROTECTED]
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to