Sebastien, VirtualBox is available for about 25 flavors of Linux and all kind of interfaces get broken in every possible way, in average we have one interface breakage a week. So we are not concerned at all. If you want to change the Crossbow APIs we use, just do it and if possible, let us know in advance.
-- Achim Hasenmueller Director Engineering, VirtualBox Sun Microsystems GmbH Werkstrasse 24 71384 Weinstadt, Germany phone: +49 7151 604050 ================================================ Sitz der Gesellschaft: Sun Microsystems GmbH, Sonnenallee 1, 85551 Kirchheim-Heimstetten Amtsgericht Muenchen: HRB 161028 On Apr 7, 2010, at 17:36 , Sebastien Roy wrote: > On 04/ 5/10 02:47 PM, Krishna Yenduri wrote: >> It was pointed out to me that this needs to be a fast track since >> there is a contract. So, I am making this a fast track case >> with the timer set to 4/9/2010. > ... >> Header files: >> <sys/mac.h> Consolidation Private >> <sys/mac_client.h> Consolidation Private >> <sys/vnic_mgmt.h> Consolidation Private >> <sys/dls.h> Consolidation Private > > The latter three header files are not currently included in any package. I > assume that this case delivers these header files as part of some package, > presumably pkg:/system/header.(?) > > I am generally concerned about the viability of long term use of these > contracted interfaces by another consolidation given that the interfaces are > not centralized in any part of the ON source (there's no easy way to place a > big warning in the code concerning their consumption by another > consolidation), and that these interfaces have recently undergone numerous > and drastic changes. Assuming that interfaces remain volatile, this could > lead to either unintentional breakage of VirtualBox, or complex version > dependencies between VirtualBox and the underlying host OS. This is less of > a concern if the interfaces contracted have sedimented somewhat and are more > stable than they have been in the recent past. > > This could be mitigated in a number of ways in the longer term. Committing to > a Public MAC client API and VNIC API would be one solution. Another might be > to integrate the Solaris kernel specific portion of VirtualBox into ON. Has > either project team considered such options? > > -Seb Geschaeftsfuehrer: Jürgen Kunz ================================================ _______________________________________________ opensolaris-arc mailing list [email protected]
