dtrace discuss - Oct 2006 - DTrace Feature set

Hi All,

Can someone help me in getting info about specific dtrace features introduced in
individual S10 updates like U1,U2,U3 etc...
 
 
This message posted from opensolaris.org

Narain wrote:
> Hi All,
>
> Can someone help me in getting info about specific dtrace features
introduced in individual S10 updates like U1,U2,U3 etc...
>   
If any functionality/features were added they should be in the
"What''s
New" document in the Release Collection for each update.

Thanks,

-- 
Derek E. Lewis
delewis at acm.org
http://riemann.solnetworks.net/~dlewis

Emphasis on the "should be".  If you look through the "Solaris 10
What''s
New", you''ll see some discussion about DTrace, but it''s
not very
specific.  For example, "strstr()" is in 6/06, but not in 3/05. 
There''s
no mention of that or any other additional functions in the
"What''s New".

I''ve been thinking about adding a section for this to the DTrace FAQ 
(http://www.genunix.org/wiki/index.php/DTrace_FAQ), in my copious spare 
time,  ;-)  but I''m not sure what was added when.

But I''ll tell you what.  If others would be willing to send me
what''s
been added and what release it was added, I''d be willing to act as 
consolidator and add it to the web site.

Chip

Derek E. Lewis wrote:
> Narain wrote:
>> Hi All,
>>
>> Can someone help me in getting info about specific dtrace features 
>> introduced in individual S10 updates like U1,U2,U3 etc...
>>   
> If any functionality/features were added they should be in the
"What''s
> New" document in the Release Collection for each update.
>
> Thanks,
>

Chip Bennett wrote:
> I''ve been thinking about adding a section for this to the DTrace
FAQ
> (http://www.genunix.org/wiki/index.php/DTrace_FAQ), in my copious 
> spare time,  ;-)  but I''m not sure what was added when.
I think any behavioral changes or feature additions present in DTrace 
that are implemented in future Solaris versions should be quantified and 
explained in some manner by way of official documentation. Adding a 
section to the "Dynamic Tracing Guide" that does this for each Solaris
release would be adequate, but that in itself is not really an 
OpenSolaris issue as much as it is an issue with Sun''s
OpenSolaris-based
distribution, Solaris.

Having a community Wiki page to clarify these changes and feature 
additions sounds like the best route to cover the entire OpenSolaris 
community and not just Solaris users.

-- 
Derek E. Lewis
delewis at acm.org
http://riemann.solnetworks.net/~dlewis

Derek E. Lewis wrote:
> I think any behavioral changes or feature additions present in DTrace 
> that are implemented in future Solaris versions should be quantified 
> and explained in some manner by way of official documentation. Adding 
> a section to the "Dynamic Tracing Guide" that does this for each 
> Solaris release would be adequate, but that in itself is not really an 
> OpenSolaris issue as much as it is an issue with Sun''s 
> OpenSolaris-based distribution, Solaris.
>
> Having a community Wiki page to clarify these changes and feature 
> additions sounds like the best route to cover the entire OpenSolaris 
> community and not just Solaris users.
>
If you''re just saying a community FAQ should included both worlds, I 
agree.  But if you''re saying we shouldn''t try to document
official Sun
release information, just because it doesn''t really belong in a 
community FAQ, I would disagree.  Until Sun catches up, we should try to 
reduce the confusion, if we can.

Chip

Chip Bennett wrote:
> If you''re just saying a community FAQ should included both worlds,
I
> agree.  
Yes, this is exactly what I meant. The question is what should we use as 
a source of information other than experimentation to determine 
functionality/feature variations between Solaris/DTrace releases?

-- 
Derek E. Lewis
delewis at acm.org
http://riemann.solnetworks.net/~dlewis