Dirk Nehring dixit: >??? Last week we decide to go with openntpd in the package collections, >so it looks like the default client.
No. Think of FreeWRT as a toolkit. We are not providing firmware for that "Aunt Tilly" or however she's named (at least not now), we provide a toolkit to build embedded GNU/Linux/uClibc (and later maybe with more kernels) appliances. This basically means we provide users with the choice, but have sensible defaults. As Waldemar already correctly explained, OpenNTPD is an ntp server and client, and ntpclient can merely sync the time of the router itself (and OpenNTPD, as it runs continuously, can even do that better, much better if you read the source code). This is the reason I voted for OpenNTPD to be the default in our pre-selected package collections: people using a FreeWRT box as e.g. ADSL or UMTS router should be able to pull a good time from it as well. This is especially good if the users are using ntpclient on their desktops, as the distance to the NTP server is much shorter and so the result will be better - OpenNTPD on the router keeps a good-quality time for much longer. I hope I explained my motivation, and wbx' intended target audience in the first paragraph, well enough. //mirabile -- I believe no one can invent an algorithm. One just happens to hit upon it when God enlightens him. Or only God invents algorithms, we merely copy them. If you don't believe in God, just consider God as Nature if you won't deny existence. -- Coywolf Qi Hunt _______________________________________________ freewrt-developers mailing list [email protected] https://www.freewrt.org/lists/listinfo/freewrt-developers
