ksh on cygwin

[Gary R. Van Sickle]

> -----Original Message-----
> From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com]On Behalf
> Of Karsten Fleischer
>
> 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.
> 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. My patch would solve this
> in an easy way.

Actually, I can easily see it causing much *more* trouble, because then there'd
be one more way to get things FUBAR.  Well actually more like Permutation(2) (or
whatever the notation is, God I'm getting old):

"Why is /bin/sh ash even though I set $SHELL to bash?"  "I replaced /bin/sh with
bash but I still get ash when I run a script."  Rinse, repeat.  I just don't see
how the cost:benefit works out on this one.

--
Gary R. Van Sickle
Brewer.  Patriot.


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