This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Linux Journal Cygwin article
- From: Christopher Faylor <cgf-no-personal-reply-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Sun, 6 Feb 2005 11:07:18 -0500
- Subject: Re: Linux Journal Cygwin article
- References: <4204CF9D.8070407@buddydog.org> <4205DC20.AEE603B2@dessent.net>
- Reply-to: cygwin at cygwin dot com
On Sun, Feb 06, 2005 at 12:58:08AM -0800, Brian Dessent wrote:
>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.
Yes, he should have been a little more careful copying my words from
the cygwin web site.
>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.
And the author actually gives some bad advice of not using the default
c:\cygwin root directory, claiming that we said it was best to do things
that way. Why would we have a program with a default that
we didn't want people to use?
cgf
--
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/