Re: Removing "CMOS clock set to UTC" question

On Wed, Jun 12, 2024 at 3:08 PM Chris <bsd-lists@bsdforge.com> wrote:
>
> On 2024-06-12 10:07, Mark Delany wrote:
> > On 12Jun24, Ed Maste apparently wrote:
> >> Our installer asks (via tzsetup):
> >>
> >> > Is this machine's CMOS clock set to UTC?  If it is set to local time,
> >> > or you don't know, please choose NO here!
> >>
> >> I've heard many reports of new users being confused by this question
> >
> > And experienced users too!
> >
> > I've been installing FBSD and various other OSes for decades and whenever I
> > see that
> > question invariable:
> >
> >   a) I have no clue as to what the machine's CMOS clock is set to in the
> > first instance
> >
> >   b) I do not want the hassle of stopping the install to gain access to some
> > obscure BIOS
> >      screen that might or might not give me the answer.
> >
> >   c) I have no clue as to the implications of answering this question one
> > way or the
> >      other.
> >
> >   d) I don't know whether it's a good idea or not to change the CMOS clock
> > to UTC if it's
> >      not the case. Is it?
> >
> >   e) I don't think I've ever seen a similar question asked by any other OS
> > install.
> >
> > At the very least the message should indicate what happens if you get the
> > answer
> > wrong. Does the system fail to install, does the clock run backwards, will
> > my dog stop
> > barking? What?
>
> "If you are unsure, or don't know the answer here. Select NO"
> Seems intuitive enough.
> IOW no harm done here, if you choose NO (selects localtime). :)
> Personally, I don't have a strong BIAS here, except that it's always been
> this
> way, and I don't have to remember to set it post installation. So it seems
> "convenient".

In a dual (or more) boot config it is *NOT* more convenient because
some OS's like Window$ just assume that it is set to local time and if
you set it to UTC on FreeBSD you will need to always sync on reboot
(to different OS) or be 5 hrs off (EDT/NYC).... in the 3 years of
having my machine being dual boot and even after reinstalling FreeBSD
(my primary OS) on a brand new drive (old one died) I still have this
issue... lucky FreeBSD has ntpdate at boot but Window$ doesn't....
from what I have seen Linux also does this (or at least when I run the
Linux partition under bhyve it does)


-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org