Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83 (MC840302); site erisun.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!mcvax!enea!erix!erisun!leif
From: leif@erisun.UUCP (Leif Samuelsson)
Newsgroups: net.unix
Subject: Re: Daylight Saving Time???
Message-ID: <320@erisun.UUCP>
Date: Thu, 28-Mar-85 11:56:48 EST
Article-I.D.: erisun.320
Posted: Thu Mar 28 11:56:48 1985
Date-Received: Sun, 7-Apr-85 06:29:07 EST
References: <316@erisun.UUCP> <471@grendel.UUCP>
Reply-To: leif@erisun.UUCP (Leif Samuelsson)
Distribution: net
Organization: Ericsson Information Systems, Sundbyberg, Sweden
Lines: 35

In article <471@grendel.UUCP> avolio@grendel.UUCP (Frederick M. Avolio) writes:
>> 
>> Well, it seems that all 4.2BSD machines in Europe went on
>> DST a week too early this year...
>
>     One other solution --- I believe this is good for any 4.2bsd
>based U*ix.  When you configure the system specify dst followed by a
>number. 1 = usa, 2=australia, 3=w. europe, 4=central europe, and 5= e.
>europe.

This isn't the problem. The code is *wrong* for group 3 and 4 of
the above. If we hadn't specified a "4" for our machine, we would
have had to wait another *month* for DST to happen. (It's this
sunday, folks!)

It's hard work to correct the code in ctime.c for a system
administrator, even with the sources, because it does not reside in
the kernel. It is linked in with every routine that deals with
time, like "date".

I think a solution would be to handle the timezone and dst
business with the "date" command and have the algorithms in the
kernel instead. That way you could specify the timezone and dst
in your /etc/rc like this:

	date -tMET -d4


Leif Samuelsson

Ericsson Information Systems AB			..mcvax!enea!erix!erisun!leif
Advanced Workstations Division
S-172 93  SUNDBYBERG				59 19 N / 17 57 E
SWEDEN