From owner-freebsd-current@FreeBSD.ORG  Thu Sep 18 21:34:29 2008
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 8D526106567D;
	Thu, 18 Sep 2008 21:34:29 +0000 (UTC)
	(envelope-from jb@what-creek.com)
Received: from what-creek.com (what-creek.com [66.111.37.70])
	by mx1.freebsd.org (Postfix) with ESMTP id 6B45B8FC14;
	Thu, 18 Sep 2008 21:34:24 +0000 (UTC)
	(envelope-from jb@what-creek.com)
Received: by what-creek.com (Postfix, from userid 102)
	id 9E1A67416E; Thu, 18 Sep 2008 21:16:52 +0000 (GMT)
Date: Thu, 18 Sep 2008 21:16:52 +0000
From: John Birrell <jb@what-creek.com>
To: Roman Divacky <rdivacky@freebsd.org>
Message-ID: <20080918211652.GB19958@what-creek.com>
References: <20080917101013.GA90749@freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20080917101013.GA90749@freebsd.org>
User-Agent: Mutt/1.4.2.3i
Cc: jb@freebsd.org, current@freebsd.org
Subject: Re: dtrace status
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Sep 2008 21:34:29 -0000

On Wed, Sep 17, 2008 at 12:10:13PM +0200, Roman Divacky wrote:
> Dtrace was commited 3 months ago and the only things that prevents
> using it "out of the box" is building kernel with WITH_CTF=1.
> 
> When is this going to be enabled on default. What is preventing this
> from happening? 

I wonder whether people generally want it enabled by default.

--
John Birrell