KDED time zone module

[Thiago Macieira]

David Jarvie wrote:
>The only case where a significant amount of processing may be required
> at initialisation is on those systems where the local time definition
> file /etc/localtime is held as a copy of, rather than a link to, one of
> the zoneinfo files.

So you're saying that the only case of significant amount of processing is 
the default case?

Remember that /etc/localtime must be a copy, not a link. If it's a link, 
the local time isn't available at boot time if /usr is a mount-point, 
which in turn means the system clock will be set wrongly if the hardware 
clock isn't Universal Time.

But you didn't answer the question: does that information need to be 
cached? Does it need to be shared via mmap() file? 

Also, why do we need that information? What are the use cases?

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20070330/e4c3eaef/attachment.sig>