As noted in Part I and Part II most of the date-time problems were caused by hwclock.

Today Util-linux v2.26 was released.

Using its hwclock as a drop-in replacement without
changing anything in Slackware will fix:

* Kernel NTP clobbering a localtime Hardware Clock

* No Hardware Clock drift correction

* Hwclock clobbering its drift factor to near zero (NTP)

* Was not possible to use 'cold' drift factor with hwclock

* No x86_64 direct ISA access.

* System hangs from automatic direct ISA fall-back

* Since hwclock was changed to default to UTC in 2011 , if
there was no adjtime file and hwclock --localtime
--adjust was called an adjtime file was not created

Correction: there is one required change in Slackware, with the
expanded direct isa access the rtc tests in rc.S and rc.6 scripts
must be fixed. The simplest fix is to drop the -w option from grep.

do I understand this correct and the short version is 'put Util-linux v2.26' into the what should be fixed thread?

this got into the last changelog

Fixed as of today i guess. This is the most recent change log entry.

The same fix is required in rc.6

out of curiosity, has this been brought to Pat's attention, i.e. by email? if I understand correctly, the fix as applied to -current right now seems incomplete.

Yes, I sent an email to Pat at the same time that I posted it here.

1 members found this post helpful.

I found another way to fix the clock when it's not right in Slackware.
I followed the steps in this link and my clock is now correct.

http://pc-freak.net/blog/how-to-fix-...time-troubles/

1 members found this post helpful.