On Mon, Mar 28, 2011 at 04:52:16PM +0200, Kurt J. Bosch wrote:
28.03.2011 16:20, Dave Reisner:
... This is an awful lot of movement for just one patch. I also don't agree with adding an extra daemon to take care of the hwclock when it could be satisfied just as easily by a simple var in /etc/rc.conf (falling back on the current behavior if it doesn't exist). Thank you for your comments. Actually the daemon idea came from Tom. Afaics the main benefits is you could use it in a pm-utils hook to fix hardware clock drift while suspended to disk.
My hangup (which I should have mentioned in my previous email), is that the popular use case will always be to set the hwclock as we do right now. This changes default behavior without any fallback. The majority of users are inconvenienced and need to pick up on this change. I'll have to read up on pm-utils hooks to see if there's another approach that would also be suitable. dave