Actually, my problems w/ the DST issue comes from having my thinkpad do
multiboot; If I've got a machine dedicated to Linux I'm able to tell it to
keep the NVRAM's TOD clock in UTC (which will never be shifted).
The problem arises because M$'s Windoze wants the clock to be the local
time, so it changes the CMOS clock when the time change occurs (well, it
asks you to confirm the change at the next boot). Linux, even when it's
using local time, will adapt directly but WILL NOT make the CMOS clock jump
the 60 minutes (+/-) so you'll get an odd clock setting _after_ you reboot.
I tend to run an ntpdate each time I boot linux on my thinkpad (though when
I'm home I have to account for the different networks...).
Assuming you're operating on a mainframe you're far more likely to keep the
T-Rex on UTC and let the guests do the "down and dirty" stuff since each
guest may be (implicitly) supporting a different time zone, so it's
reasonable to provide the baseline clock this way.
Though I do recommend using either an ntp daemon or using crontab to fire
off ntpdate commands at specific intervals.
But the DST shifts are NOT a problem for Linux; You'll only get confused
if you expect the h/w clock to be in "local time" so it'll be automagically
adjusted from the "Standard" time as needed- until you reboot. That's why
it's best to remove the Windoze partition so that you can leave the clock
on UTC.
--------------------
John R. Campbell, Speaker to Machines (GNUrd) {813-356|697}-5322
Adsumo ergo raptus sum
IBM Certified: IBM AIX 4.3 System Administration, System Support
"Hall, Ken
(ECSS)" To: [EMAIL PROTECTED]
<KeHall@exchange. cc:
ml.com> Subject: Re: [LINUX-390] time change
Sent by: Linux on
390 Port
<[EMAIL PROTECTED]
IST.EDU>
10/22/2002 02:22
PM
Please respond to
Linux on 390 Port
The first UNIX I worked with was on a PDP-11 in 1978, and it could handle
the clock change automatically, as long as the change happened on the
"proper" day. (There was one year it didn't.)
I've always found it bizarre that everyone else is still having trouble
with it. My Windows boxen sync their clocks via an add-on NTP client, but
they always get confused when Windows AND the NTP
client try to correct the clocks at the same time.
Remember, zLinux doesn't sync to the system clock except at IPL time. I
recommend NTP.
