Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <4205DC20.AEE603B2@dessent.net>
Date: Sun, 06 Feb 2005 00:58:08 -0800
From: Brian Dessent <brian AT dessent DOT net>
Organization: My own little world...
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Linux  Journal Cygwin article
References: <4204CF9D DOT 8070407 AT buddydog DOT org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

Jonathan Arnold wrote:
> 
> Interesting article in Linux Journal on Cygwin:
> 
> http://www.linuxjournal.com/article/8078

Unfortunately it's not written by someone very familiar with Cygwin. 
First these's this incorrect statement in the introduction:

"Cygwin does not enable your computer to understand UNIX signals,
pseudo-terminals (PTYs) and such; it only provides mappings of UNIX
actions to the Windows platform."

Perhaps he meant to say "it does not enable normal windows applications
to use signals and PTYs" but Cygwin most certainly supports them for
anything ported or compiled as a Cygwin app.

Then later on he advises on how to setup ssh manually, instead of just
running ssh-host-config which takes care of everything in one step.

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/