head	1.1;
access;
symbols
	RELENG_9:1.1.0.2;
locks; strict;
comment	@# @;


1.1
date	2012.05.12.21.25.48;	author gnn;	state Exp;
branches
	1.1.2.1;
next	;

1.1.2.1
date	2012.05.12.21.25.48;	author svnexp;	state dead;
branches;
next	1.1.2.2;

1.1.2.2
date	2013.06.13.19.01.54;	author svnexp;	state Exp;
branches;
next	;


desc
@@


1.1
log
@SVN rev 235380 on 2012-05-12 21:25:48Z by gnn

Import dtracetoolkit into cddl/contrib
@
text
@Examples - Script demos, screenshots, and how to read the output

   This directory contains an example file per script in the DTraceToolkit.

   When I hear of a new performance tool or what not, the first thing I want
   to see are screenshots. They illustrate,

   	- generally what the tool is for
	- many details and features, since the output is (supposed to be)
	  as intuitive as possible
	- how to use the tool (command line usage)

   It is a rapid way to get a handle on what a tool generally is, and how
   to start using it. The files in this directory serve that purpose.

   These are especially important now that the DTraceToolkit has over 200
   scripts. Flicking through these files and seeing the screenshots may
   be the quickest way to find what you are after.

   Of course, don't forget to read the man pages and notes files too :)

@


1.1.2.1
log
@file Readme was added on branch RELENG_9 on 2013-06-13 19:01:54 +0000
@
text
@d1 21
@


1.1.2.2
log
@## SVN ## Exported commit - http://svnweb.freebsd.org/changeset/base/251697
## SVN ## CVS IS DEPRECATED: http://wiki.freebsd.org/CvsIsDeprecated
@
text
@a0 21
Examples - Script demos, screenshots, and how to read the output

   This directory contains an example file per script in the DTraceToolkit.

   When I hear of a new performance tool or what not, the first thing I want
   to see are screenshots. They illustrate,

   	- generally what the tool is for
	- many details and features, since the output is (supposed to be)
	  as intuitive as possible
	- how to use the tool (command line usage)

   It is a rapid way to get a handle on what a tool generally is, and how
   to start using it. The files in this directory serve that purpose.

   These are especially important now that the DTraceToolkit has over 200
   scripts. Flicking through these files and seeing the screenshots may
   be the quickest way to find what you are after.

   Of course, don't forget to read the man pages and notes files too :)

@


