X-Spam-Check-By: sourceware.org
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Subject: RE: sh files
Date: Sun, 29 Oct 2006 16:24:57 -0500
Message-ID: <31DDB7BE4BF41D4888D41709C476B65704169293@NIHCESMLBX5.nih.gov>
In-Reply-To: <7064712.post@talk.nabble.com>
From: "Buchbinder, Barry \(NIH/NIAID\) [E]" <BBuchbinder AT niaid DOT nih DOT gov>
To: "dubcek" <goltrock AT wanadoo DOT fr>, <cygwin AT cygwin DOT com>
X-IsSubscribed: yes
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
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k9TLP7d4028035

From: dubcek, Sunday, October 29, 2006 3:00 PM
> Far from being a computer expert, here is what you need to know to
understand my problem.
> For years I worked basically in an UNIX environment. 
> For practical reasons, I am now using Windows XP. Two years ago, I
downloaded Cygwin in the hope of finding an UNIX-like environment. That
worked fine. 
> I got to use the cygwin version of the Lilypond music notation and
that too worked perfectly until the day when I found myself stuck with a
'very simple' problem' which is irrelevant to the present story.
> In order to solve that problem, I downloaded a more recent version of
cygwin.
> 
> My problem is this:
> From the time I started using UNIX, I have made at least a hundred
different .sh files, all of which ran perfectly on my first version of
cygwin. But they don't work on the new version.
> What do I do to make them work again?
> All clear and simple explanation is welcome. My computer education
lasted half an hour twenty-five years ago.
> Thanks for your patience.
> dubcek

Your problem sounds like line endings, specifically \r\n line endings on
binary mounts.  See
<http://cygwin.com/ml/cygwin-announce/2006-09/msg00006.html> and
<http://cygwin.com/ml/cygwin-announce/2006-10/msg00000.html>.

The mailing list over the past month
<http://cygwin.com/ml/cygwin/2006-10/> discusses ad nauseam problems
resulting from the changed behavior.  Look there for guidance.

While we're at this, thanks to Eric for all the work he puts into bash
and his other packages, and to his patience in dealing with the fallout
from this change.

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