From owner-freebsd-current Tue Apr 14 07:14:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA19073 for freebsd-current-outgoing; Tue, 14 Apr 1998 07:14:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from set.spradley.tmi.net (set.spradley.tmi.net [207.170.107.99]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA19067 for ; Tue, 14 Apr 1998 14:14:38 GMT (envelope-from tsprad@set.spradley.tmi.net) Received: from localhost (set.spradley.tmi.net) [127.0.0.1] by set.spradley.tmi.net with esmtp (Exim 1.82 #2) id 0yP6Tf-0003SQ-00; Tue, 14 Apr 1998 09:14:23 -0500 X-Mailer: exmh version 2.0zeta 7/24/97 To: Stephen Roome Cc: current@FreeBSD.ORG Subject: Re: ps segfaults since I overclocked. and worries. In-reply-to: Your message of "Tue, 14 Apr 1998 03:46:32 BST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 14 Apr 1998 09:14:23 -0500 From: Ted Spradley Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I see your point. Someone replied earlier with the incredibly sensible > suggestion that I should recompile my ps binary. Worked a treat! So, the > hardware was fine after all, I'd just not got the software in proper > order. Wasn't kidding anyone, I just hadn't made myself clear. I hope I wasn't the only one who suggested that. If everything else works, then the problem is probably with the thing that doesn't work, the ps command. Seems to me like an obvious place to look. 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? Last I heard, even wcarchive.cdrom.com is overclocked. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message