From owner-freebsd-hackers Fri Dec 26 21:30:26 1997 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA04775 for hackers-outgoing; Fri, 26 Dec 1997 21:30:26 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA04769 for ; Fri, 26 Dec 1997 21:30:15 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id VAA02013 for ; Fri, 26 Dec 1997 21:30:14 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199712270530.VAA02013@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: freebsd-hackers@FreeBSD.ORG Subject: totally accurate clocks 8) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 26 Dec 1997 21:30:14 -0800 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk Surfing around the web I found this old reference: ftp://aleph.gsfc.nasa.gov/GPS/totally.accurate.clock Now it is quite obvious that we can use gps units to sync our clocks to . The question now is, does anyone in this group have any experience in using something like a Garmin GPS, Motorola Oncore , TAC to provide a stable, accurate clock? If I am not mistaken from anywhere to $150 to $300 for a GPS unit we should be to get timing clock signals accurate from 50 to 100 nano seconds. Tnks, Amancio