Bug in cygwin's mkdir

I came across what I believe is an interesting bug. Let's say I have a file in a directory named foo.exe. If I run mkdir foo then it succeeds. If I then run mkdir -p foo then it fails. If I remove foo.exe then mkdir -p foo succeeds. The error message contains says foo exists but is not a

Re: Bug in cygwin's mkdir

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Chris Mumford on 8/22/2005 3:02 PM: I came across what I believe is an interesting bug. Let's say I have a file in a directory named foo.exe. If I run mkdir foo then it succeeds. If I then run mkdir -p foo then it fails. If I

date and UTC and GMT odd behaviour

I have just noticed an anomaly with the UTC and GMT time zones in the standard coreutils. Around the Unix epoch they are not delivering the same times: --At midnight: $ date -d Tue Jan 01 00:00:00 UTC 1970 +%s 0 $ date -d Tue Jan 01 00:00:00 GMT 1970 +%s -3600 --At 1am $ date -d Tue Jan 01

Re: date and UTC and GMT odd behaviour

Mike 'Mike' Jones [EMAIL PROTECTED] writes: A little bit of trial-and-error and I find that the anomaly is limited to between 6pm, 23 Jun 1968 GMT and 2am, 31 Oct 1971: $ date -d Sat Oct 31 01:59:59 UTC 1971 +%s 57722399 $ date -d Sat Oct 31 01:59:59 GMT 1971 +%s 57718799 $ date -d Sat

Re: date and UTC and GMT odd behaviour

Yep, I tried the same on a SuSE 8.2 machine with version 4.5.8 in Germany and I get the correct behaviour. Unfortunately it's the only SuSE machine I have access to! However, on a machine in the USA running Red Hat WS release 3 and data version 4.5.3, I also see the correct behaviour. So,

Re: date and UTC and GMT odd behaviour

Mike 'Mike' Jones [EMAIL PROTECTED] writes: A little bit of trial-and-error and I find that the anomaly is limited to between 6pm, 23 Jun 1968 GMT and 2am, 31 Oct 1971: Good detective work. This is a bug that stems from the fact that Great Britain was at UTC+1 for that entire period. The bug