Bug#755722: Not having a hwclock systohc and back is not only an NTP issue

[Eric L.]

Hello,

I tried to follow your discussion, and I want to add a new use case to 
having a generic solution, independent of NTP:

My problem is a VDR system where I need to have the HW clock set to 
LOCAL (not UTC).
No continuous network access, hence no NTP.
VDR itself is setting the (system) clock based on the time provided by 
the TV-transponder
Today was summer to winter time switching, so the clock made a big jump 
backwards and the (TV) system doesn't like it and freezes.
No issue, restart the system and start again, right? Actually, no, 
because the system clock isn't saved to the HW clock anymore, you start 
the cycle again and again.

So, summary:
- the world is not perfect
- there are many places where the time can be switched, not only through 
NTP.
- the hwclock mechanism was perhaps a workaround, but it worked for all 
of us for many years
- so make sure that something works for all of us is put in place before 
removing it

Thanks, Eric