On Thu, 08 Aug 2019 23:36:48 -0600 "Theo de Raadt" <[email protected]> wrote: > YASUOKA Masahiko <[email protected]> wrote: >> On Wed, 7 Aug 2019 21:41:17 -0500 >> Scott Cheloha <[email protected]> wrote: >> > Drop config(8) support for getting/setting the kernel timezone. >> >> I'm using this. Is there any alternative or discussion? >> >> I think PCs are still shipped with their firmware configured to the >> local time. > > How are you using this? > > By deactivating KARL I assume? That's a pretty bad tradeoff.
Currently I rewrote /usr/libexec/reorder_kernel manually. --- /usr/libexec/reorder_kernel.orig Sat Jul 6 18:20:04 2019 +++ /usr/libexec/reorder_kernel Sat Jul 6 18:18:23 2019 @@ -63,6 +63,13 @@ fi cd $KERNEL_DIR/$KERNEL make newbsd + +cat <<EOT | config -ef bsd +disable ims* +t -540 +q +EOT + make newinstall echo "\nKernel has been relinked and is active on next reboot.\n" Finding alternative way is todo. But it remains long term... > My view is that localtime-offset of a PC doesn't matter unless you run > another operating system, and frankly why has that become our problem > instead of their problem? Above diff is for my laptop PC. As another use case, my company has some PC servers as a stock which are commonly used for some services. Some services use OpenBSD, others use Linux. If OpenBSD cannot use the clock as local time, we need to change the clock setting and ask Linux team to use the clock as UTC. Of course it's possible, but I'd like to show you the matter. > To my amusement this supporting code was added on January 8, 2000. --yasuoka
