Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Wed, 10 Jul 2002 05:40:39 +0200 From: Thomas Baker To: cygwin AT cygwin DOT com Subject: Re: running mks toolkit and cygwin on same machine Message-ID: <20020710054039.A1832@mail.gmd.de> Mail-Followup-To: Thomas Baker , cygwin AT cygwin DOT com References: <3D2B06C2 DOT 4090608 AT telesoft DOT com> <3 DOT 0 DOT 6 DOT 32 DOT 20020709173509 DOT 00aa6930 AT phoenix DOT projtech DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3.0.6.32.20020709173509.00aa6930@phoenix.projtech.com>; from pablo@projtech.com on Tue, Jul 09, 2002 at 05:35:09PM +0000 On Tue, Jul 09, 2002 at 05:35:09PM +0000, Paul Coltrin wrote: > >From my limited experience, they seem to co-exist reasonably well. > But it depends on what you need to do. Unless it has changed very > recently, the Cygwin installer does not contain a ksh. I have > downloaded and installed the ATT ksh into my Cygwin installation but > I am finding that converting scripts from MKS ksh to Cygwin/ATT ksh > is not trivial. After installing Cygwin on a WIN2000 system with an existing MKS installation, the two installations seemed to "lock horns". I was able to establish peace by removing the MKS-related environment variables from the system configuration (Start -> Settings -> Control Panel -> System -> Advanced -> Environment Variables) and moving them into profile.ksh. Specifically: MKS_TK_PATH_BACK NUTCROOT ROOTDIR SHELL TERM (value had been "nutc") TERMCAP (value had been "E:\MKS\etc\termcap") TERMINFO (value had been "E:\MKS\usr\lib\terminfo") In particular, the TERM* values seemed to be causing of alot of the problems; Cygwin likes TERM=cygwin. I also installed the ATT ksh -- there was a thread about this two or three weeks ago -- but understand that a KSH package for the standard Cygwin setup is on the way. Have also had some small problems porting scripts, one of which being that "egrep" must always be changed to "grep -E". Tom -- Dr. Thomas Baker Thomas DOT Baker AT bi DOT fhg DOT de Institutszentrum Schloss Birlinghoven mobile +49-171-408-5784 Fraunhofer-Gesellschaft work +49-30-8109-9027 53754 Sankt Augustin, Germany fax +49-2241-144-1408 -- 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/