Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com From: Robert R Schneck Subject: Re: Managed mounts and .exe files (Was Re: cp, install, and the .exe extension) Date: Sat, 21 Feb 2004 23:07:03 +0000 (UTC) Lines: 39 Message-ID: References: <20040219232350 DOT GE23994 AT redhat DOT com> <6 DOT 0 DOT 1 DOT 1 DOT 0 DOT 20040220141302 DOT 0391ba10 AT 127 DOT 0 DOT 0 DOT 1> X-Complaints-To: usenet AT sea DOT gmane DOT org X-Gmane-NNTP-Posting-Host: 80.45.134.193 User-Agent: slrn/0.9.8.0 (CYGWIN_NT-5.1) Igor Pechtchanski wrote: > On Sat, 21 Feb 2004, Robert R Schneck-McConnell wrote: >> Hey, it might be interesting for managed mounts *really* to identify the >> filenames "foo" and "foo.exe". (Maybe they already do?) > > Huh? What do you mean by "identify" here? If you mean "equate", this > most likely won't happen. If you mean "differentiate", then that's > already happening even on non-managed mounts (hence the need for special > cp and install hacks). If you simply mean that *cp* (and install) should > not assume foo=foo.exe on managed mounts, then PTC. :-) I mean, that Windows special handling of .exe be invisible on managed mounts. So "equate" in that the Cygwin filename "foo" might be the actual file "foo.exe", but certainly not preventing a Cygwin filename "foo.exe" as well (which might or might have the .exe extension as an actual file). This would require that the coding of filenames allow the Cygwin filename to have an .exe extension, independently of whether the actual file has the .exe extension. Doubtless "chmod" would need to be able to change the actual filename when a file is made executable. As for install etc *not* assuming foo=foo.exe, that should be possible just by making "stat" not perform the translation on managed mounts. (Presumably Cygwin tools which perform special .exe handling, perform it when they encounter a file which one can stat, but which returns "No such file" on open.) > FWIW, WinNT/2k/XP allow executables to not have a .exe extension. I wasn't aware of it, and haven't been able to figure it out in a couple of minutes of playing around and Googling. How? Certainly I observe that Cygwin executes .exe files differently; if I rename a shell script to something.exe, it doesn't work very well at all. Robert -- 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/