From owner-freebsd-arm@FreeBSD.ORG Thu Feb 7 02:12:51 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 9EB3FF76; Thu, 7 Feb 2013 02:12:51 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from monday.kientzle.com (99-115-135-74.uvs.sntcca.sbcglobal.net [99.115.135.74]) by mx1.freebsd.org (Postfix) with ESMTP id 6F56FAC4; Thu, 7 Feb 2013 02:12:50 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id r172ClE5096128; Thu, 7 Feb 2013 02:12:47 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.143] (CiscoE3000 [192.168.1.65]) by kientzle.com with SMTP id 8u7zcyd7756kdxbqpp5h5un6bw; Thu, 07 Feb 2013 02:12:47 +0000 (UTC) (envelope-from tim@kientzle.com) Subject: Re: SD card -image- for the beaglebone Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=windows-1252 From: Tim Kientzle In-Reply-To: <1360177280.93359.611.camel@revolution.hippie.lan> Date: Wed, 6 Feb 2013 18:12:44 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <933D29A2-B78E-44D5-A701-7397CD532CD1@kientzle.com> References: <510A4F5B.7000407@g7iii.net> <1359646574.93359.327.camel@revolution.hippie.lan> <510AE1D6.8010203@g7iii.net> <1360124308.93359.557.camel@revolution.hippie.lan> <5112115D.5040709@g7iii.net> <1360158409.93359.590.camel@revolution.hippie.lan> <52928DD2-AA41-4B3C-A22A-1F755832D220@bsdimp.com> <1360177280.93359.611.camel@revolution.hippie.lan> To: Ian Lepore X-Mailer: Apple Mail (2.1283) Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Feb 2013 02:12:51 -0000 >=20 > Well, besides running a little roll-your-own clock ensemble system, a > more mundane use of multiple PPS inputs would be simple failover for > ntpd. At least, I think in theory it should work fine to configure = ntpd > with multiple refclocks and if one goes bad it can continue with = others. Hmmm=85 I think I would instead have multiple BeagleBones, each with a single PPS input and each acting as an independent NTP master. If one goes bad, the NTP clients will fail over to use another master. Tim