Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Thu, 10 Jan 2002 20:41:16 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: ksh on cygwin
Message-ID: <20020111014116.GC2211@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20020110183618 DOT GD26493 AT redhat DOT com> <DIENLECHGMDAEJHGMEBCIEALCBAA DOT K DOT Fleischer AT omnium DOT de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <DIENLECHGMDAEJHGMEBCIEALCBAA.K.Fleischer@omnium.de>
User-Agent: Mutt/1.3.23.1i

On Fri, Jan 11, 2002 at 02:04:47AM +0100, Karsten Fleischer wrote:
>It's not a major change.  SUSv2 doesn't say that you have to use
>/bin/sh for a shell.  It even says that $SHELL can name the user's
>favorite shell.

Every UNIX system that I've ever seen uses /bin/sh.  The SUSv2 says that
system uses the 'sh' utility.  it doesn't say that it uses the SHELL
environment variable if certain prerequisites are met.

>I know that you always have trouble with users who copy /bin/bash to
>/bin/sh, it's a monthly issue on the mailing list.

Actually, I don't think this is a really big issue.

>My patch would solve this in an easy way.

This is not a new idea.  It has been discussed a lot over the years.  I
think this is one of the places where UWIN and Cygwin differ in matters
of philosophy.  I know that UWIN does a lot of extra stuff like this.
It's basically a matter of where you draw the line, I think.  I don't
see any reason to add this extra processing to cygwin.

cgf

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