From nobody Thu Jun 13 14:34:22 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 4W0Q0W55F8z5NmRZ for ; Thu, 13 Jun 2024 14:34:35 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-io1-f53.google.com (mail-io1-f53.google.com [209.85.166.53]) (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 4W0Q0W376cz4Gn7 for ; Thu, 13 Jun 2024 14:34:35 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-io1-f53.google.com with SMTP id ca18e2360f4ac-7e25bf84b58so40024239f.0 for ; Thu, 13 Jun 2024 07:34:35 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718289274; x=1718894074; 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=WW1d+QV3VhNwN3c/ddDOxpr0MMhgZMFmDaIVX+c013c=; b=p/PFkuCC835vWFzwAso6PzdvuVpquqBcuZmbREwzZDO1FkYAp/Cuo0TQh/maG3jg3+ cCOvNWjrsc78vw97eJW7Nr+3yO32ZAUM/yIQdAfTRWLnRjjR5YIAPX3QFTJoSZUVo2b4 f9HsnCKuMHh28+Ma8NLgLTm7V9ygR73rkQ4tkCl8fb4yf9zj1XTmQ8dfGZ/m+6HES10T wDw4HWrxduOf95bPRcQ69qubrL2VoMdENU7RhTRMAVDLRj2ZXqfDEemg0OeqDgeK+oxA Pb7Ozdk+JdVbBqlETj218l0AEOiXIhIisiOvNxtjYSxYX0s76HQDGUbvzBGeVcrYAet2 k3+A== X-Forwarded-Encrypted: i=1; AJvYcCWEzvlkQ2qXl8jdG0IUvqrlzBVn/KjCi90bfCdn32lS6bPRIMD55whMC+x/GvX107Ij3ZaD8rm+IDU+pq8k+x4nVPK5lXjD8AC3lEY= X-Gm-Message-State: AOJu0YwCx/BxyfC//zmWCnA5zJZUECyCIu9NjEpUjdviX8I3IC1JT/+F S8zpKjMUs9ensLn6vmfHyISrwDxiqx5XKGFmXDsrJ6ncvCVvsZfHETRtmDpx7DnhyVAWUQgOksf eF5EzaXe0rSiz56YzI2ZpNBbi+mT45w== X-Google-Smtp-Source: AGHT+IE2XpBIQyuc7NxqpG817MOcz9SFh+t1R2rvOb6lbwVg+Jq/B1lqaE2iSByKtxcIpobWLAPHeFm4SCHfy9F/xfw= X-Received: by 2002:a05:6602:2c88:b0:7ea:fc3a:fff6 with SMTP id ca18e2360f4ac-7ebcd0b6c3bmr580308139f.6.1718289273748; Thu, 13 Jun 2024 07:34:33 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@FreeBSD.org MIME-Version: 1.0 References: <202406131350.45DDobuA044814@gndrsh.dnsmgr.net> In-Reply-To: <202406131350.45DDobuA044814@gndrsh.dnsmgr.net> From: Ed Maste Date: Thu, 13 Jun 2024 10:34:22 -0400 Message-ID: Subject: Re: Removing "CMOS clock set to UTC" question To: "Rodney W. Grimes" Cc: Bertrand Petit , 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: 4W0Q0W376cz4Gn7 On Thu, 13 Jun 2024 at 09:50, Rodney W. Grimes 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.