So, troubled by the same situation and not finding any alternatives, I tried this technique. However, it doesn't seem to work -- at least on my BB Black with the 2015-03-01 build.
In fact, I had a hint that it would not work even before I tried it. My original /etc/timestamp file had a March 1 date matching the build date, but my /var/log/syslog timestamps on reboot began with March 5 while today's date is March 15. I don't know why the system decided to startup using March 5 as its date. And after following the suggestion of updating /etc/timestamp using a cron job -- I chose once per minute since the /etc/timestamp file captured only hours/minutes (why??) -- and confirming that the file was being updated appropriately, after a reboot, I'm back to March 5 until after networking is up and NTP can connect to a server. So, how DOES the system decide to choose a starting time on reboot??? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
