FWIIW, the hardware clock configuration is set to use localtime by default. This can be reconfigured to use UTC (see /etc/rc.sysinit which includes the config file /etc/sysconfig/clock if it exists), but it probably isn't worth the effort.
WRT my previous advice on using hwclock, do *not* use the --utc flag. hwclock --systohc Best regards, gvb Joshua Minor wrote: > Great. This will be perfect. > > For now I've set mine manually via ntpdate and hwclock. > > Thanks everyone. > > -josh > > On Dec 22, 2007, at 4:49 AM, C. Scott Ananian wrote: > >> On Dec 22, 2007 3:07 AM, Bernardo Innocenti <[EMAIL PROTECTED]> >> wrote: >>> Joshua Minor wrote: >>>> Is it reasonable to assume that the XO's clock is set correctly? >>>> Specifically I'd like to use python's time.time() to determine which >>>> participant of an activity has been using it the longest. >>> A NetworkManager callout could set it, but it seems we're not >>> doing it yet. >> It's done in joyride and will be done in update.1, but not in ship.2 >> builds. trac #3359. >> --scott >> >> -- >> ( http://cscott.net/ ) > > _______________________________________________ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel _______________________________________________ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel