On Fri, Aug 30, 2013 at 04:04:08PM -0400, Mouse wrote: > > As it's currently written, it seems to me that we as distributor of > > ntpd would need to add this ToS to our ntp package and that the user > > would have to agree to it before he can install/run it. > > Why? This applies only to pool service as far as I can see. At most, > you'd have to rip the pool references out of your distributed config > files, surely?
To clarify, I want to distribute a package that by default just works. That means I either have it default to using the pool or we would need to set the default to our own servers and provide the resources for that. And I'm not sure we want to go with that second option. My main problem is that it requires the End-User to agree to it, and that I basicly can't agree to that on behalf of the End-User. What I would like is to be able to provide a default config that is uses the pool and that is acceptable according to the ToS. I see no problem adding a statement in that config file about the ToS. But I don't want to user to have to agree to the ToS for a default config. Kurt _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
