From owner-freebsd-hackers@freebsd.org Tue Jan 5 22:21:44 2021 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B61DE4CDDA3 for ; Tue, 5 Jan 2021 22:21:44 +0000 (UTC) (envelope-from se@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4D9Rmm4dYPz3QY7; Tue, 5 Jan 2021 22:21:44 +0000 (UTC) (envelope-from se@freebsd.org) Received: from Stefans-MBP-WLAN.fritz.box (p200300cd5f110800e50b83eaa3464b63.dip0.t-ipconnect.de [IPv6:2003:cd:5f11:800:e50b:83ea:a346:4b63]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: se/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id E857C2BAC; Tue, 5 Jan 2021 22:21:43 +0000 (UTC) (envelope-from se@freebsd.org) To: Warner Losh Cc: FreeBSD Hackers , Hal Murray References: <20210105075109.A412C40605C@ip-64-139-1-69.sjc.megapath.net> <4e6721bc-e593-76b6-90f8-03d96486dc28@freebsd.org> <47c37f75-e082-7a34-7eb6-3ee2a4ade395@freebsd.org> From: Stefan Esser Subject: Re: How does the time zone info get updated? Message-ID: <02ebd386-a7fd-1816-72b6-3211f4bc69fb@freebsd.org> Date: Tue, 5 Jan 2021 23:21:42 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="m3NxzA46hr9WDhHEyA2DiAy5T5gtO34iz" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jan 2021 22:21:44 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --m3NxzA46hr9WDhHEyA2DiAy5T5gtO34iz Content-Type: multipart/mixed; boundary="5G05ioXAqikIrfWoJqbjgYDbXZSrpJnFa"; protected-headers="v1" From: Stefan Esser To: Warner Losh Cc: FreeBSD Hackers , Hal Murray Message-ID: <02ebd386-a7fd-1816-72b6-3211f4bc69fb@freebsd.org> Subject: Re: How does the time zone info get updated? References: <20210105075109.A412C40605C@ip-64-139-1-69.sjc.megapath.net> <4e6721bc-e593-76b6-90f8-03d96486dc28@freebsd.org> <47c37f75-e082-7a34-7eb6-3ee2a4ade395@freebsd.org> In-Reply-To: --5G05ioXAqikIrfWoJqbjgYDbXZSrpJnFa Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: quoted-printable Am 05.01.21 um 21:36 schrieb Warner Losh: > On Tue, Jan 5, 2021 at 12:51 PM Stefan Esser > wrote: [...] > Yes, if only the leap-seconds are required, this helps get the time= > synchronized - but is quite different from timezone file updates. >=20 > > So no TZ update outside an os upgrade, but the leap seconds file= > updates > > at the speed of NIST... >=20 > The OP did not ask for leap-second updates but for timezone files, > if I understand his mail correctly. >=20 > Yes. But I know him from another list I'm on and knew the back story.=20 > How does FreeBSD know about leap seconds and what mechanism does it use= =20 > to keep up to date was the topic there. Well, then you answered the question sent to the other list, which I have not seen and did not know about this context ... But Ed Maste has meanwhile answered the question he asked on this list (as far as I understand it): -> "freebsd-update" applies the timezone changes and EN notes are sent out to notify users of the availability of this update. And release users should follow-up on EN notes anyway and thus should not miss the timezone updates. Regards, STefan --5G05ioXAqikIrfWoJqbjgYDbXZSrpJnFa-- --m3NxzA46hr9WDhHEyA2DiAy5T5gtO34iz Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsB5BAABCAAjFiEEo3HqZZwL7MgrcVMTR+u171r99UQFAl/05nYFAwAAAAAACgkQR+u171r99URg Wgf+KlxjRQBoCOsZ+ljkB7KBwzOcTAMkssd4rgnX0yda1zvtqvib09+6923upZylM3iNxJKTIxSG BIV3iZYoixDzUAkexIjZ+24/lUH+BKi9/wR5QNmbeQAJrpJpPluhTEKSUt2/2ikPi5Ti0IYsD2pX aPJXHN0awPbE8JM9fGboiDSjWPUz0Xq3l9Yaw0qtClIUu3RIBtiSVCNpwH69ixJyyWSIXpvLbMxg YqMz/hEgpM7gsKBvo3OXYUaK2T78A4ZJLRtB3PJtqylKDY2WZVC0o9y4FjjAK+lwugwKYkPE+TDi p+aji52HLJzjFqyOL3TCC5UDXMV3BnvBOpq5SNJpgA== =slDA -----END PGP SIGNATURE----- --m3NxzA46hr9WDhHEyA2DiAy5T5gtO34iz--