Date: Thu, 13 Jun 2024 10:34:22 -0400 From: Ed Maste <emaste@freebsd.org> To: "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net> Cc: Bertrand Petit <freebsd-hackers@phoe.frmug.org>, freebsd-hackers@freebsd.org Subject: Re: Removing "CMOS clock set to UTC" question Message-ID: <CAPyFy2DwXpM2K8-1C3Us-2YAw94EQKC1i9RFyuOpyZDXK1A82A@mail.gmail.com> In-Reply-To: <202406131350.45DDobuA044814@gndrsh.dnsmgr.net> References: <CAPyFy2D623nS=8DkXhA8Eg9ZvTW6BJv3sf79Rp13-keY_atT0w@mail.gmail.com> <202406131350.45DDobuA044814@gndrsh.dnsmgr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 13 Jun 2024 at 09:50, Rodney W. Grimes <freebsd-rwg@gndrsh.dnsmgr.net> wrote: > > You could use this data to present a time based on CMOS with and without > the TZ offset and derive the correct wall_cmos_clock value. > > Please try to make things better, not just less confusing. Can you please explain how that is making this better? First, on a brand new install the RTC may be off by several hours or days, or may be correct but for a completely wrong timezone, perhaps where the machine was manufactured. So then we'd have to fist pick a timezone, then ask: Is the current time ( ) 10:31 ( ) 15:31 ( ) Something else If you pick "something else" we need to ask the user for the current time, and then still need to ask them whether the RTC should be set to UTC or local time.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2DwXpM2K8-1C3Us-2YAw94EQKC1i9RFyuOpyZDXK1A82A>