Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com> List-Archive: <http://sourceware.cygnus.com/ml/cygwin/> List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com> List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs> Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com From: Chris Faylor <cgf AT cygnus DOT com> Date: Mon, 22 May 2000 14:52:41 -0400 To: cygwin AT sourceware DOT cygnus DOT com Subject: Re: How to undo damage caused by cygwin tool behavior Message-ID: <20000522145241.A8191@cygnus.com> Reply-To: cygwin AT sourceware DOT cygnus DOT com Mail-Followup-To: cygwin AT sourceware DOT cygnus DOT com References: <Pine DOT LNX DOT 4 DOT 10 DOT 10005221439040 DOT 15280-100000 AT rksystems DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <Pine.LNX.4.10.10005221439040.15280-100000@rksystems.com>; from bkline@rksystems.com on Mon, May 22, 2000 at 02:48:25PM -0400 On Mon, May 22, 2000 at 02:48:25PM -0400, Bob Kline wrote: >Through my own lack of attentiveness, I caused an installation of Cygwin >to be placed at the root of the D: drive of one of our servers (I had >been used to the practice of the older versions of installing themselves >with several layers of subdirectories under the real location of the >tools). This caused lots of our operations to break (for example, make >and rcsdiff) because the Cygwin tools, in spite of the statement in the >FAQ to the contrary, appear to process text files in binary mode, and >then choke on the carriage returns that standard editing tools insert in >the Microsoft world. Is there any way I can counteract this behavior, >or do I need to go back to the backup tapes and undo the damage by >removing the Cygwin tools from d:\bin? I've looked through the docs, >and I found the information on CYGWIN and "nobinmode" but that didn't >seem to have any effect, whether I was in a COMMAND shell or a bash >shell (and yes, I did set CYGWIN before invoking bash). Look at the documentation for the mount command. It should provide you with the information that you need. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com