From owner-freebsd-hackers Fri Mar 15 23:37:16 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from services.webwarrior.net (overlord-host99.dsl.visi.com [209.98.86.99]) by hub.freebsd.org (Postfix) with ESMTP id E512137B416 for ; Fri, 15 Mar 2002 23:37:08 -0800 (PST) Received: from twincat.vladsempire.net (hutch-662.hutchtel.net [206.10.68.190]) by services.webwarrior.net (Postfix) with ESMTP id 743B63ED for ; Sat, 16 Mar 2002 01:37:07 -0600 (CST) Received: by twincat.vladsempire.net (Postfix, from userid 1001) id 7E14F3899; Sat, 16 Mar 2002 01:37:54 +0000 (GMT) Date: Sat, 16 Mar 2002 01:37:53 +0000 From: Josh Paetzel To: Terry Lambert Cc: Josh Paetzel , Matthew Emmerton , hackers@FreeBSD.ORG Subject: Re: Interesting sysctl variables in Mac OS X with hw info Message-ID: <20020316013753.A290@twincat.vladsempire.net> References: <006601c1cb06$b9f07370$1200a8c0@gsicomp.on.ca> <3C902B36.4D4EB8E@mindspring.com> <20020315100853.P287@twincat.vladsempire.net> <3C923D0A.2259D49F@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3C923D0A.2259D49F@mindspring.com>; from tlambert2@mindspring.com on Fri, Mar 15, 2002 at 10:27:22AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Mar 15, 2002 at 10:27:22AM -0800, Terry Lambert wrote: > Josh Paetzel wrote: > > This is a perfect example of, "Just because you can do something, > > doesn't mean you should." > > > > I wouldn't see anything wrong with grabbing the clock frequency of the > > first cpu in the system and noting in the man page that if you have > > multiple cpus and you aren't running them at the same frequency, then > > the reported value is applicable only to the first cpu. > > > > This would save a ton of time in implementing Jordan's ideas, at the > > cost of not being able to deal correctlywith a situation that > > (hopefully) isn't too common in the field. The other less tangible > > disadvantage to my suggestion is that it takes us one step further in our > > single-cpu-centric userland, ala top, uptime, and so forth only > > displaying stats for "one" cpu. > > Incorrect information is always worse than no information. > > -- Terry Yeah, you're right. Six hours of contemplation and I've changed my tune. If it's going to be done, should be done right. Josh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message