Charles Meo wrote: > Apologies definitely not needed. I think everyone appreciates the > massive amount of work involved and it's hardly your > fault that S'noracle has shall we say lost focus over the last few > months, and not just on engineering issues. I work for a Sun > partner and the ride has been bumpy to say the least. Things seem to be > improving across the board though.
Uh, no, it's not that sort of thing. It's great that Brendan Gregg is offering to clean up the scripts that exist, and I wish him luck in tracking down all the patch levels required to do that, but the truth is that the scripts were originally written to use internal interfaces that are _intentionally_ not stable. That internal interfaces are not stable has been true since the beginning of time and is still true now for those same interfaces in OpenSolaris. What's actually changed in OpenSolaris is that *NEW* stable interfaces were introduced on which scripts like those could safely be (re)written. It just was not safe to write those scripts before there were stable interfaces that could be used, and that lack of safety is what's showing up. Blaming the problem on a lack of "focus" or something having to do with Oracle is to completely miss the point. The problem was an inappropriate (albeit unavoidable) reliance on undocumented implementation artifacts, and the issues you experienced are the unavoidable outcome of that sort of design. This sort of problem has happened many times in the past, and will almost certainly happen many times again in the future. As long as there are folks writing independently delivered and maintained software that depends on undocumented and unstable interfaces, you're going to have field breakage and unhappy users. For what it's worth, that's exactly why Sun has run an architecture review board for 20 years, and why Oracle continues to do so. -- James Carlson 42.703N 71.076W <carls...@workingcode.com> _______________________________________________ dtrace-discuss mailing list dtrace-discuss@opensolaris.org