From: Alessandro Zummo <alessandro.zummo@towertech.it>
To: David Brownell <david-b@pacbell.net>
Cc: akpm@osdl.org, hackers@lists.ntp.isc.org, Andi Kleen <ak@muc.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ralf@linux-mips.org, linuxppc-dev@ozlabs.org,
lethal@linux-sh.org, paulus@samba.org, rmk@arm.linux.org.uk, Kim,
davem@davemloft.net, kkojima@rr.iij4u.or.jp, mills@udel.edu
Subject: Re: NTP time sync
Date: Wed, 22 Nov 2006 21:23:55 +0100 [thread overview]
Message-ID: <20061122212355.046de470@inspiron> (raw)
In-Reply-To: <200611221155.26686.david-b@pacbell.net>
On Wed, 22 Nov 2006 11:55:23 -0800
David Brownell <david-b@pacbell.net> wrote:
> >
> > So, if the arch maintainers agree,
> > I would suggest to schedule it for removal.
> >
> > [1] http://lkml.org/lkml/2006/3/28/358
>
> Suggested time of removal: one year after two relevant software
> package releases get updated:
>
> - NTPD, to call hwclock specifying the relevant RTC;
This might introduce delays. ntpd might open the device
and update the time itself.
> - util-linux, updating hwclock to know about /dev/rtcN;
> - busybox, with its own hwclock implementation.
>
> The util-linux hwclock update is already in the queue, I'm told.
I suspect nobody would change NTPD if we don't
schedule that feature for removal :)
--
Best regards,
Alessandro Zummo,
Tower Technologies - Turin, Italy
http://www.towertech.it
next prev parent reply other threads:[~2006-11-22 20:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 19:36 NTP time sync Alessandro Zummo
2006-11-22 19:51 ` Russell King
2006-11-22 20:26 ` Alessandro Zummo
2006-11-22 19:55 ` David Brownell
2006-11-22 20:23 ` Alessandro Zummo [this message]
2006-11-23 1:48 ` Gabriel Paubert
2006-11-23 10:54 ` Andi Kleen
2006-11-23 11:00 ` Benjamin Herrenschmidt
2006-11-25 23:22 ` David Brownell
2006-11-26 11:04 ` Joakim Tjernlund
2006-11-26 19:21 ` Alessandro Zummo
2006-11-26 21:37 ` Joakim Tjernlund
2006-11-26 22:53 ` Alessandro Zummo
2006-11-27 1:21 ` [Bulk] " David Brownell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061122212355.046de470@inspiron \
--to=alessandro.zummo@towertech.it \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=david-b@pacbell.net \
--cc=hackers@lists.ntp.isc.org \
--cc=kkojima@rr.iij4u.or.jp \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mills@udel.edu \
--cc=paulus@samba.org \
--cc=ralf@linux-mips.org \
--cc=rmk@arm.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).