From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 8 13:30:24 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C4C216A4D5; Thu, 8 Jul 2004 13:30:24 +0000 (GMT) Received: from areandor.numenor.net (areandor.numenor.net [69.55.237.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id 98ED943D62; Thu, 8 Jul 2004 13:30:12 +0000 (GMT) (envelope-from lists-freebsd@silverwraith.com) Received: from [69.55.228.10] (helo=keylime.silverwraith.com) by areandor.numenor.net with esmtp (TLSv1:RC4-SHA:128) (Exim 3.36 #1) id 1BiYyZ-000KAF-00; Thu, 08 Jul 2004 06:30:11 -0700 Received: from keylime ([69.55.228.10] helo=keylime.silverwraith.com) by keylime.silverwraith.com with esmtp (Exim 4.34; FreeBSD) id 1BiUBM-00033O-Qz; Thu, 08 Jul 2004 01:23:05 -0700 Received: (from avleen@localhost)i688N469011741; Thu, 8 Jul 2004 01:23:04 -0700 (PDT) (envelope-from lists-freebsd@silverwraith.com) X-Authentication-Warning: keylime.silverwraith.com: avleen set sender to lists-freebsd@silverwraith.com using -f Date: Thu, 8 Jul 2004 01:23:04 -0700 From: Avleen Vig To: Daniel Ellard Message-ID: <20040708082304.GE5238@silverwraith.com> References: <20040706120130.3DF9816A57D@hub.freebsd.org> <40EB9A46.2050409@trio.plala.or.jp> <20040708034845.GA59801@VARK.homeunix.com> <20040708033741.E28518@bowser.eecs.harvard.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040708033741.E28518@bowser.eecs.harvard.edu> User-Agent: Mutt/1.5.6i X-Spam-Score: -100.0 (---------------------------------------------------) X-Spam-Report: Spam detection software, running on the system "keylime.silverwraith.com", hasmessageblock similar future email. If you have any questions, see the administrator of that system for details.Ellardin most > projects the design phase consumes a lot of time, and it isset cost the > developers a lot of time. So while it might have taken six years to > write DTrace the first time, I suspect it would take a longer than "a few > months" and I'm not going to quibble. We won't know the precise > number until someone does the port.) [...] Content analysis details: (-100.0 points, 5.0 required) pts rule name description -------------------------------------------------- -100 USER_IN_WHITELIST From: address is in the user's white-list cc: freebsd-hackers@FreeBSD.ORG cc: David Schultz Subject: Re: Article on Sun's DTrace X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jul 2004 13:30:24 -0000 On Thu, Jul 08, 2004 at 03:46:24AM -0400, Daniel Ellard wrote: > I don't doubt that DTrace took a long time to do. However, in most > projects the design phase consumes a lot of time, and it is often the > case that unforeseen problems or changes in the feature set cost the > developers a lot of time. So while it might have taken six years to > write DTrace the first time, I suspect it would take a fraction of > that time to re-implement. (It certainly might be longer than "a few > months" and I'm not going to quibble. We won't know the precise > number until someone does the port.) They said "6 staff-years". This means if they have 6 people working on it full time, it took 1 year to complete. If they had 60 people full time, it took just over 5 weeks (technically, i doubt that would work practically). >From speaking to a friend at sun, I do know it took a long time and a lot of effort, and was *not* a simple thing to implement.