Date: Wed, 29 Nov 2006 12:10:39 -0500 From: John Baldwin <jhb@freebsd.org> To: freebsd-current@freebsd.org Cc: John Birrell <jb@what-creek.com> Subject: Re: KDTRACE is gone? Message-ID: <200611291210.39449.jhb@freebsd.org> In-Reply-To: <20061123215851.GA56442@what-creek.com> References: <2b22951e0611212109t69b01400q5eb0ba15b028ce68@mail.gmail.com> <20061123213659.GA8405@localhost.localdomain> <20061123215851.GA56442@what-creek.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200611291210.39449.jhb>