Re: [MiNT] timezone change

[Martin-Éric Racine <q-funk@pp.fishpool.fi>]

On 2000-3-27, Guido Flohr <gufl0000@stud.uni-sb.de> wrote:

> > Here, cron executed its activities 1 hour earlier that scheduled,
> > but the system did not change its clock last night.  MINT.CNF has
> > 
> > setenv MINT_CLOCKMODE local
> > setenv TZ EET-2EEST,M3.5.0,M10.5.0
> 
> You should not use localtime, things go much better in UTC.  

Anbd then my RTC and files show a time that has nothing to do
with what my wristwatch says.... no thanks.

> You should also not set TZ if you have the timezone database
> installed.

Too many old apps that have not been re-ported depend on the
environment string.  Even new ones do.  Bash, for instance,
doesn't like it if it cannot figure out its timezone when it 
is started in a secondary level shell.

> Anyway, even in UTC, you have to reboot or run tzinit again
> to inform the kernel about the timezone change.

What's the point of having _any_ timezone functions at all if the
kernel won't update itself.  Might as well run Windows...

> The reboot wouldn't be necessary if we didn't have to provide
> the compatibility functions that deal with localtime (because
> the kernel simple wouldn't need to know about the timezone).

Real people live in a specific time zone, not in UTC, thank you.
Anyhow, seeing that other OSes change time on their own without
a reboot, sounds like UTC stubornness on your part.  Shame.
 
-- 
Martin-Éric Racine  http://funkyware.atari.org/  Atari TT030 FAQ
Lappeenranta, Finland.  Surfing on a Intel/Microsoft-free GEM OS