From owner-freebsd-current@FreeBSD.ORG Wed Nov 29 18:43:04 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E27CF16A52D for ; Wed, 29 Nov 2006 18:43:04 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id 92DB143CA3 for ; Wed, 29 Nov 2006 18:43:00 +0000 (GMT) (envelope-from kip.macy@gmail.com) Received: by ug-out-1314.google.com with SMTP id o2so1706337uge for ; Wed, 29 Nov 2006 10:43:02 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=kqjOPNfM10dvTIHd01r5+YIKG/vAvZoIqK3Xc1Z2Rp9kpwPsFbj+tZ25VTkxE3n1YBueVx4MjX6r8zp7kpxUO5cKr8JyjI/V5LaVCgfAn6ey4V4cDeLWyWWIBcdYR0prXRD5EVcqL7/gCwaZ5s+FWUyMx2+1o/HHWgoeGW6YP/4= Received: by 10.82.101.3 with SMTP id y3mr649627bub.1164825781399; Wed, 29 Nov 2006 10:43:01 -0800 (PST) Received: by 10.82.191.20 with HTTP; Wed, 29 Nov 2006 10:43:01 -0800 (PST) Message-ID: Date: Wed, 29 Nov 2006 10:43:01 -0800 From: "Kip Macy" To: "John Baldwin" In-Reply-To: <200611291210.39449.jhb@freebsd.org> MIME-Version: 1.0 References: <2b22951e0611212109t69b01400q5eb0ba15b028ce68@mail.gmail.com> <20061123213659.GA8405@localhost.localdomain> <20061123215851.GA56442@what-creek.com> <200611291210.39449.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current@freebsd.org Subject: Re: KDTRACE is gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Nov 2006 18:43:05 -0000 I definitely don't agree with jb@ that this is grounds for not committing dtrace support. However, his point that the value of dtrace is greatly diminished if the user has to actively anticipate a need for it and then compile a custom kernel is valid. Developers are just a little too comfortable with the notion of "oh, just tell the user to add FOO to his config and compile a new kernel!". -Kip On 11/29/06, John Baldwin wrote: > > On Thursday 23 November 2006 16:58, John Birrell wrote: > > On Thu, Nov 23, 2006 at 10:36:59PM +0100, Stanislaw Halik wrote: > > > Why isn't importing it as a non-default option acceptable? I believe a > > > lot of users would be happy to include it in their custom kernels. > > > > Because in 5 years time when there is a production server that > > can't be rebooted, I want the admins to be able to run DTrace. > > The only way I can guarantee that is by making the ability to > > load DTrace kernel modules available to everyone. > > > > DTrace isn't intended as a toy. > > Not having it in GENERIC doesn't mean that. :) We have a lot of machines > at > work and none of them run GENERIC, but a custom kernel config. We would > just > add the option to the kernel (just like now we statically compile in > things > like COMPAT_LINUX which aren't in GENERIC). I think this fear is perhaps > a > little inflated relative to reality. > > -- > John Baldwin > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >