Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!goanna!escargot!minyos.xx.rmit.OZ.AU!s902113 From: s902113@minyos.xx.rmit.OZ.AU (Luke Mewburn) Newsgroups: comp.os.386bsd.bugs Subject: Fix to clock probs [was Re: CMOS clock is incorrectly handled] Message-ID: <1tk1bfINN383@escargot.xx.rmit.OZ.AU> Date: 22 May 93 01:58:07 GMT References: <1993May18.165711.3527@alw.nih.gov> Reply-To: zak@rmit.edu.au Organization: Not RMIT (this is an implicit disclaimer :) Lines: 35 NNTP-Posting-Host: minyos.xx.rmit.oz.au crtb@helix.nih.gov (Chuck Bacon) writes: > I've got my CMOS clock running so that DOS gets the time of day > correctly. But 386bsd sets its time three hours fast. I'm in > the Eastern time zone, so I'm 4 or 5 hours west of Greenwich. > Has anybody figured this one out? I'm pretty sure that I've worked this one out. It involves a bit of kernel hacking, among other things. You have to a) calculate the offset to gmt to where you are in hours. This is the value you use in the 'timezone xxx' line in /sys/i386/conf/WHATEVER. (e.g, 'timezone 10') b) recompile your kernel c) sym link /etc/localtime to /usr/share/timezone/wherever/you/are (e.g, /usr/share/timezone/Australia/Victoria) d) reboot with new kernel To be honest, I've not tested this fully. What I _know_ works is setting the kernel's idea of timezone in the config file to 0 (gmt), setting the bios time to gmt, and then symlinking in /usr/share/timezone/Australia/Victoria to /etc/localtime. So, I've assumed (maybe incorrectly) that setting the kernel so that it thinks the bios time is gmt (by telling you are at gmt+10 or whatever) will still work. Experiment. I will test out the 'setting timezone to 10 hours and putting my bios clock to the _real_ time here' trick tonight and follow up this post if I'm wrong. > -- > Chuck Bacon - crtb@helix.nih.gov ( alas, not my 3b1 )-: > ABHOR SECRECY - DEFEND PRIVACY