From owner-freebsd-stable@freebsd.org Mon Aug 17 18:00:08 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 756789BBDE1 for ; Mon, 17 Aug 2015 18:00:08 +0000 (UTC) (envelope-from news@mips.inka.de) Received: from mail.inka.de (quechua.inka.de [IPv6:2001:7c0:407:1001:217:a4ff:fe3b:e77c]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3D2D010F2 for ; Mon, 17 Aug 2015 18:00:08 +0000 (UTC) (envelope-from news@mips.inka.de) Received: from mips.inka.de (news@[127.0.0.1]) by mail.inka.de with uucp (rmailwrap 0.5) id 1ZROhZ-0003iM-HU; Mon, 17 Aug 2015 20:00:05 +0200 Received: from lorvorc.mips.inka.de (localhost [127.0.0.1]) by lorvorc.mips.inka.de (8.15.2/8.15.2) with ESMTP id t7HHxM7R055388 for ; Mon, 17 Aug 2015 19:59:22 +0200 (CEST) (envelope-from news@lorvorc.mips.inka.de) Received: (from news@localhost) by lorvorc.mips.inka.de (8.15.2/8.15.2/Submit) id t7HHxMm9055387 for freebsd-stable@freebsd.org; Mon, 17 Aug 2015 19:59:22 +0200 (CEST) (envelope-from news) To: freebsd-stable@freebsd.org From: Christian Weisgerber Newsgroups: list.freebsd.stable Subject: Re: 10.2: ntp update breaks DCF77 clock Date: Mon, 17 Aug 2015 17:59:22 +0000 (UTC) Lines: 18 Message-ID: References: <55D03771.9000605@FreeBSD.org> <1439744220.242.87.camel@freebsd.org> X-Trace: lorvorc.mips.inka.de 1439834362 55102 ::1 (17 Aug 2015 17:59:22 GMT) X-Complaints-To: usenet@mips.inka.de User-Agent: slrn/1.0.2 (FreeBSD) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Aug 2015 18:00:08 -0000 On 2015-08-16, Ian Lepore wrote: > I wonder: is there a reason to not enable all (or most of) the refclocks > in base and in ports? I guess it isn't very elegant to enable clock drivers if nobody knows whether they work or whether the hardware was ever produced in series or whether external services they rely on still exist. As a rough guess I'd say NMEA GPS clocks are the most popular, maybe also by way of gpsd and SHM, some RAWDCF here in Europe, a few institutional or corporate users with MEINBERG clocks, and then things are getting mighty thin on the ground... Not coincidentally this looks quite a bit like the list of clock drivers originally enabled (r268351). -- Christian "naddy" Weisgerber naddy@mips.inka.de