From owner-freebsd-doc@FreeBSD.ORG Thu Jul 5 12:42:06 2012 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5C81A106566B; Thu, 5 Jul 2012 12:42:06 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 1762F8FC16; Thu, 5 Jul 2012 12:42:06 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id q65Cg3oC029373; Thu, 5 Jul 2012 06:42:03 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id q65Cg3K1029370; Thu, 5 Jul 2012 06:42:03 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Thu, 5 Jul 2012 06:42:03 -0600 (MDT) From: Warren Block To: Benjamin Kaduk In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Thu, 05 Jul 2012 06:42:03 -0600 (MDT) Cc: doc@freebsd.org Subject: Re: Handbook update: HorizSync and VertRefresh X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jul 2012 12:42:06 -0000 On Thu, 5 Jul 2012, Benjamin Kaduk wrote: > On Tue, 3 Jul 2012, Warren Block wrote: > >> On Wed, 4 Jul 2012, Benjamin Kaduk wrote: >> >>> One does hear the occasional tale of a CRT which exploded when the wrong >>> frequencies were configured ... it might be worth mentioning that guessing >>> values could lead to hardware damage. >> >> It's such a rare situation that I'm hesitant to mention it. This might >> be better: >> >> Most monitors support sync frequency autodetection, making >> manual entry of these values unnecessary. For the few >> monitors that do not support autodetection, avoid potential >> damage by only entering values provided by the manufacturer. > > Fine by me -- thanks. Committed with this and a few other minor wording revisions. Thanks!