X-Spam-Check-By:	sourceware.org
Date:	Wed, 7 Dec 2005 14:56:02 -0500
From:	David Arnstein <arnstein AT panix DOT com>
To:	cygwin AT cygwin DOT com
Subject:	bash vs sh in scripts
Message-ID:	<20051207195602.GA27946@panix.com>
Reply-To:	arnstein AT pobox DOT com
Mime-Version:	1.0
User-Agent:	Mutt/1.5.10i
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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

Some cygwin packages install shell scripts that begin with the line
	#!/bin/sh
The latest example is the smartd script that smartmontools installs in
/etc/rc.d/init.d. But there are many others. This seems to be standard
Linux usage.

On some of my PCs, this causes the shell script to fail. In most
cases, I can fix this by replacing the above line with
	#!/usr/bin/bash

I would like a canonical solution to this issue. Should I simply copy
/usr/bin/bash.exe to /bin/bash.exe? This has fixed the problem on one
of my PCs.

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

- Raw text -