Setting timezones
Sybren Stüvel <[email protected]>
| Newsgroups | gmane.comp.handhelds.openzaurus.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi folks,
Some more feedback here. I tried setting the timezone with the
"Date/Time" application. I set it to Europe/Amsterdam, since that's
where I live. I also linked /usr/share/zoneinfo/Europe/Berlin to
/etc/localtime. I'd rather use Europe/Amsterdam, but that file wasn't
there, and Berlin is in the same timezone anyway.
If I then set the time with the "Date/Time" application using
ntp.xs4all.nl (also situated in Amsterdam) the clock is set two hours
back, i.e. to UTC. This also happens when I open the console and type
'ntpdate ntp.xs4all.nl'. This is via the Opie console:
root@spitz:~# echo $TZ
Europe/Amsterdam
root@spitz:~# date
Thu Apr 6 09:00:35 Europe/Amsterdam 2006
The weird thing is, that if I log in via SSH/WiFi, and type 'ntpdate
ntp.xs4all.nl', the clock is set to the correct timezone. This is via
the WiFi SSH shell:
root@spitz:~# echo $TZ
root@spitz:~# date
Thu Apr 6 11:00:38 CEST 2006
After installing timezones-europe, linking
/usr/share/zoneinfo/Europe/Amsterdam to /etc/localtime, and rebooting,
I get:
root@spitz:~# date
Mon Mar 20 08:24:11 CET 2006
on both the Opie console and the SSH console. Running 'ntpdate' one
last time set the clock straight.
So the bottom of the story is this: when you pick a city off the map
to select your timezone, you might be selecting a city that doesn't
work. Would it be a lot of work to alter the map to only show cities
for which it actually knows timezone information?
--
Sybren Stüvel
"Gravitation cannot be held responsible for people falling in love."
-- Albert Einstein
signature.asc
(application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFENNufNIPvGICzDyQRAhvLAKCIVcMlrr61gHVV+/Kl/Go7kVrgTACeKxwn dLVxRmeFXjl1gfiStU0wS/Q= =W015 -----END PGP SIGNATURE-----