Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Gerald S. Williams" To: Subject: RE: "==" operand not found Date: Thu, 24 Oct 2002 08:25:21 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal In-Reply-To: <7BFCE5F1EF28D64198522688F5449D5AD63A6D@xchangeserver2.storigen.com> Scott Prive wrote: > 1) Why is ash the default? At least on UNIX systems that use "true" > sh -- usually just /bin/bash in /bin/sh compatibility mode But bash in compatibility mode isn't true Bourne shell. For instance, /bin/sh on a Solaris box doesn't support the "==" operator either. This is a case where ASH is doing the right thing. If you put #!/bin/sh at the beginning of your script, you should only use pure Bourne shell commands. You'd do better with #!/usr/bin/bash instead. Or if bash isn't in /usr/bin on your Unix boxes, there may be some trick using #!/bin/sh along with a conditional exec (similar to the trick used in many Tcl scripts), but I'd have to think about it. -Jerry Williams -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/