Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA5908 ; Fri, 01 Jan 93 15:04:55 EST Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!uunet!news.univie.ac.at!news.tu-graz.ac.at!fstgds01!chmr From: chmr@fstgds01 (Christoph Robitschko) Subject: Re: [386bsd] happy new year Message-ID: <1993Jan4.104339.24050@news.tu-graz.ac.at> Sender: news@news.tu-graz.ac.at (USENET News System) Nntp-Posting-Host: fstgds01 Organization: Technical University of Graz, Austria X-Newsreader: TIN [version 1.1 PL7] References: <C0AFoE.2GB@moxie.hou.tx.us> Date: Mon, 4 Jan 93 10:43:39 GMT Lines: 18 In article <C0AFoE.2GB@moxie.hou.tx.us> Greg Hackney (hackney@moxie.hou.tx.us) wrote: :> However, when setting the date under 386BSD, the onboard computer clock does :> not seem to get updated. A reboot reverts back to it's idea of time. :> Could this be the problem? :> I have rewritten the clock routines, adding one to write the time back to the CMOS. I wrote this a few months ago, but did not release it, because it also contains some (probably) non-portable code to automatically write Time-zone information along with the time to the CMOS. This makes it possible for DOS and 386bsd to (nearly) always have the correct time, even if you have DST. Because this code uses the ALARM registers of the CMOS clock, it might collide with some DOS applications (which one ?), and so is only enabled with a config option. I will clean it up and post it in a few days. Christoph