From nobody Wed Jun 12 23:42:12 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 4W02C60BCNz5L0KP for <freebsd-hackers@mlmmj.nyi.freebsd.org>; Wed, 12 Jun 2024 23:42:26 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-io1-f41.google.com (mail-io1-f41.google.com [209.85.166.41]) (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 4W02C55d0sz4dx3 for <freebsd-hackers@freebsd.org>; Wed, 12 Jun 2024 23:42:25 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-io1-f41.google.com with SMTP id ca18e2360f4ac-7eb85e80661so14229039f.1 for <freebsd-hackers@freebsd.org>; Wed, 12 Jun 2024 16:42:25 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718235744; x=1718840544; 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=E7pelQ5flk3S1aGfj18W49uT+JNjjBOKd61iLSeLo9g=; b=l7v6aYlBNEXX3p28KR+XH9xnI7J0ZacXrFA6eVCZvyboYz8gfvp9tD79kHHeIRrS1r G9I8tXeQJXP/C0LhYXvHGV1bZkoy6SbGga3sJIBo3n2ZJJmFYLI8JbxqiZqTM+Q2I/U1 vlu1XOZWxrORua8EY/gX3gRiGONuUXxdqIScoN6dG7XHCAydeJGm+1gwZTMQXZ1S6uba l+PgL6LEiBnUgGzLdQJmlrdgYomSDIoTkrVHUeBrraBVOC0eKROEaX65KcIssbR7NbYZ CZ4kwvsgPomcaZFo8mPAudSxaYpYJqIQlIy3KmjjLNglfTluEWtMZn1KOTqfLFCO0UQo G+/Q== X-Gm-Message-State: AOJu0YwEtwZXCyEKzSVHAFHil09IikZDrMPvP6/K3Gf6DDM9QBREZYcO FMid0waCdqB43l03NmRxae/ZMy2cNHxoKnsjV0+By/q4axL2xVWGXepbSoo5xlgNtrkbNWpcsJ9 CtbCU1/1RUQXmtUSuMiW8YTorEGI= X-Google-Smtp-Source: AGHT+IGF6f9kvQcWyaeaCC/Qu0MK4wblpmUO4YhZ4jXzt+enN6zPiehwpuWvqLw9VG5g9PoOFoWRoyKHg40r/MIpWmM= X-Received: by 2002:a05:6602:3f86:b0:7eb:cba1:b19e with SMTP id ca18e2360f4ac-7ebcd0e4efbmr420273139f.8.1718235743965; Wed, 12 Jun 2024 16:42:23 -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> <0.2.0-final-1718212027.814-0x75c1f0@qmda.emu.st> <26eaa45fec5b95b6a00948d45aaea927@bsdforge.com> <CAGBxaXkZpGNhxBhSVmmK9wyZtUs6aVpPUtmwepO4fWL-cNLGbA@mail.gmail.com> <20240612211337.GZ2052@memo2.memo.frmug.org> In-Reply-To: <20240612211337.GZ2052@memo2.memo.frmug.org> From: Ed Maste <emaste@freebsd.org> Date: Wed, 12 Jun 2024 19:42:12 -0400 Message-ID: <CAPyFy2D623nS=8DkXhA8Eg9ZvTW6BJv3sf79Rp13-keY_atT0w@mail.gmail.com> Subject: Re: Removing "CMOS clock set to UTC" question To: Bertrand Petit <freebsd-hackers@phoe.frmug.org> Cc: 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: 4W02C55d0sz4dx3 On Wed, 12 Jun 2024 at 17:14, Bertrand Petit <freebsd-hackers@phoe.frmug.org> wrote: > > > It is sad to see an option removed because "it confuse users". It's not only that it's confusing, it's that there is not much value in asking the question. > I agree > it is broken so we need to fix it: we should make the option's effect obvious > so that anyone can understand it. I porpose that in place of asking for a UTC > or local selection we query "what time is it?" instead. Two choices would be > presented as (live) timestamps, each simultaneously showing the effect of > UTC/local time CMOS setting would have later on the host's wall clock. The > task of the user is to select the option matching any external reference he > sees fit. This is not the point of the question though -- once we have a timezone selected and the answer to the UTC question the installer prompts for the user to set the time; it doesn't really matter what it was before.. Despite being exactly what the question asks, it isn't really important whether the CMOS clock is currently set to UTC or local time. What the installer needs to know is whether the user wants the real-time CMOS clock to contain UTC or local time.