From owner-freebsd-current@FreeBSD.ORG Tue Feb 3 12:21:54 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 224543B0 for ; Tue, 3 Feb 2015 12:21:54 +0000 (UTC) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D0CBD31F for ; Tue, 3 Feb 2015 12:21:53 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.84 (FreeBSD)) (envelope-from ) id 1YIcUH-000A3u-M5; Tue, 03 Feb 2015 15:21:49 +0300 Date: Tue, 3 Feb 2015 15:21:49 +0300 From: Slawa Olhovchenkov To: Paul Koch Subject: Re: tzsetup - UTC user question Message-ID: <20150203122149.GA29901@zxy.spb.ru> References: <20150203150838.5bcde9a9@akips.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150203150838.5bcde9a9@akips.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Feb 2015 12:21:54 -0000 On Tue, Feb 03, 2015 at 03:08:38PM +1000, Paul Koch wrote: > > Since the default option for "Select local or UTC clock" changed from > "No" to "Yes", we are seeing many customers who incorrectly answer this > question! > > This screws up things in our app because we store all data in UTC. > > A few observations... > > Most people don't know what "CMOS clock" is. Maybe change the wording > to "BIOS clock" or "Hardware Clock" ?? > > The person doing the install may not know what the clock is currently set > to, especially when installing in a VM. Perhaps the screen should display > the current machine time so they can correctly answer the question. > > Why was the default changed from "No" to "Yes" ? or change ntpd_sync_on_start="YES" to force correct time. in most case for hardware platform CMOS time contains garbage.