From owner-freebsd-current Tue Apr 14 07:41:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA23830 for freebsd-current-outgoing; Tue, 14 Apr 1998 07:41:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shadow.worldbank.org (shadow.worldbank.org [138.220.104.78]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23814 for ; Tue, 14 Apr 1998 14:41:52 GMT (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.8.8/8.8.8) with SMTP id KAA28272; Tue, 14 Apr 1998 10:38:15 -0400 (EDT) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Tue, 14 Apr 1998 10:38:15 -0400 (EDT) From: "Alok K. Dhir" To: tsprad@set.spradley.tmi.net cc: steve@visint.co.uk, current@FreeBSD.ORG Subject: Re: ps segfaults since I overclocked. and worries. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 14 Apr 1998 tsprad@set.spradley.tmi.net wrote: > I was really surprised by the intense negative reaction to overclocking. > The manufacturer tests the parts an then decides how to mark the parts > based on the results of those tests and other marketing considerations, > like the demand for slower parts and the embarrassment of not having > faster ratings than the competition. The Do-It-Yourselfer tests the > whole system and then decides how fast to run it based on the results of > those tests and other considerations, like the cost of shortening the > life of some parts and the inconvenience of a potential intermittent > failure. What's the big deal? Its not a big deal - until there are problems and you tell "tech support" you're overclocked. Then there's a big deal, because the immediate assumption is to blame the overclocking, and you'll never get past that, even if you un-overclock. If the problem still exists, you're typically told that the overclocking must have caused permanent damage. The moral of the story is "never admit to overclocking when asking for support". :-) Seriously, though, you give up the right to certain things when you overclock. When you run your machine out of spec, you can't be surprised when things start getting screwy, and there's just no easy way to tell what it is that's broken. If you are an overclocker, you need to be prepared to support yourself. -------------------------------------------------------------------- \||/_ Alok K. Dhir Phone: +1.202.473.2446 oo \ S13-069, ISGMC Email: adhir@worldbank.org L_ The World Bank Group Washington, DC \/ ------------------------------------------------------------------------| "Unix _is_ user friendly - it just chooses friends selectively..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message