Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com From: Chris Faylor Date: Thu, 18 May 2000 12:18:17 -0400 To: cygwin@sourceware.cygnus.com Subject: Re: 'mount -t' problems in 1.1.1? Message-ID: <20000518121817.A10769@cygnus.com> Reply-To: cygwin@sourceware.cygnus.com Mail-Followup-To: cgf@cygnus.com, cygwin@sourceware.cygnus.com References: <20000518152849.27162.qmail@web805.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.12i In-Reply-To: <20000518152849.27162.qmail@web805.mail.yahoo.com>; from rick_rankin@yahoo.com on Thu, May 18, 2000 at 08:28:48AM -0700 On Thu, May 18, 2000 at 08:28:48AM -0700, Rick Rankin wrote: >Well, I'm currently using 1.1.0 with the 04/23 snapshot and all of my mounts >are text mounts. Also, all of my Makefiles have \r\n line endings. If I upgrade >to 1.1.1, my Makefiles stop working until I remove the CRs, after which they >work fine. > >Another example is my .bash_profile, which also has \r\n line endings. When I >upgrade to 1.1.1, I get all sorts of complaints about commands not found until >I remove the CRs. Then it works fine. > >It seems to me that if you add CRs to your .bash_profile or .bashrc, you should >see the problem immediately. In the meantime, I'll try to think of a way to be >more specific. I think that's specific enough. Thanks. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com