[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20061122212355.046de470@inspiron>
Date: Wed, 22 Nov 2006 21:23:55 +0100
From: Alessandro Zummo <alessandro.zummo@...ertech.it>
To: David Brownell <david-b@...bell.net>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linuxppc-dev@...abs.org, Kumar Gala <galak@...nel.crashing.org>,
Kim Phillips <kim.phillips@...escale.com>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Andi Kleen <ak@....de>, akpm@...l.org, davem@...emloft.net,
kkojima@...iij4u.or.jp, lethal@...ux-sh.org, paulus@...ba.org,
ralf@...ux-mips.org, rmk@....linux.org.uk, mills@...l.edu,
hackers@...ts.ntp.isc.org
Subject: Re: NTP time sync
On Wed, 22 Nov 2006 11:55:23 -0800
David Brownell <david-b@...bell.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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists