Date: Thu, 13 Jun 2024 11:32:10 -0400 From: Ed Maste <emaste@freebsd.org> To: Tomoaki AOKI <junchoon@dec.sakura.ne.jp> Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: Removing "CMOS clock set to UTC" question Message-ID: <CAPyFy2Ab1Sm7B7cnhHiPCwftOOZBj58249TFjPK8%2B6XGuq6sPA@mail.gmail.com> In-Reply-To: <20240613075137.c734a227e578996013d3bcc7@dec.sakura.ne.jp> References: <CAPyFy2Bo8Mn=Y9g3ePwMN=YOivgTryGpHC4=qzi%2BnJX3c2h68A@mail.gmail.com> <20240613075137.c734a227e578996013d3bcc7@dec.sakura.ne.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 12 Jun 2024 at 18:51, Tomoaki AOKI <junchoon@dec.sakura.ne.jp> wrote: > > tzsetup(8) manpage is a bit confusing. > Does `tzsetup -s` create /etc/wall_cmos_clock when it's not exist and > selected timezone is NOT UTC? No, with -s tzsetup neither creates nor removes /etc/wall_cmos_clock. I've created https://reviews.freebsd.org/D45576 to clarify this in tzsetup(8) and would appreciate review. > Unfortunately, most of computers used by end-users (personal or > corporate) would running Windows. Does emulated CMOS clocks on VMware, > virtualBox and/or something else on Windows shows always UTC, or wall > CMOS clock same as host Windows? For the last 10 years we've skipped this question when running in a VM: commit e91afc1cda50cbcb8fffa3f52cc0f8c595a392a3 Author: Devin Teske <dteske@FreeBSD.org> Date: Tue Nov 11 19:37:17 2014 +0000 Default `bsdconfig timezone' and `tzsetup' to `-s' in a VM. Recommended by: cperciva Reviewed by: cperciva Relnotes: tzsetup and bsdconfig now assume that the "hardware" clock inside a VM is set to UTC VirtualBox has an option to indicate that the RTC stores UTC time, I assume others do as well. There's a VirtIO RTC interface that provides (among others) a UTC clock.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2Ab1Sm7B7cnhHiPCwftOOZBj58249TFjPK8%2B6XGuq6sPA>