Tue Feb 8 01:15:00 GMT 2005
On 17 Dec 2004 16:35:31 -0000 Christopher Faylor wrote:
> I'd like to note for the archives also that I'd like to get the real version
> of ksh into the cygwin distribution.
> This comes up from time to time. The first time it happened someone was insisting
> that they needed to change the cygwin DLL for this to happen and I had reservations
> about the licensing status of some of the changes since the person had also seen
> U/WIN sources. Then, somehow, ksh was built without the need to change cygwin and
> a cygwin ksh package was going to show up any second now.
> Well, years later, we still don't have a ksh.
> Anyone want to take the plunge?
Rather than waste time arguing about cygwin correctness, we added
section 2 system call intercepts to our base library to get cygwin to
act like unix. The library intercepts keep windows from contaminating
our mainline source and scripts. For details see
Since the last cygwin round AT&T ksh93, ast libraries, and UWIN source
and binaries have been released uder the OSI approved CPL 1.0
(Common Public License 1.0.) I packaged the 2005-02-02 standalone
ksh for cygwin and posted setup.hint, tarballs and md5 sums at
The packages under this URL are password protected. See
for the rationale and name and password to use (the same name and
password for every user.)
I believe previous ksh93 vs. cygwin issues mentioned on this list have
been addressed in this release.
I won't be the cygwin ksh93 maintainer, but I can supply cygwin
packages at the above URL to the maintainer, including any changes
required in the package files. All of our packages, including the
cygwin ones, are generated by table driven scripts, so any cygwin
specific package changes will be rolled back into those tables and
-- Glenn Fowler -- AT&T Research, Florham Park NJ --
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
More information about the Cygwin