I have a cron job that runs ntpdate daily now. Fortunately I won't be rebooting much anymore.

why not just enable ntpd

I had never set up ntpd before and using ntpdate from cron was simpler. I took the time to set it up and now my RPi is the ntp server for my LAN, haha. I still have some excess RAM and CPU cycles so I am thinking of adding a mozilla sync server too.

Thats the easy one :P

http://docs.slackware.com/howtos:network_services:ntp

I have now pushed out a slackpkg update for Slackware ARM 14.1 both in patches/ and have overwritten the package within the slackware/a/ series.
It will now error if the date is in the past (UNIX Epoch time - 1970), and having put the new package in to the 'a' series, future users installing 14.1 will be able to use slackpkg immediately since it now knows about the new GPG key.

Hopefully these issues are now solved.

1 members found this post helpful.

Thanks for your hard work. It is much appreciated.

Just to add to that... for the cost of a RTC it would be a good thing to have one installed, because the time and trouble it saves is very welcome indeed. Once it's configured you'll never need to wonder or worry about accurate timekeeping on your Slackware ARM system again.

I like the DS3231 based RTCs because of the extreme accuracy of the controller. I bought 5 of them from eBay (like this) for around $10 and am seriously impressed by them. Installed in seconds and configured in a few short minutes, using the I2C bus under Slackware ARM. Very accurate. Very reliable. Perfect solution for me personally.

1 members found this post helpful.

For the record, don't forget to upgrade aaa_elflibs, as if the added udev lib inside it is not present, slackpkg will fail with the same gpg error.