Message-Id: <200305061900.h46J0Z700667@delorie.com>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
From: news AT garydjones DOT mailshell DOT com
Subject: File modification times
Organization: 
Summary: 
Keywords: 
To: cygwin AT cygwin DOT com
Date: Tue, 06 May 2003 20:54:21 +0200

Running ScanDisk this evening generated errors for a whole bunch of files as
follows:

This file or folder's last-modified date or time is invalid or is in the
future. This may be because your computer's clock is set incorrectly.
ScanDisk repairs future dates by changing them to your computer's current
date setting. ScanDisk repairs out-of-range dates or times by changing them
to the nearest setting within the valid range.

Nothing new, to be honest, it almost always happens. Previously I had put it
down to Microsoft's OS's normal behaviour (i.e. shit). Something made me
have a look today though, and Explorer revealed this oddity on each of the
files involved (exact dates and times vary):

Created: 02 May 2003 14:33:56
Modified: 30 March 2003 17:06:00

i.e. it thinks that the file was modified before it was created. Huh? I
can't say for all of them, but at least some were files which were upgraded
from previous versions of Cygwin packages on that date. Is Setup or bzip2 or
something not doing something optimal here?

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/