Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site cstvax.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!mhuxn!mhuxr!ulysses!allegra!mit-eddie!think!harvard!seismo!mcvax!ukc!cstvax!gdmr
From: gdmr@cstvax.UUCP (George D M Ross)
Newsgroups: net.unix-wizards
Subject: Re: Daylight Savings Time
Message-ID: <36@cstvax.UUCP>
Date: Fri, 20-Dec-85 04:56:34 EST
Article-I.D.: cstvax.36
Posted: Fri Dec 20 04:56:34 1985
Date-Received: Mon, 23-Dec-85 04:37:12 EST
References: <507@azure.UUCP> <493@brl-tgr.ARPA> <985@rlvd.UUCP>
Reply-To: gdmr@cstvax.UUCP (George D M Ross)
Distribution: net
Organization: Comp. Sc., Edinburgh Univ., Scotland
Lines: 22

In article <985@rlvd.UUCP> drg@rlvd.UUCP (Duncan Gibson) writes:
>Last year I did some work with the "Newcastle Connection" ...
> One system took
>"British Summer Time" (BST) into account, and the other ran GMT. I can
>remember being incredibly confused when I copied a file from one machine
>to the other and did an 'ls -l' on it only to find that it wasn't due for
>creation for another hour (:-))

This is, surely, a failing in the way information is presented to the user.
The poor user shouldn't be expected to remember all the quirks of the file
servers (s)he might use -- rather the clients should hide them.  In this case
the date should have been converted into the appropriate local form before
you, the user, got to see it.

Perhaps this is a "feature" of the Newcastle Connection, or perhaps it's
just ctime that's broken.

-- 
George D M Ross, Dept. of Computer Science, Univ. of Edinburgh
Phone: +44 31-667 1081 x2730
UUCP:  <UK>!ukc!cstvax!gdmr
JANET: gdmr@UK.AC.ed.cstvax