Dave Miner writes: > Mike Gerdts wrote: [...] > > thing with external visibility that it will be very shortly." I think > > that this view comes from experience with various things from Sun > > being delayed so long as to make it so that I put in long-term > > workarounds that I'm not terribly interested in undoing. This has [...] > I don't think it's quite nothing, but admittedly there's a gap between > contributing something to OpenSolaris and having it show up in a > supported Solaris release. That won't get any better so long as Solaris > 10 is the current fully-supported release, but one of the points of > Indiana is to move us in the direction of having a supported Solaris > that's based on OpenSolaris. Until that point in time, I agree, you're > going to be frustrated if we have problems like the above (and yes, the > WAN installation one represented a particularly galling lack of > alignment between Sun businesses - I don't know enough about any of the > others to comment constructively).
It wasn't clear to me whether he was referring to having contributions show up in Solaris itself (there's never any guarantee of that; OpenSolaris is the next release under development, but no distributor is under any obligation to take the bits) or just the ability for customers to patch over the defects that Sun has been unable to fix. I assumed it was the latter, and it looks like you assumed the former. Either way, though, I'm not sure that getting things into Solaris patches is really on-target here. The other poster who mentioned patches on unbundled software was on-target, though. Since that *is* possible, and since those sorts of patches may not be going away soon, I think we have an obligation to get pdo.c out there. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
