X-Spam-Check-By: sourceware.org
Date: Fri, 29 Sep 2006 10:24:24 -0400 (EDT)
From: Igor Peshansky <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: Eric Blake <ebb9 AT byu DOT net>
cc: cygwin AT cygwin DOT com, Dan_Wilks AT intuit DOT com
Subject: Re: Similar Bash 3.1.18 CR/LF Problem
In-Reply-To: <451C8D98.4030302@byu.net>
Message-ID: <Pine.GSO.4.63.0609291023160.8141@access1.cims.nyu.edu>
References: <657A9BE009D3504AAE29BD8E8C2DD61E01A5ABDB AT SDGEXEVS02 DOT corp DOT intuit DOT net>  <451C8D98 DOT 4030302 AT byu DOT net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Thu, 28 Sep 2006, Eric Blake wrote:

> According to Wilks, Dan on 9/28/2006 3:59 PM:
> >
> > That was my guess.  But since this was the cygwin installer run off
> > of the cygwin site I thought I'd mention it, if for no other reason
> > than tracking purposes.  Maybe there's a problem with the installer /
> > postinstall script when downgrading? Or perhaps that's intended
> > behavior.  It was just surprising.
>
> It's intended behavior; the postinstall script was not written with
> downgrades in mind (I may rethink that for my next release; but, it won't
> help you, because downgrading to 3.1-8 or earlier will not have this patch).
>
> >
> > And... it didn't run again when re-upgrading just bash to the new
> > (broken) version so we had to manually copy bash.exe to sh.exe.
>
> What makes you think the current version is broken?  In my opinion, it
> works just fine.  However, your discovery that using Windows paths
> instead of POSIX paths makes cygwin revert to binary file opens on text
> mounts is rather interesting.  I don't know if cygwin1.dll is at fault
> for that strange behavior.  It may be possible for me to patch bash to
> always convert script names to POSIX before opening them, so that you
> would get the right mount behavior, but I'm not looking forward to such
> a hack.

IIRC, Cygwin explicitly treats out-of-mount (Win32) paths as binary.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_	    pechtcha AT cs DOT nyu DOT edu | igor AT watson DOT ibm DOT com
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

--
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/