From nobody Thu Jun 13 15:32:10 2024
X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
	by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4W0RHD4sXrz5Ns34
	for <freebsd-hackers@mlmmj.nyi.freebsd.org>; Thu, 13 Jun 2024 15:32:24 +0000 (UTC)
	(envelope-from carpeddiem@gmail.com)
Received: from mail-il1-f177.google.com (mail-il1-f177.google.com [209.85.166.177])
	(using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)
	 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256
	 client-signature RSA-PSS (2048 bits) client-digest SHA256)
	(Client CN "smtp.gmail.com", Issuer "WR4" (verified OK))
	by mx1.freebsd.org (Postfix) with ESMTPS id 4W0RHD0pvfz4P24
	for <freebsd-hackers@freebsd.org>; Thu, 13 Jun 2024 15:32:24 +0000 (UTC)
	(envelope-from carpeddiem@gmail.com)
Authentication-Results: mx1.freebsd.org;
	none
Received: by mail-il1-f177.google.com with SMTP id e9e14a558f8ab-3758fdbd2daso4235005ab.3
        for <freebsd-hackers@freebsd.org>; Thu, 13 Jun 2024 08:32:24 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20230601; t=1718292743; x=1718897543;
        h=cc:to:subject:message-id:date:from:in-reply-to:references
         :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id
         :reply-to;
        bh=6XiUaYnJIwCQF+uwS+3zyvq0irAlCNSvIfhgUtGqcnQ=;
        b=Z06h5tvwjWqSvIiuKYOA7i7opyYFz7UxK5YDJkrc8ophc8Eik9g+vwQp/PfHE/3qha
         14tgXIeASOa+7iSJIaE60Qw1+vlV+INGn/LzyvN9lCEJToXH60Ku4gGma3h9V72suDjU
         0Ya4mNw3/r7xEKO8mJCEwVfsFU6TnpphP5zmBnUFqko6AUR97b6A+7qV9ZYIgwLwBinc
         F1/5dMTa60ZyMTKP68d1iFS8jOpGr5Lu9sqFfqstC+m2uDOwB+w3QYLAQQmzpqCkwhoH
         ptMMFP5v+PX5jUF6xqtShoGRHrLRh/lhTelOTe4CvMucjhAjGZVZrxxNc2S8vO+gpoac
         zWwg==
X-Gm-Message-State: AOJu0Yy3KsT7YZSx0jdjTlU4hgfSvUuOFmBvwXFdP/VZ3qZr5FKQ2vhZ
	FCqq5Q64pFIXHJoWh5WKedIH3Rzp6o4EXItrnsQIkUwS6b9gjHvJjmqtrYp2QDZQwSxQxnY7Bgv
	83deAZX/CESp6GzrsgSiVqqFNNJTxm/rz
X-Google-Smtp-Source: AGHT+IHMow6YgXizeIQJuAfVd4+lfYUTg3CN2c4oT7ZV1Dp6d+19p5uaof6+eD0YSiWI3M4aRObsIGMOGOvatasMceU=
X-Received: by 2002:a05:6e02:138e:b0:375:a3d8:97be with SMTP id
 e9e14a558f8ab-375cd16a30bmr51156305ab.9.1718292742671; Thu, 13 Jun 2024
 08:32:22 -0700 (PDT)
List-Id: Technical discussions relating to FreeBSD <freebsd-hackers.freebsd.org>
List-Archive: https://lists.freebsd.org/archives/freebsd-hackers
List-Help: <mailto:freebsd-hackers+help@freebsd.org>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Subscribe: <mailto:freebsd-hackers+subscribe@freebsd.org>
List-Unsubscribe: <mailto:freebsd-hackers+unsubscribe@freebsd.org>
Sender: owner-freebsd-hackers@FreeBSD.org
MIME-Version: 1.0
References: <CAPyFy2Bo8Mn=Y9g3ePwMN=YOivgTryGpHC4=qzi+nJX3c2h68A@mail.gmail.com>
 <20240613075137.c734a227e578996013d3bcc7@dec.sakura.ne.jp>
In-Reply-To: <20240613075137.c734a227e578996013d3bcc7@dec.sakura.ne.jp>
From: Ed Maste <emaste@freebsd.org>
Date: Thu, 13 Jun 2024 11:32:10 -0400
Message-ID: <CAPyFy2Ab1Sm7B7cnhHiPCwftOOZBj58249TFjPK8+6XGuq6sPA@mail.gmail.com>
Subject: Re: Removing "CMOS clock set to UTC" question
To: Tomoaki AOKI <junchoon@dec.sakura.ne.jp>
Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org>
Content-Type: text/plain; charset="UTF-8"
X-Spamd-Bar: ----
X-Rspamd-Pre-Result: action=no action;
	module=replies;
	Message is reply to one we originated
X-Spamd-Result: default: False [-4.00 / 15.00];
	REPLY(-4.00)[];
	ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]
X-Rspamd-Queue-Id: 4W0RHD0pvfz4P24

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.