*BSD News Article 2590


Return to BSD News archive

Newsgroups: comp.unix.bsd
Path: sserve!manuel!munnari.oz.au!mips!mips!sdd.hp.com!usc!rpi!usenet.coe.montana.edu!warp.mhd.montana.edu!osynw
From: osynw@warp.mhd.montana.edu (Nate Williams)
Subject: Re: Beginner's problems with 386BSD
Message-ID: <1992Jul27.180942.24689@coe.montana.edu>
Sender: usenet@coe.montana.edu (USENET News System)
Organization: /usr/local/lib/MYORG
References: <1992Jul26.232240.23004@cognos.com> <1992Jul27.011712.27704@coe.montana.edu> <jnpotts.712255910@vincent1.iastate.edu>
Date: Mon, 27 Jul 1992 18:09:42 GMT
Lines: 29

In article <jnpotts.712255910@vincent1.iastate.edu> jnpotts@iastate.edu (James N. Potts) writes:
>I had a problem at first getting the correct time, but I finally got it to
>work.  I set my system clock to GMT, and linked /etc/localtime to the correct
>timezone (in my case, /usr/share/zoneinfo/US/Central).  Of course, now my DOS
>programs are a few hours off, but at least I get the correct time when I log
>onto my 386BSD system.
>
>James
>


It appears that I'm going to have to change my Real Time Clock to get
the correct time on my machine.  Some have sent me mail telling me to
re-make the kernel.  That didn't seem to make any difference.  
	Other have mentioned symlinking /etc/localtime to 
/usr/share/zoneinfo/US/Mountain, and that has me one hour too fast.  What
I *THINK* is happening is both the 386BSD code and my BIOS are both
correcting for Daylight Saving's time.  For the time being, I think I
am going to have to change my clock, but if I could figure out the format
of the zoneinfo data files, I think I could fix it so that it left the 
daylight savings time to my BIOS.  If nobody else figures it out, I will
probably look at it later, but it's not a big deal right now.  There are
more interesting bugs to fix. :-)

Nate
-- 
osynw@terra.oscs.montana.edu |  A hacker w/out a home.  Anyone  interested
work: (406) 994-5991         |  in a used Sys. Admin., which alot of 
home: (406) 586-0579         |  good hacks left?