On Fri, Feb 11, 2000 at 09:23:36AM +1300, [EMAIL PROTECTED] wrote: > Hi > > i am running slink 2.1 with kernel 2.0.36 on a Dell Power Edge 2100 and i > am having problems with the time. Basically what happens is that once i > set up the correct date/time in BIOS...when i load up linux the time & date > get's corrupted.
you should not tamper with the hardware clock. > eg. real date time is 11-Feb 09:36. When i load linux up it shows 12-Feb > 04:28. usually linux (and every other unix i am aware of) keeps the hardware clock set to UTC (GMT) not local time like broken OSes. > When i go back into BIOS it shows 11-Feb 15:31 > > what the hell is going on? :) your hardware clock is reset at shutdown by linux, its set to the current time in GMT, as known by linux. > i have tested the bios clock by setting it up correctly and booting with a > windows boot disk and it keeps the correct date/time. I can only surmise > that it is the linux software that is corrupting my date/clock. its not corrupted, windows is broken and keeps the hardware clock in local time, linux/un*x does not, it keeps it in GMT. > Any thoughts would be appreciated. if you must have correct time in windows you will have to reconfigure linux to keep time in local time instead of GMT. personally i just set the broken OS's (in my case MacOS) timezone to London, England (GMT) so it won't corrupt the hardware clock, then linux has correct time and hardware clock is also correct (in GMT as it should be) I never do anything in my broken OS that depends on the time anymore so its not a problem, i just use my wristwatch when i need to know what time it is ;-) -- Ethan Benson
