Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Thu, 10 Jan 2002 20:41:16 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: ksh on cygwin Message-ID: <20020111014116.GC2211@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20020110183618.GD26493@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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/