Thanks for the tip. Ok, I uploaded to http://drop.io/saf_chumby with the file name ntpd.tgz.
scp this archive from your host computer to your chumby by typing the following command on your host computer.
(This command is for a linux host - I don't use windows, but something similar should work on a windows machine.)
scp ntpd.tgz root@your_chumby_ip_address:/psp
Then log into your chumby using ssh, and unpack the archive using the following commands on the chumby itself:
mount -o remount,rw /
tar -xvzf /psp/ntpd.tgz
Make sure psp/ntp.drift is owned by ntp - this should happen automatically. Then just reboot the chumby. The
ntpd daemon should now be running, and keeping your time synch'd. After an hour or so, ntpd will compute the
clock drift, and write a correction factor to /psp/ntp.drift. My correction factor is currently -163.697. This number
is a function of the clock accuracy within the chumby itself, and it will vary with temperature.
Every 6 months or so, you should check ftp://time.nist.gov/pub/ to get the latest leap-second file. These files
have an expiration date, so you will want to stay current. Once you download a new file, replace the one in
psp/ntp.leap and reboot.
I have two GPS timeservers, which I am using to sync my chumby. Right now, the chumby is off by about
2 milliseconds, which is not bad for a wireless connection.