Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!uunet!usc!sdd.hp.com!uakari.primate.wisc.edu!usenet.coe.montana.edu!warp.mhd.montana.edu!osynw From: osynw@warp.mhd.montana.edu (Nate Williams) Newsgroups: comp.unix.bsd Subject: Re: Beginner's problems with 386BSD Message-ID: <1992Jul28.042836.22231@coe.montana.edu> Date: 28 Jul 92 04:28:36 GMT References: <1992Jul26.232240.23004@cognos.com> <1992Jul27.011712.27704@coe.montana.edu> <1992Jul27.123733.4507@chinet.chi.il.us> Sender: usenet@coe.montana.edu (USENET News System) Organization: /usr/local/lib/MYORG Lines: 30 In article <1992Jul27.123733.4507@chinet.chi.il.us> randy@chinet.chi.il.us (Randy Suess) writes: >In article <1992Jul27.011712.27704@coe.montana.edu> osynw@warp.mhd.montana.edu (Nate Williams) writes: >>>>I wish someone could tell me how to get my clock correct too. I have tried >>Yep, I have tried everything I could think of. I removed /usr/share/zoneinfo >>and remade everything from scratch. My machine is still one hour faster >>than my real time clock. > > I gave up, too. So, I just changed the CMOS time so 386bsd > came out right. Worked great. > After changing my CMOS time, I decided to look at the zoneinfo stuff. Since my wife still used DOS, I didn't really want to leave it with the clock incorrect. (She hasn't seen much of the machine since 386BSD got released :-) I ended up copying the northamerica datafile and making a new RULE called NATE that didn't have the Daylight savings time in it. My machine NOW has the correct time and offset. I guess my BIOS is too smart for 386BSD. The only problem with this is I'm not sure how the BIOS handles the time-change. I may have to reboot, but that's a few months away. 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?