Path: utzoo!utgpu!trantor.umd.edu!ntp-relay
Message-ID: <9002272218.AA10492@intrepid.itstd.sri.com>
To:	Mills@udel.edu
Cc:	ntp@trantor.umd.edu
Subject: Re: clock driver? 
References: Your message of Tue, 27 Feb 90 20:56:34 GMT.
Date:	Tue, 27 Feb 90 17:18:55 EST
From:	davy@itstd.sri.com
Newsgroups: list.ntp
Distribution: ut
Approved: devnull@gpu.utcs.toronto.edu


     From:  Mills@udel.edu
     Date:      Tue, 27 Feb 90 20:56:34 GMT
     Subject:   Re:  clock driver?

     Dave,

     Right on! With another GOES clock, maybe we can measure the yank of the
     San Andreas fault. I know of no such driver, but maybe how would you
     like to tackle that feat? Feet?

     Dave

Well, this isn't a GOES clock, it's a WWVB clock (Model 60-DC, not 468-DC).

Apparently we purchased two of them for some project a few years ago,
and this one's been sitting in a cabinet ever since the project ended.
Nobody knows where the other one is.  I even had to call up Kinemetrics
to get a manual for it.  They were very nice and mailed me a free one,
though.  The guy I talked to had never heard of NTP, but I told him a
little about what it did, and he sounded interested.  Unfortunately,
he didn't include his business card with the manual, so I can't mail
him any more info.  Oh well.

Anyway, if nobody has a driver, I reckon I'll be writing one.  I
haven't decided which program (ntpd or xntpd) to write it for yet,
though.  Before I found out we had a clock I was planning to use ntpd
everywhere since xntpd seems to be sort of large to run on diskless
machines.  But now that I have a clock, I guess I'll have to rethink
all this.  Sigh.

If anyone has any recommendations, suggestions, things to watch out
for, I'd appreciate hearing from you.

--Dave