JackOfAll wrote: > You don't need a script for that. (But it still isn't the solution for > your DHCP issue anyway.) > > /etc/sysconfig/ntpdate > > Code: -------------------- > > > # Set to 'yes' to sync hw clock after successful ntpdate > SYNC_HWCLOCK=no > -------------------- > >
I totally get that I still have an issue with first boot after a power cycle, but I very rarely, if ever, remove power from the board. Assuming the CSOS remains as stable as I've seen it so far, and considering how power-efficient the Wandboard is, I'm guessing most users won't often power it down either. Having the RTC up and running (and being set by ntpdate utility) seems like a very low impact and safe change, even if it is not a complete solution. It also has the the advantage that /var/log/messages won't typically be full of entries with date-stamps near the epoch, making them easier to read when debugging. I wish we could get a battery-backed RTC, but we can't. This gets us as close as possible to a normal Linux system behaviour during all but the first boot after a power cycle. I think there are sufficient advantages to keeping the RTC kernel support as part of the CSOS standard image to make it a good decision. Obviously, a well engineered and complete solution to my DHCP lease issue would still be welcome in the long term. Cheers, ------------------------------------------------------------------------ dsdreamer's Profile: http://forums.slimdevices.com/member.php?userid=12588 View this thread: http://forums.slimdevices.com/showthread.php?t=98544 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/unix
