From owner-freebsd-stable@freebsd.org Sun Aug 16 10:40:57 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 B8EA99BAC08 for ; Sun, 16 Aug 2015 10:40:57 +0000 (UTC) (envelope-from florian.ermisch@alumni.tu-berlin.de) Received: from mail-2.alumni.tu-berlin.de (mail-2.alumni.tu-berlin.de [130.149.5.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7B6071144 for ; Sun, 16 Aug 2015 10:40:56 +0000 (UTC) (envelope-from florian.ermisch@alumni.tu-berlin.de) X-tubIT-Incoming-IP: 78.52.166.150 Received: from f052166150.adsl.alicedsl.de ([78.52.166.150] helo=android-a12318b22af) by mailbox.alumni.tu-berlin.de (exim-4.76) with esmtpsa [UNKNOWN:AES256-SHA:256] for id 1ZQvMu-0001jO-2X; Sun, 16 Aug 2015 12:40:48 +0200 User-Agent: K-9 Mail for Android In-Reply-To: <55D03771.9000605@FreeBSD.org> References: <55D03771.9000605@FreeBSD.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Subject: Re: 10.2: ntp update breaks DCF77 clock From: Florian Ermisch Date: Sun, 16 Aug 2015 12:40:40 +0200 To: freebsd-stable@freebsd.org Message-ID: <70807946-3B0F-4D8B-B496-F032F76C6F43@alumni.tu-berlin.de> 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: Sun, 16 Aug 2015 10:40:57 -0000 Am 16. August 2015 09:10:41 MESZ, schrieb Matthew Seaman : >On 15/08/2015 16:46, Christian Weisgerber wrote: >> The ntp code is not very transparent, but I think the root cause >> are the ntp/config.h changes that came with the 4.2.8p3 update. A >> number of previously disabled obscure clock drivers were enabled, >> but crucially CLOCK_RAWDCF was disabled, and this is the PARSE >> subdriver needed to use the popular DCF77 serial receivers. >> […] > >[…] >For a more timely solution[*], it looks like the ports is your best >option. By default the net/ntp port disables all of the clock drivers, >but allows you to configure the port to enable whatever drivers you >want. >[…] You could also check the PCBSD/TrueOS pkg repos. I Kris Moore mentioned on BSDnow he'll happily enable/change build options when people need them. When ntpd is the only pkg you'll install anyway this might be the most hassle free option. Regards, Florian