Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
From: Chris Faylor <cgf@cygnus.com>
Date: Tue, 19 Sep 2000 07:15:09 -0400
To: cygwin@sourceware.cygnus.com
Subject: Re: Link "bash" to "ksh" to be more "portable"?
Message-ID: <20000919071509.C27571@cygnus.com>
Reply-To: cygwin@sources.redhat.com
Mail-Followup-To: cygwin@sourceware.cygnus.com
References: <uyn1h5qta3.fsf@tcsi.com> <39C7148F.EAE9F548@cern.ch>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.6i
In-Reply-To: <39C7148F.EAE9F548@cern.ch>; from lassi.tuura@cern.ch on Tue, Sep 19, 2000 at 09:23:59AM +0200

On Tue, Sep 19, 2000 at 09:23:59AM +0200, Lassi A. Tuura wrote:
>> Is it reasonable to link "bash.exe" to "ksh.exe" in the Cygwin
>> distribution?  Is there any feature in Korn shell that is NOT in Bash,
>> or any other reason why this might be a bad thing to do?
>
>IIRC, zsh has a mode to emulate ksh, and will do so automatically if it
>starts as "ksh"-named process.  There have been messages about porting
>zsh to cygwin on this list, so take a look around to see if you can find
>the port.  Then create a symlink ksh to zsh or just copy the program to
>ksh.  Haven't tried that though.

Why not just use pdksh?  I'd have more confidence that something with "ksh"
in its name would emulate ksh more precisely.

I don't know if anyone has ported it, but I wouldn't be surprised.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com