ssh ProxyCommand not finding anything to execute

[SQueeZe]

Hi All
I am trying to connect to my home computer from work and I have to use the work HTTP proxy on port 443 in order to do so.  I have done this using PuTTY just fine so I know there is nothing wrong with my setup.  I have downloaded the windows binary of Connect and placed it in the same folder as the ssh binary (c:\cwrsync\bin).  If I try to run the connect command by itself in debug mode I can connect to the proxy and thus my home PC just fine:

bash-3.00$ connect -d -H proxy:8085 myhomepc 443
DEBUG: No direct address are specified.
DEBUG: relay_method = HTTP (3)
DEBUG: relay_host=proxy
DEBUG: relay_port=8085
DEBUG: relay_user=myuser
DEBUG: local_type=stdio
DEBUG: dest_host=myhomepc
DEBUG: dest_port=443
DEBUG: Program is $Revision: 100 $
DEBUG: checking myhomepc is for direct?
DEBUG: myhomepc for not direct.
DEBUG: resolving host by name: proxy
DEBUG: resolved: proxy (192.168.100.10)
DEBUG: connecting to 192.168.100.2:8085
DEBUG: begin_http_relay()
DEBUG: >>> "CONNECT myhomepc:443 HTTP/1.0\r\n"
DEBUG: >>> "\r\n"
DEBUG: <<< "HTTP/1.0 200 Connection established\r\n"
DEBUG: connected, start user session.
DEBUG: <<< "\r\n"
DEBUG: connected
DEBUG: start relaying.
DEBUG: recv 31 bytes
SSH-2.0-OpenSSH_4.3p2 Debian-9

DEBUG: sent 2 bytes
DEBUG: recv 19 bytes
Protocol mismatch.
DEBUG: connection closed by peer
DEBUG: relaying done.
DEBUG: that's all, bye.

I have installed cwRsync which has the OpenSSH client version 4.5.  I should be able to type in the following:

ssh -v -o ProxyCommand="connect -H -d proxy:8085 %h 443" user@myhomepc

However I get the following error:

OpenSSH_4.5p1, OpenSSL 0.9.8d 28 Sep 2006
debug1: Executing proxy command: exec connect.exe -H proxy:8085 myhomepc 443
debug1: permanently_drop_suid: 400
/bin/sh: No such file or directory
debug1: identity file /cygdrive/c/Documents and Settings/myuser/.ssh/identity type -1
debug1: identity file /cygdrive/c/Documents and Settings/myuser/.ssh/id_rsa type 1
debug1: identity file /cygdrive/c/Documents and Settings/myuser/.ssh/id_dsa type -1
ssh_exchange_identification: Connection closed by remote host

The problem is that it doesn't seem to be finding the connect binary.  If I remove all the "connect.exe...." stuff and just leave it as "" or put random stuff in there, I get exactly the same error.  C:\cwRsync\bin is in my PATH variable so I can type it from anywhere.
I have tried specifying the location with:
C:\cwRsync\bin\connect
/cygdrive/c/cwRsync/bin/connect
and I have tried copying the binary to various places on my hard drive to no avail.

My understanding is that I should get some output from Connect once it finds it as I have specified the -d flag.
What am I doing wrong?
Thanks
SQueeZe

[DePriest, Jason R.]

On 9/17/07, SQueeZe <> wrote:

>
> Hi All
> I am trying to connect to my home computer from work and I have to use the
> work HTTP proxy on port 443 in order to do so.  I have done this using PuTTY
> just fine so I know there is nothing wrong with my setup.  I have downloaded
> the windows binary of Connect and placed it in the same folder as the ssh
> binary (c:\cwrsync\bin).  If I try to run the connect command by itself in
> debug mode I can connect to the proxy and thus my home PC just fine:
>
> bash-3.00$ connect -d -H proxy:8085 myhomepc 443
>

- - -  deleted DEBUG - - -

> SSH-2.0-OpenSSH_4.3p2 Debian-9
>
> DEBUG: sent 2 bytes
> DEBUG: recv 19 bytes
> Protocol mismatch.
> DEBUG: connection closed by peer
> DEBUG: relaying done.
> DEBUG: that's all, bye.
>
> I have installed cwRsync which has the OpenSSH client version 4.5.  I should
> be able to type in the following:
>
> ssh -v -o ProxyCommand="connect -H -d proxy:8085 %h 443" user@myhomepc
>
> However I get the following error:
>
> OpenSSH_4.5p1, OpenSSL 0.9.8d 28 Sep 2006
> debug1: Executing proxy command: exec connect.exe -H proxy:8085 myhomepc 443
> debug1: permanently_drop_suid: 400
> /bin/sh: No such file or directory
> debug1: identity file /cygdrive/c/Documents and
> Settings/myuser/.ssh/identity type -1
> debug1: identity file /cygdrive/c/Documents and Settings/myuser/.ssh/id_rsa
> type 1
> debug1: identity file /cygdrive/c/Documents and Settings/myuser/.ssh/id_dsa
> type -1
> ssh_exchange_identification: Connection closed by remote host
>
> The problem is that it doesn't seem to be finding the connect binary.  If I
> remove all the "connect.exe...." stuff and just leave it as "" or put random
> stuff in there, I get exactly the same error.  C:\cwRsync\bin is in my PATH
> variable so I can type it from anywhere.
> I have tried specifying the location with:
> C:\cwRsync\bin\connect
> /cygdrive/c/cwRsync/bin/connect
> and I have tried copying the binary to various places on my hard drive to no
> avail.
>
> My understanding is that I should get some output from Connect once it finds
> it as I have specified the -d flag.
> What am I doing wrong?
> Thanks
> SQueeZe
> --

Hello.

I have used the ProxyConnect option successfully.  However, I do not
use your method.
Instead, I modify my ~/.ssh/config file to contain ProxyCommand
sections for specific IP addresses or hosts.
It might make your command line a little bit easier to read and would
elimiate potential quoting errors.

I am also using corkscrew instead of connect.exe for ProxyCommand and
I compiled it myself inside of cygwin.

See man ssh_config

Also
> Problem reports:       http://cygwin.com/problems.html

-Jason

--
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/

[SQueeZe]

Thanks for your reply Jason.
I have also tried putting it in a config file but it had the same result.  I ended up using the command-line just because I could be sure that it was using correct parameter.

I did look at corkscrew, however I couldn't find a precompiled download.  I know I can compile it but I dont have a full cygwin install, and I am trying to make it as simple for other people to follow.

I know I must be doing something really simply wrong, but I just can't think what it is!

Thanks again.

SQueeZe

DePriest, Jason R. wrote:

On 9/17/07, SQueeZe <> wrote:
>
> Hi All
> I am trying to connect to my home computer from work and I have to use the
> work HTTP proxy on port 443 in order to do so.  I have done this using PuTTY
> just fine so I know there is nothing wrong with my setup.  I have downloaded
> the windows binary of Connect and placed it in the same folder as the ssh
> binary (c:\cwrsync\bin).  If I try to run the connect command by itself in
> debug mode I can connect to the proxy and thus my home PC just fine:
>
> bash-3.00$ connect -d -H proxy:8085 myhomepc 443
>
- - -  deleted DEBUG - - -
> SSH-2.0-OpenSSH_4.3p2 Debian-9
>
> DEBUG: sent 2 bytes
> DEBUG: recv 19 bytes
> Protocol mismatch.
> DEBUG: connection closed by peer
> DEBUG: relaying done.
> DEBUG: that's all, bye.
>
> I have installed cwRsync which has the OpenSSH client version 4.5.  I should
> be able to type in the following:
>
> ssh -v -o ProxyCommand="connect -H -d proxy:8085 %h 443" user@myhomepc
>
> However I get the following error:
>
> OpenSSH_4.5p1, OpenSSL 0.9.8d 28 Sep 2006
> debug1: Executing proxy command: exec connect.exe -H proxy:8085 myhomepc 443
> debug1: permanently_drop_suid: 400
> /bin/sh: No such file or directory
> debug1: identity file /cygdrive/c/Documents and
> Settings/myuser/.ssh/identity type -1
> debug1: identity file /cygdrive/c/Documents and Settings/myuser/.ssh/id_rsa
> type 1
> debug1: identity file /cygdrive/c/Documents and Settings/myuser/.ssh/id_dsa
> type -1
> ssh_exchange_identification: Connection closed by remote host
>
> The problem is that it doesn't seem to be finding the connect binary.  If I
> remove all the "connect.exe...." stuff and just leave it as "" or put random
> stuff in there, I get exactly the same error.  C:\cwRsync\bin is in my PATH
> variable so I can type it from anywhere.
> I have tried specifying the location with:
> C:\cwRsync\bin\connect
> /cygdrive/c/cwRsync/bin/connect
> and I have tried copying the binary to various places on my hard drive to no
> avail.
>
> My understanding is that I should get some output from Connect once it finds
> it as I have specified the -d flag.
> What am I doing wrong?
> Thanks
> SQueeZe
> --

Hello.

I have used the ProxyConnect option successfully.  However, I do not
use your method.
Instead, I modify my ~/.ssh/config file to contain ProxyCommand
sections for specific IP addresses or hosts.
It might make your command line a little bit easier to read and would
elimiate potential quoting errors.

I am also using corkscrew instead of connect.exe for ProxyCommand and
I compiled it myself inside of cygwin.

See man ssh_config

Also
> Problem reports:       http://cygwin.com/problems.html

-Jason

--
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/

[SQueeZe]

OK, I have installed the full version of Cygwin and now it is working as expected.  I still need to get this working without a full installation of Cygwin though, so if anyone has any ideas, they would be greatfully received.



Thanks for your reply Jason.
I have also tried putting it in a config file but it had the same result.  I ended up using the command-line just because I could be sure that it was using correct parameter.

I did look at corkscrew, however I couldn't find a precompiled download.  I know I can compile it but I dont have a full cygwin install, and I am trying to make it as simple for other people to follow.

I know I must be doing something really simply wrong, but I just can't think what it is!

Thanks again.

SQueeZe

DePriest, Jason R. wrote:

On 9/17/07, SQueeZe <> wrote:
>
> Hi All
> I am trying to connect to my home computer from work and I have to use the
> work HTTP proxy on port 443 in order to do so.  I have done this using PuTTY
> just fine so I know there is nothing wrong with my setup.  I have downloaded
> the windows binary of Connect and placed it in the same folder as the ssh
> binary (c:\cwrsync\bin).  If I try to run the connect command by itself in
> debug mode I can connect to the proxy and thus my home PC just fine:
>
> bash-3.00$ connect -d -H proxy:8085 myhomepc 443
>
- - -  deleted DEBUG - - -
> SSH-2.0-OpenSSH_4.3p2 Debian-9
>
> DEBUG: sent 2 bytes
> DEBUG: recv 19 bytes
> Protocol mismatch.
> DEBUG: connection closed by peer
> DEBUG: relaying done.
> DEBUG: that's all, bye.
>
> I have installed cwRsync which has the OpenSSH client version 4.5.  I should
> be able to type in the following:
>
> ssh -v -o ProxyCommand="connect -H -d proxy:8085 %h 443" user@myhomepc
>
> However I get the following error:
>
> OpenSSH_4.5p1, OpenSSL 0.9.8d 28 Sep 2006
> debug1: Executing proxy command: exec connect.exe -H proxy:8085 myhomepc 443
> debug1: permanently_drop_suid: 400
> /bin/sh: No such file or directory
> debug1: identity file /cygdrive/c/Documents and
> Settings/myuser/.ssh/identity type -1
> debug1: identity file /cygdrive/c/Documents and Settings/myuser/.ssh/id_rsa
> type 1
> debug1: identity file /cygdrive/c/Documents and Settings/myuser/.ssh/id_dsa
> type -1
> ssh_exchange_identification: Connection closed by remote host
>
> The problem is that it doesn't seem to be finding the connect binary.  If I
> remove all the "connect.exe...." stuff and just leave it as "" or put random
> stuff in there, I get exactly the same error.  C:\cwRsync\bin is in my PATH
> variable so I can type it from anywhere.
> I have tried specifying the location with:
> C:\cwRsync\bin\connect
> /cygdrive/c/cwRsync/bin/connect
> and I have tried copying the binary to various places on my hard drive to no
> avail.
>
> My understanding is that I should get some output from Connect once it finds
> it as I have specified the -d flag.
> What am I doing wrong?
> Thanks
> SQueeZe
> --

Hello.

I have used the ProxyConnect option successfully.  However, I do not
use your method.
Instead, I modify my ~/.ssh/config file to contain ProxyCommand
sections for specific IP addresses or hosts.
It might make your command line a little bit easier to read and would
elimiate potential quoting errors.

I am also using corkscrew instead of connect.exe for ProxyCommand and
I compiled it myself inside of cygwin.

See man ssh_config

Also
> Problem reports:       http://cygwin.com/problems.html

-Jason

--
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/

[David Rothenberger]

On 9/17/2007 11:38 AM, SQueeZe wrote:
> I have installed cwRsync which has the OpenSSH client version 4.5.

You should probably ask for support from the cwRsync project.

 > I should be able to type in the following:
>
> ssh -v -o ProxyCommand="connect -H -d proxy:8085 %h 443" user@myhomepc
>
> However I get the following error:
>
> OpenSSH_4.5p1, OpenSSL 0.9.8d 28 Sep 2006
> debug1: Executing proxy command: exec connect.exe -H proxy:8085 myhomepc 443
> debug1: permanently_drop_suid: 400
> /bin/sh: No such file or directory

OpenSSH invokes "/bin/sh -c proxycmd" (see sshconnect.c line 98 in the
4.7 sources) and the cwRsync package does not include sh. Even if you
included sh.exe in your installation directory, I doubt it would work
because you won't have the Cygwin mount table setup so that /bin/sh
would map to the correct directory.

You really should raise this with the cwRsync developers.

--
David Rothenberger  ----  daveroth@...

Duty, n:
         What one expects from others.
                 -- Oscar Wilde


--
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/

[SQueeZe]

Thanks David, that is exactly what it is.  It seems so obvious in the cold light of day!  I have contacted the cwRsync guys to see if they can include it.

Thanks again for your help.

David Rothenberger wrote:

On 9/17/2007 11:38 AM, SQueeZe wrote:
> I have installed cwRsync which has the OpenSSH client version 4.5.

You should probably ask for support from the cwRsync project.

 > I should be able to type in the following:
>
> ssh -v -o ProxyCommand="connect -H -d proxy:8085 %h 443" user@myhomepc
>
> However I get the following error:
>
> OpenSSH_4.5p1, OpenSSL 0.9.8d 28 Sep 2006
> debug1: Executing proxy command: exec connect.exe -H proxy:8085 myhomepc 443
> debug1: permanently_drop_suid: 400
> /bin/sh: No such file or directory

OpenSSH invokes "/bin/sh -c proxycmd" (see sshconnect.c line 98 in the
4.7 sources) and the cwRsync package does not include sh. Even if you
included sh.exe in your installation directory, I doubt it would work
because you won't have the Cygwin mount table setup so that /bin/sh
would map to the correct directory.

You really should raise this with the cwRsync developers.

--
David Rothenberger  ----  [e-mail]

Duty, n:
         What one expects from others.
                 -- Oscar Wilde


--
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/

[SQueeZe]

Lets say I just drop sh.exe into the installation folder, what else would I need to do?

I have taken the sh.exe file from a cywgin install and put it into c:\bin\, and tried running my command again.  Now it no longer complains that it can't find /bin/sh but it still doesn't print anything to the screen like it should.  Obviously putting it in c:\bin isn't ideal, I need to point it to my cwRsync directory.

I have emailed the cwRsync guys the problem but I'm not sure if they will be willing to include sh.exe in the next release or not.

Thanks for your help
Kevin

David Rothenberger wrote:

On 9/17/2007 11:38 AM, SQueeZe wrote:
> I have installed cwRsync which has the OpenSSH client version 4.5.

You should probably ask for support from the cwRsync project.

 > I should be able to type in the following:
>
> ssh -v -o ProxyCommand="connect -H -d proxy:8085 %h 443" user@myhomepc
>
> However I get the following error:
>
> OpenSSH_4.5p1, OpenSSL 0.9.8d 28 Sep 2006
> debug1: Executing proxy command: exec connect.exe -H proxy:8085 myhomepc 443
> debug1: permanently_drop_suid: 400
> /bin/sh: No such file or directory

OpenSSH invokes "/bin/sh -c proxycmd" (see sshconnect.c line 98 in the
4.7 sources) and the cwRsync package does not include sh. Even if you
included sh.exe in your installation directory, I doubt it would work
because you won't have the Cygwin mount table setup so that /bin/sh
would map to the correct directory.

[Larry Hall (Cygwin)]

SQueeZe wrote:
> Lets say I just drop sh.exe into the installation folder, what else would I
> need to do?
>
> I have taken the sh.exe file from a cywgin install and put it into c:\bin\,
> and tried running my command again.  Now it no longer complains that it
> can't find /bin/sh but it still doesn't print anything to the screen like it
> should.  Obviously putting it in c:\bin isn't ideal, I need to point it to
> my cwRsync directory.


Really, this is off-topic for this list.  You should be talking to the
cwRsync guys about this.  We don't have any knowledge of what cwRsync does
or the requirements to make it work, even though it claims to be
Cygwin-based.  So you're better off talking with the maintainers of this
tool.

Aside: A quick read of the web site doesn't leave me with the impression
that this is any more than a repackaged version of a subset of the
Cygwin-provided tools.  Since repackaging Cygwin tools just results in
incompatibilities with the stock Cygwin toolset, I don't see any advantage
to installing cwRsync.  I'd recommend just using the rsync package as
provided with Cygwin.  If you have problems with that, you have this list
and it's archives to help you out.


> I have emailed the cwRsync guys the problem but I'm not sure if they will be
> willing to include sh.exe in the next release or not.


Since doing so would simply add to the incompatibilities between cwRsync and
the stock Cygwin installation, I hope not.


--
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      [phone] - RFK Office
216 Dalton Rd.                          [phone] - FAX
Holliston, MA 01746

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
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/

[SQueeZe]

Thanks for your reply Larry, I will continue with the cwRsync guys.

The 'advantage' of a package like cwRsync is that most Windows users wouldn't understand or want to dabble with a cywgin install and the intricacies that go along with it. cwRsync can be installed in about 10 seconds, and requires no knowledge of *Nix; I don't think the same could be said of Cygwin.  Although I love Cygwin, if you just want a tiny, single subset of its functionality, then it just isn't worth the full install.

Of course this has it's disadvantages as we are finding out now.....

Thanks again for your help.

Kevin

Larry Hall (Cygwin) wrote:

SQueeZe wrote:
> Lets say I just drop sh.exe into the installation folder, what else would I
> need to do?
>
> I have taken the sh.exe file from a cywgin install and put it into c:\bin\,
> and tried running my command again.  Now it no longer complains that it
> can't find /bin/sh but it still doesn't print anything to the screen like it
> should.  Obviously putting it in c:\bin isn't ideal, I need to point it to
> my cwRsync directory.


Really, this is off-topic for this list.  You should be talking to the
cwRsync guys about this.  We don't have any knowledge of what cwRsync does
or the requirements to make it work, even though it claims to be
Cygwin-based.  So you're better off talking with the maintainers of this
tool.

Aside: A quick read of the web site doesn't leave me with the impression
that this is any more than a repackaged version of a subset of the
Cygwin-provided tools.  Since repackaging Cygwin tools just results in
incompatibilities with the stock Cygwin toolset, I don't see any advantage
to installing cwRsync.  I'd recommend just using the rsync package as
provided with Cygwin.  If you have problems with that, you have this list
and it's archives to help you out.


> I have emailed the cwRsync guys the problem but I'm not sure if they will be
> willing to include sh.exe in the next release or not.


Since doing so would simply add to the incompatibilities between cwRsync and
the stock Cygwin installation, I hope not.


--
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      [phone] - RFK Office
216 Dalton Rd.                          [phone] - FAX
Holliston, MA 01746

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
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/

[Christopher Faylor-8]

On Wed, Sep 19, 2007 at 08:53:21AM -0700, SQueeZe wrote:

>Thanks for your reply Larry, I will continue with the cwRsync guys.
>
>The 'advantage' of a package like cwRsync is that most Windows users
>wouldn't understand or want to dabble with a cywgin install and the
>intricacies that go along with it.  cwRsync can be installed in about
>10 seconds, and requires no knowledge of *Nix; I don't think the same
>could be said of Cygwin.  Although I love Cygwin, if you just want a
>tiny, single subset of its functionality, then it just isn't worth the
>full install.
>
>Of course this has it's disadvantages as we are finding out now.....

And these would not be disadvantages as far as this project or this
mailing list are concerned.  We don't really care about people who only
want a tiny subset of the functionality we provide and don't want to
know anything about Cygwin or Linux/UNIX.

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/

[Larry Hall (Cygwin)]

SQueeZe wrote:

> Thanks for your reply Larry, I will continue with the cwRsync guys.
>
> The 'advantage' of a package like cwRsync is that most Windows users
> wouldn't understand or want to dabble with a cywgin install and the
> intricacies that go along with it. cwRsync can be installed in about 10
> seconds, and requires no knowledge of *Nix; I don't think the same could be
> said of Cygwin.  Although I love Cygwin, if you just want a tiny, single
> subset of its functionality, then it just isn't worth the full install.
>
> Of course this has it's disadvantages as we are finding out now.....
>
> Thanks again for your help.

I'm confused by the perception that Cygwin is an "all or nothing" deal.
It's certainly possible to set up a package server that doles out just a
subset of the entire distribution.  'setup.exe' does this now.  The default
set of packages is far less than the whole distribution.  Any package server
with its own 'setup.ini' can define a larger or smaller set of default
packages.  'setup.exe' will install only those defaults if the user doesn't
select any others.  I don't see where any of that requires special
knowledge.  But since cwRsync is still a Cygwin-based app, I also don't see
how one can get away from the fact that it's based in Cygwin and has its
roots in Unix/Linux/POSIX environments.  This would show through even with a
vanilla Windows port.

All that said, there's still no reason a third-party can't "go it's own
way".  Personally, I'd rather see them add value by working with Cygwin
instead of against it.  But I like synergy. ;-)



--
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      [phone] - RFK Office
216 Dalton Rd.                          [phone] - FAX
Holliston, MA 01746

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
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/