Lan Barnes wrote: > On Mon, March 5, 2007 11:10 pm, John H. Robinson, IV wrote: >> Ralph Shumaker wrote: >>> Why not run the computers on Universal Time. Local time is only >>> necessary for the people factor, right? >> I know someone that does exactly that. The system time is UTC, and each >> person can individually set their own TZ. I immediately saw the wisdom >> in that, but I don't see my shop changing anytime soon. >> >> -john >> > > I know this is a problem on a dual boot (M$ insists on the clock being > local), but have never had a problem with Linux on GMT in a mixed network. > So that strikes me as ignorance on their part. >
Is everybody clear on whether they are talking about: hardware clock (OS) system clock I have always understood that Windows maintained system clock = hardware clock, regardless of the timezone setting. This may be different these days. (By "maintain", I mean whenever set or synced). On a dual-boot system, therefore, I have always recommended that Linux use a hardware clock set to localtime (one of the installation options). On Linux, the above-mentioned installation setting (on Redhat-relatives, stored in /etc/sysconfig/clock) simply tells what offset to add [sub} when setting system clock from hardware clock [or vice versa]. On my workstation (and any system not dual-booted w/ Windows), I always use hardware clock on UTC, just 'cause it seems simpler. After the system clock is initialized (eg, on boot), the hardware clock has little to do with ongoing time operations. Regards, ..jim -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
