On Wed, 2012-10-31 at 10:15 -0200, Otavio Salvador wrote: > On Wed, Oct 31, 2012 at 10:11 AM, Phil Blundell <[email protected]> wrote: > > On Wed, 2012-10-31 at 12:43 +0100, Martin Ertsås wrote: > > > >> for now I guess we can just use pool.ntp.org > > > > > > I'm not sure that this is a very good idea. The pool.ntp.org > > documentation is fairly explicit that they don't want this: > > > > > > You must absolutely not use the default pool.ntp.org zone names > > as the default configuration in your application or appliance. > > So how we'll fix it? We need to fix it somehow. So give us an alternative to > us.
It's not entirely obvious to me that it really does need to be fixed all that urgently, at least not in the default metadata. The sky is probably not going to fall in if you ship a service file which doesn't sync with NTP by default. In particular, if it's been broken in meta-oe for however long up to this point, I don't entirely understand why moving the recipe to meta-networking suddenly means that fixing this issue is super-important or why the two things need to be done at the same time. But, anyway, see other email I just sent for a handful of alternatives. p. _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
