This is the mail archive of the
mailing list for the Cygwin project.
Re: bash vs sh in scripts
- From: ericblake at comcast dot net (Eric Blake)
- To: cygwin at cygwin dot com
- Date: Wed, 07 Dec 2005 20:29:21 +0000
- Subject: Re: bash vs sh in scripts
> /bin/sh should exist and be a hard-link to /bin/bash. If this is not
> the case you have an installation problem. The bash postinstall script
> should ensure this.
Actually, it should be a copy rather than a hard link, since hard links
can't be broken to be upgraded while the postinstall script is
running. But the postinstall takes care of that.
> /bin vs. /usr/bin is meaningless since they're the same under cygwin.
Unless you've messed with your mount points.
> If you have no /bin/sh you will run into countless problems all over the
> place, such as anything that calls system().
By the way, attaching the output of 'cygcheck -svr' would have
pointed out all of these issues.
volunteer cygwin bash maintainer
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html