Comment # 12 on bug 1082369 from Per Jessen

(In reply to Reinhard Max from comment #11)
> (In reply to Per Jessen from comment #10)
> 
> > I can't help pointing out the contradiction here - "if user want to use ntp,
> > he should disable ntp synchronization." :-)
> 
> Yeah, that's the "joy" of using the same name for a protocol and its
> reference implementation. Maybe we should use "NTP" when referring to the
> protocol and generic synchronisation service, and "ntp" or even "legacy ntp"
> when referring to the implementation.

or just say "chrony" / "ntpd" ? 

> > Personally, I think YaST ought to fail quietly and not stop the
> > installation.
> 
> If we made it faill quietly, it won't take long until we receive bug reports
> complaining that YaST doesn't inform the user that the NTP settings they
> made are being ignored.

Yeah, I guess so.  Still, assuming most users will prefer the new default, it
would not be very many. 

> BTW, I am curious why you want or need to use ntp instead of chrony? Is it
> just personal preference or is there a technical reason, e.g. you use a
> clock source for which chrony does not have a driver?

No benefits in changing - and we use ipv6 multicast.