X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <4C90FD69.5020100@cygwin.com> References: <20100915120315.GQ15121@calimero.vinschen.de> <20100915135030.GR15121@calimero.vinschen.de> <20100915140721.GS15121@calimero.vinschen.de> <4C90FD69.5020100@cygwin.com> Date: Wed, 15 Sep 2010 19:28:44 +0200 Message-ID: Subject: Re: .exe magic reloaded 2 From: Al To: cygwin@cygwin.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com >> 1.) When a file is made executable .exe is appended, but only visible >> from Windows API. > How would this work with non-Cygwin programs? =A0They wouldn't be handled > under > (1). Depends on how you install or mount them. But yes, as a prerequest there would be two types of filessystem handling. The "normal" windows one, always with .exe suffix stored into the filename of executables. When mounting foreign unix filesystems no .exe magic would be used at all on them. Al -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple