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: Shankar Unni Subject: Re: file not working on executables? Date: Thu, 08 Sep 2005 13:19:50 -0700 Lines: 13 Message-ID: References: <20050907074223 DOT GA24333 AT calimero DOT vinschen DOT de> <20050908000030 DOT 9499B83C9A AT pessard DOT research DOT canon DOT com DOT au> <20050908072154 DOT GX5555 AT calimero DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Thunderbird/1.0.6 Mnenhy/0.7 In-Reply-To: <20050908072154.GX5555@calimero.vinschen.de> X-IsSubscribed: yes Corinna Vinschen wrote: > You should not mount the whole Cygwin tree in textmode Totally agree. But we need to do a "text mode install" from setup.exe because so many of the tools we use are non-Cygwin tools, and "cvs" does nasty (or at least unattractive) things if the mount is binmode, and the text file contains "^M"s. But this really applies only to the cygdrive mounts (since that's where the affected files live). What would be nice is if setup *always* mounted / and /usr/lib in binmode, and /usr/bin in "mount -x" mode, and only honored the "text mode" in the installer screen for the cygdrive mounts. -- 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/