Date: Wed, 12 Jun 2024 13:59:47 -0700 From: Bakul Shah <bakul@iitbombay.org> To: Aryeh Friedman <aryeh.friedman@gmail.com> Cc: Chris <bsd-lists@bsdforge.com>, Mark Delany <x9k@charlie.emu.st>, FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: Removing "CMOS clock set to UTC" question Message-ID: <FDC55DDB-81DF-4EAA-AC56-0FA89BEB6E3F@iitbombay.org> In-Reply-To: <CAGBxaXkZpGNhxBhSVmmK9wyZtUs6aVpPUtmwepO4fWL-cNLGbA@mail.gmail.com> References: <CAPyFy2Bo8Mn=Y9g3ePwMN=YOivgTryGpHC4=qzi%2BnJX3c2h68A@mail.gmail.com> <0.2.0-final-1718212027.814-0x75c1f0@qmda.emu.st> <26eaa45fec5b95b6a00948d45aaea927@bsdforge.com> <CAGBxaXkZpGNhxBhSVmmK9wyZtUs6aVpPUtmwepO4fWL-cNLGbA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jun 12, 2024, at 1:44=E2=80=AFPM, Aryeh Friedman = <aryeh.friedman@gmail.com> wrote: >=20 > 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.... Rather than removing this feature, perhaps the installer should say something like "If you also run windows on this machine, or plan to, set the CMOS clock to Local, else set it to UTC".=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FDC55DDB-81DF-4EAA-AC56-0FA89BEB6E3F>