On Tue, Aug 19, 2014 at 08:25:24AM -0400, Robert Moskowitz wrote:
A lot of the arm boards, or so I have been told, are like mine; no
This is causing a lot of interesting problems with boot up until ntp
can set the time (or is it ntpdate?).
So I was thing of how to 'fix' this. Over on the Redsleeve list a
fellow that is dealing with this on his RasberryPi noted:
This might be one solution if someone took it on (I have no skills in
coding or building packages).
But I was thinking of a scripted approach.
First you need a file that has date/time in a format that it can be
piped into the date command like:
date < /etc/fixtime
The image build process would put the build date into this file for
starters. At firstboot, if the time is near zero (some seconds
having passed since poweron), a few things happen:
The fixtime script is run to set the time to the image build date/time.
The fixtime script is set to run at every boot as one of the first
A cron job is enabled (hourly or dayly) to update /etc/fixtime so the
next boot will have a more current time.
You're describing almost exactly the fake-hwclock package I wrote for
Debian a couple of years ago, to solve exactly this problem... :-)
Explicitly it also saves the current time at shutdown too.
Steve McIntyre steve.mcintyre(a)linaro.org
| Open source software for ARM SoCs