head	1.6;
access;
symbols
	TIGRIS_1_1_0RC2:1.3
	TIGRIS_1_1_0RC1:1.3
	TIGRIS_1_1:1.3.0.4
	TIGRIS_1_0_8:1.3
	TIGRIS_1_0_8RC3:1.3
	TIGRIS_1_0_8RC2:1.3
	TIGRIS_1_0_8RC1:1.3
	TIGRIS_1_0_7:1.3
	TIGRIS_1_0_7RC3:1.3
	TIGRIS_1_0_7RC2:1.3
	TIGRIS_1_0_7RC1:1.3
	TIGRIS_1_0_6:1.3
	TIGRIS_1_0_6RC5:1.3
	TIGRIS_1_0_6RC4:1.3
	TIGRIS_1_0_6RC3:1.3
	TIGRIS_1_0_6RC2:1.3
	TIGRIS_1_0_6RC1:1.3
	TIGRIS_1_0_5:1.3
	TIGRIS_1_0_5RC6:1.3
	TIGRIS_1_0_5RC5:1.3
	TIGRIS_1_0_5RC4:1.3
	TIGRIS_1_0_5RC3:1.3
	TIGRIS_1_0_5RC2:1.3
	TIGRIS_1_0_5RC1:1.3
	TIGRIS_1_0_4:1.3
	TIGRIS_1_0_3:1.3
	TIGRIS_1_0_2:1.3
	TIGRIS_1_0_1:1.3
	TIGRIS_1_0:1.3.0.6
	TIGRIS_1_0_0:1.3
	TIGRIS_1_0_0_RC1:1.3.0.2;
locks; strict;
comment	@# @;


1.6
date	2001.08.27.23.33.07;	author tberry;	state Exp;
branches;
next	1.5;

1.5
date	2001.06.21.07.07.40;	author jefflove;	state Exp;
branches;
next	1.4;

1.4
date	2001.06.11.03.14.33;	author jefflove;	state Exp;
branches;
next	1.3;

1.3
date	2001.03.13.06.25.58;	author lori;	state Exp;
branches;
next	1.2;

1.2
date	2001.02.11.18.29.47;	author jrobbins;	state Exp;
branches;
next	1.1;

1.1
date	2001.01.29.19.38.23;	author lori;	state Exp;
branches;
next	;


desc
@@


1.6
log
@fixed broken links.
Issue number:
Obtained from:
Submitted by:
Reviewed by:
@
text
@  <div class="docs" id="ddsshguidecygwin">
   <h2>SSH tunneling using Cygwin: The Desktop Unix Emulator</h2>

   <div class="toc">
    <h3>SSH Guide: Index</h3>

    <ul>
     <li>
      <a href="ddSSHGuide.html">About this guide</a> 

      <ul>
       <li><a href="ddSSHGuide.html#aboutssh">About SSH</a></li>

       <li><a href="ddSSHGuide.html#furtherdocumentation">Further documentation</a></li>
      </ul>
     </li>

     <li><a href="ddSSHGuideConcepts.html">Concepts</a></li>

     <li><a href="ddSSHGuideTerminals.html">Choosing the desktop terminal</a></li>

     <li>
      <a href="ddSSHGuideTerminals.html">Using the Desktop Terminal</a> 

      <ul>
       <li><a href="ddSSHGuideTerminals.html#macs">Macintosh</a></li>

       <li><a href="ddSSHGuideTerminals.html#windows">Windows</a></li>

       <li><a href="ddSSHGuideTerminals.html#othersshclients">Other SSH clients</a></li>
      </ul>
     </li>

     <li><strong>You are here:</strong> Tunneling using Cygwin: The Desktop Unix Emulator</li>

     <li><a href="ddSSHGuideterminating.html">Terminating the tunnel</a></li>
    </ul>
   </div>

   <div class="courtesylinks">
    <p><a href="/servlets/HelpTOC">Back to main Help index</a></p>
   </div>

   <h3><a id="installation" name="installation">Installation</a></h3>

   <p>Before we can tunnel with Cygwin, it must be correctly installed.</p>

   <p>The most important consideration for installing Cygwin is creating the appropriate Unix folders. Cygwin's <a href="http://www.cygwin.com/">website</a> offers complete and detailed instructions; the below is an abbreviated version.</p>

   <ul>
    <li>Download and install Cygwin. Cygnus gives you the option of installing from the Web, but it is faster (and ultimately more efficient) to install from a local disk. So just download and save the file somewhere you can easily find it.</li>

    <li>Click on Cygwin's "setup.exe" icon and follow the instructions, accepting the defaults. At some point, you will be asked for text format and whether you want Cygwin to be for yourself alone or to be shared. It doesn't matter whether you choose DOS or Unix, but for the sake of ease of use, choose Unix and "All." Cygwin will then install, and should create icons in your start file as well as on your desktop. If it doesn't, run setup again. Nothing will be installed if nothing needs to be, but it will take you to the end, where you can check the boxes indicating you want the icons installed. Check them.</li>

    <li>At this point, you need to create the Unix folders. You can create the standard directories from within Cygwin, as Cygwin's configuration instructions suggest (<a href="http://www.cygwin.com/cygwin-ug-net/setup-dir.html">http://www.cygwin.com/cygwin-ug-net/setup-dir.html</a>), or you can set them up from within Windows. Using the Windows method has some advantages, especially for people who are not entirely familiar with Unix commands and protocols. Since Cygwin is able to read both Win32 (Windows) file paths as well as Unix ones (POSIX), it doesn't much matter how you do it.</li>

    <li>Very clear instructions for creating the Unix directories can be found at <a href="http://www.woodsoup.org/projs/ORKiD/basic.htm">http://www.woodsoup.org/projs/ORKiD/basic.htm</a>. Although the instructions are specifically for a slightly earlier version of the program, they still obtain: the typical Unix directories must still be created.</li>

    <li>As well, the cygwin.bat file needs to be modified. Cygnus suggests that other files, too, need modification; but of these, the .bat file, which specifies the commands and their sequence that bash must go through, needs immediate modification.</li>

    <li>Configure your cygwin.bat file using Windows' Notepad utility or other text editor (not Microsoft Word or anything that imparts formatting) so that it looks something like this:</li>
   </ul>
<pre>
<code>@@ECHO OFF
    SET MAKE_MODE=Unix
    SET CYGWIN=notty
    SET HOME=C:\unix\HOME\[your home directory name]
    SET TERM=VT100
    CHDIR C:\Unix\HOME\[your home directory name]
    SET PATH=C:\Unix\BIN;C:\Unix\USR\LOCAL\BIN;C:\CYGWIN\BIN;%PATH%
    BASH</code>
  
</pre>

   <ul>
    <li>Where the "unix" directory on the "C" drive contains the traditional Unix directories. You can name it anything you want, as long a you do not use anything that confuses Unix, e.g., hyphens, spaces, etc.</li>

    <li>You should now have the C:\Cygwin directories, and your own C:\unix directories, which include your crucial home directory.</li>

    <li>There is still one more, optional, step. For Cygwin to run efficiently, you might want to configure the shortcut icon on your desktop so that it starts the program in the right directory. This is not necessary, if you have stipulated the HOME directory in the .bat file.</li>

    <li>Cygwin offers some further refinements, and, to be sure, there will doubtless be some tweaking you will have to do to make have the program running efficiently. Again, if you are familiar with Unix commands and file structures, you will find this easy; if you are not, Cygwin is quite forgiving, and you can get started with a minimum of fuss.</li>
   </ul>

   <h3><a id="tunneling" name="tunneling">Tunneling</a></h3>

   <ul>
    <li>First, begin the program.</li>

    <li>At the prompt, enter "<code>ssh -x -L 2401:localhost:2401 tunnel@@thisdomain.com</code>"</li>

    <li>The server should ask you for your password. Enter it. It is "<code>tunnel</code>"</li>

    <li>
     If this is your first time, the server will send you a message along these lines: 

     <ul>
      <li><code>Host key not found from the list of known hosts.</code></li>

      <li><code>Are you sure you want to continue connecting (yes/no)?</code></li>
     </ul>
    </li>

    <li>Enter "<code>Yes</code>." You can't just enter "y"; you have to spell it out.</li>

    <li>The server will then respond with: "<code>Host "thisdomain.com" added to the list of known hosts.</code>"</li>

    <li>The screen does not show a prompt. That's how it should be. The tunnel has been established. You are now ready to begin using CVS.</li>

    <li>You can, at this point, minimize the terminal, but do not close it or enter <code>Ctrl-C (^C)</code>. Doing so will kill the terminal tunnel.</li>
   </ul>

   <div class="courtesylinks">
    <p><a href="/servlets/HelpTOC">Back to main Help index</a></p>
   </div>
  </div>
 


@


1.5
log
@html usage revision
@
text
@d12 1
a12 1
       <li><a href="ddSSHGuide#aboutssh">About SSH</a></li>
d14 1
a14 1
       <li><a href="ddSSHGuide#furtherdocumentation">Further documentation</a></li>
@


1.4
log
@extensive markup rework - first pass toward house xhtmlification
@
text
@d1 2
a2 6
<!DOCTYPE html PUBLIC "-//CollabNet//DTD XHTML 1.0 Transitional//EN"
"http://collabnet.com/dtds/collabnet_transitional_10.dtd">
<html>
 <head>
  <title>SSH tunneling using Cygwin</title>
 </head>
d4 2
a5 3
 <body>
 <div class="docs" id="docid">
  <h2>SSH tunneling using Cygwin: The Desktop Unix Emulator</h2>
d7 3
a9 1
  <p>SSH Guide: Index</p>
d11 2
a12 4
  <ul>
   <li>
    <dl>
     <dt><a href="ddSSHGuide.html">About this guide</a></dt>
d14 3
a16 3
     <dd><a href="ddSSHGuide.html#aboutssh">About SSH</a></dd>
    </dl>
   </li>
d18 1
a18 5
   <li>
    <dl>
     <dd><a href="ddSSHGuide.html#furtherdocumentation">Further documentation</a></dd>
    </dl>
   </li>
d20 1
a20 3
   <li>
    <dl>
     <dt><a href="ddSSHGuideConcepts.html">Concepts</a></dt>
d22 2
a23 1
     <dt><a href="ddSSHGuideChoosing.html">Choosing the desktop terminal</a></dt>
d25 2
a26 1
     <dt><a href="ddSSHGuideTerminals.html">Using the desktop terminal</a></dt>
d28 1
a28 1
     <dd><a href="ddSSHGuideTerminals.html#macs">Macintosh</a></dd>
d30 3
a32 1
     <dd><a href="ddSSHGuideTerminals.html#windows">Windows</a></dd>
d34 1
a34 1
     <dt class="c2">You are here: Tunneling using Cygwin: The Desktop Unix Emulator</dt>
d36 3
a38 12
     <dd class="c3"><a href="#installation">Installation</a></dd>

     <dd class="c3"><a href="#tunneling">Tunneling</a></dd>

     <dt><a href="ddSSHGuideterminating.html">Terminating the tunnel</a></dt>
    </dl>
   </li>
  </ul>

  <div class="courtesylinks">
 <div class="courtesylinks"><a href="/servlets/HelpTOC">Back to main Help index</a></div>
  </div>
d40 3
a42 1
  <h3><a id="installation" name="installation">Installation</a></h3>
d44 1
a44 1
  <p>Before we can tunnel with Cygwin, it must be correctly installed.</p>
d46 1
a46 1
  <p>The most important consideration for installing Cygwin is creating the appropriate Unix folders. Cygwin's <a href="http://www.cygwin.com/">website</a> offers complete and detailed instructions; the below is an abbreviated version.</p>
d48 1
a48 2
  <ul>
   <li>Download and install Cygwin. Cygnus gives you the option of installing from the Web, but it is faster (and ultimately more efficient) to install from a local disk. So just download and save the file somewhere you can easily find it.</li>
d50 2
a51 1
   <li>Click on Cygwin's "setup.exe" icon and follow the instructions, accepting the defaults. At some point, you will be asked for text format and whether you want Cygwin to be for yourself alone or to be shared. It doesn't matter whether you choose DOS or Unix, but for the sake of ease of use, choose Unix and "All." Cygwin will then install, and should create icons in your start file as well as on your desktop. If it doesn't, run setup again. Nothing will be installed if nothing needs to be, but it will take you to the end, where you can check the boxes indicating you want the icons installed. Check them.</li>
d53 1
a53 1
   <li>At this point, you need to create the Unix folders. You can create the standard directories from within Cygwin, as Cygwin's configuration instructions suggest (<a href="http://www.cygwin.com/cygwin-ug-net/setup-dir.html">http://www.cygwin.com/cygwin-ug-net/setup-dir.html</a>), or you can set them up from within Windows. Using the Windows method has some advantages, especially for people who are not entirely familiar with Unix commands and protocols. Since Cygwin is able to read both Win32 (Windows) file paths as well as Unix ones (POSIX), it doesn't much matter how you do it.</li>
d55 1
a55 1
   <li>Very clear instructions for creating the Unix directories can be found at <a href="http://www.woodsoup.org/projs/ORKiD/basic.htm">http://www.woodsoup.org/projs/ORKiD/basic.htm</a>. Although the instructions are specifically for a slightly earlier version of the program, they still obtain: the typical Unix directories must still be created.</li>
d57 1
a57 1
   <li>As well, the cygwin.bat file needs to be modified. Cygnus suggests that other files, too, need modification; but of these, the .bat file, which specifies the commands and their sequence that bash must go through, needs immediate modification.</li>
d59 1
a59 2
   <li>Configure your cygwin.bat file using Windows' Notepad utility or other text editor (not Microsoft Word or anything that imparts formatting) so that it looks something like this:</li>
  </ul>
d61 4
a64 1
  <pre><code>@@ECHO OFF
d72 5
a76 1
   </pre>
d78 1
a78 2
  <ul>
   <li>Where the "unix" directory on the "C" drive contains the traditional Unix directories. You can name it anything you want, as long a you do not use anything that confuses Unix, e.g., hyphens, spaces, etc.</li>
d80 1
a80 1
   <li>You should now have the C:\Cygwin directories, and your own C:\unix directories, which include your crucial home directory.</li>
d82 2
a83 1
   <li>There is still one more, optional, step. For Cygwin to run efficiently, you might want to configure the shortcut icon on your desktop so that it starts the program in the right directory. This is not necessary, if you have stipulated the HOME directory in the .bat file.</li>
d85 1
a85 2
   <li>Cygwin offers some further refinements, and, to be sure, there will doubtless be some tweaking you will have to do to make have the program running efficiently. Again, if you are familiar with Unix commands and file structures, you will find this easy; if you are not, Cygwin is quite forgiving, and you can get started with a minimum of fuss.</li>
  </ul>
d87 2
a88 1
  <h3><a id="tunneling" name="tunneling">Tunneling</a></h3>
d90 1
a90 2
  <ul>
   <li>First, begin the program.</li>
d92 1
a92 1
   <li>At the prompt, enter "<code>ssh -x -L 2401:localhost:2401 tunnel@@thisdomain.com</code>"</li>
d94 2
a95 1
   <li>The server should ask you for your password. Enter it. It is "<code>tunnel</code>"</li>
d97 2
a98 2
   <li>
    If this is your first time, the server will send you a message along these lines: 
d100 3
a102 2
    <ul>
     <li><code>Host key not found from the list of known hosts.</code></li>
d104 1
a104 3
     <li><code>Are you sure you want to continue connecting (yes/no)?</code></li>
    </ul>
   </li>
d106 1
a106 1
   <li>Enter "<code>Yes</code>." You can't just enter "y"; you have to spell it out.</li>
d108 1
a108 1
   <li>The server will then respond with: "<code>Host "thisdomain.com" added to the list of known hosts.</code>"</li>
d110 2
a111 1
   <li>The screen does not show a prompt. That's how it should be. The tunnel has been established. You are now ready to begin using CVS.</li>
d113 5
a117 6
   <li>You can, at this point, minimize the terminal, but do not close it or enter <code>Ctrl-C (^C)</code>. Doing so will kill the terminal tunnel.</li>
  </ul>
<div class="courtesylinks"><a href="/servlets/HelpTOC">Back to main Help index</a></div>
 </div>
</body>
</html>
@


1.3
log
@fixing links; conforming index and style with rest of help docs
@
text
@d1 2
d4 7
a10 1
<head>
d12 1
a12 1
<title>SSH tunneling using Cygwin</title>
d14 4
a17 2
</head>
<body>
d19 3
a21 5
<p>
<span class="InputHeader">SSH tunneling using Cygwin: The Desktop Unix Emulator</span>
<p>
<span class="PlainText"><b>SSH Guide: Index</b>
<p>
d23 5
a27 3
<ul>
	<dl>
<dt><a href="ddSSHGuide.html">About this guide</a>
d29 3
a31 1
<dd><a href="ddSSHGuide.html#aboutssh">About SSH</a></li>
d33 1
a33 1
<dd><a href="ddSSHGuide.html#furtherdocumentation">Further documentation</a></li>
d35 1
a35 1
<dt><a href="ddSSHGuideConcepts.html">Concepts</a>
d37 1
a37 1
<dt><a href="ddSSHGuideChoosing.html">Choosing the desktop terminal</a>
d39 1
a39 10
<dt><a href="ddSSHGuideTerminals.html">Using the desktop terminal</a>
	
	<dd><a href="ddSSHGuideTerminals.html#macs">Macintosh</a></dd>
	
	<dd><a href="ddSSHGuideTerminals.html#windows">Windows</a></dd>
	
<dt><b>You are here: Tunneling using Cygwin: The Desktop Unix Emulator
	<dd><a href="#installation">Installation</a>
	<dd><a href="#tunneling">Tunneling</a>
</b>
d41 1
a41 1
<dt><a href="ddSSHGuideterminating.html">Terminating the tunnel</a>
d43 1
a43 3
	</dl>
</ul>
<a href="/servlets/HelpTOC">Back to main Help index</a>
d45 1
a45 3
<p>
<hr noshade size=1>
<a name="installation"></a><span class="InputHeader">Installation</span>
d47 4
a50 5
<p>Before we can tunnel with Cygwin, it must be correctly installed.
<p>The most important consideration for installing Cygwin is creating
the appropriate Unix folders. Cygwin's <a
href="http://www.cygwin.com/" target="_new">website</a> offers complete and detailed
instructions; the below is an abbreviated version.</p>
d52 3
a54 1
<ul>
d56 1
a56 1
<li>Download and install Cygwin. Cygnus gives you the option of installing from the Web, but it is faster (and ultimately more efficient) to install from a local disk. So just download and save the file somewhere you can easily find it.</li>
d58 1
a58 1
<li>Click on Cygwin's "setup.exe" icon and follow the instructions, accepting the defaults. At some point, you will be asked for text format and whether you want Cygwin to be for yourself alone or to be shared. It doesn't matter whether you choose DOS or Unix, but for the sake of ease of use, choose Unix and "All." Cygwin will then install, and should create icons in your start file as well as on your desktop. If it doesn't, run setup again. Nothing will be installed if nothing needs to be, but it will take you to the end, where you can check the boxes indicating you want the icons installed. Check them.</li>
d60 1
a60 1
<li>At this point, you need to create the Unix folders. You can create the standard directories from within Cygwin, as Cygwin's configuration instructions suggest (<a href="http://www.cygwin.com/cygwin-ug-net/setup-dir.html" target="_new">http://www.cygwin.com/cygwin-ug-net/setup-dir.html</a>), or you can set them up from within Windows. Using the Windows method has some advantages, especially for people who are not entirely familiar with Unix commands and protocols. Since Cygwin is able to read both Win32 (Windows) file paths as well as Unix ones (POSIX), it doesn't much matter how you do it.</li>
d62 2
a63 1
<li>Very clear instructions for creating the Unix directories can be found at <a href="http://www.woodsoup.org/projs/ORKiD/basic.htm" target="_new">http://www.woodsoup.org/projs/ORKiD/basic.htm</a>. Although the instructions are specifically for a slightly earlier version of the program, they still obtain: the typical Unix directories must still be created. 
d65 1
a65 1
<li>As well, the cygwin.bat file needs to be modified. Cygnus suggests that other files, too, need modification; but of these, the .bat file, which specifies the commands and their sequence that bash must go through, needs immediate modification. 
d67 1
a67 1
<li>Configure your cygwin.bat file using Windows' Notepad utility or other text editor (not Microsoft Word or anything that imparts formatting) so that it looks something like this:</li>
d69 1
a69 1
</ul>
d71 1
a71 1
  <ul><p><span class="TypewriterPlain">@@ECHO OFF<br>
d73 2
a74 1
  SET MAKE_MODE=Unix<br>
d76 9
a84 1
  SET CYGWIN=notty<br>
d86 2
a87 1
  SET HOME=C:\unix\HOME\[your home directory name]<br>
d89 1
a89 1
  SET TERM=VT100<br>
d91 1
d93 1
a93 6
  CHDIR C:\Unix\HOME\[your home directory name]<br>

  SET PATH=C:\Unix\BIN;C:\Unix\USR\LOCAL\BIN;C:\CYGWIN\BIN;%PATH%<br>

  BASH</span><br>

a94 1
<ul>
d96 1
a96 1
<p><li>Where the "unix" directory on the "C" drive contains the traditional Unix directories. You can name it anything you want, as long a you do not use anything that confuses Unix, e.g., hyphens, spaces, etc. 
d98 2
a99 1
<li>You should now have the C:\Cygwin directories, and your own C:\unix directories, which include your crucial home directory. 
d101 1
a101 1
<li>There is still one more, optional, step. For Cygwin to run efficiently, you might want to configure the shortcut icon on your desktop so that it starts the program in the right directory. This is not necessary, if you have stipulated the HOME directory in the .bat file.</li>
d103 1
a103 3
<li>Cygwin offers some further refinements, and, to be sure, there will doubtless be some tweaking you will have to do to make have the program running efficiently. Again, if you are familiar with Unix commands and file structures, you will find this easy; if you are not, Cygwin is quite forgiving, and you can get started with a minimum of fuss. </li>
</ul>
<p>
d105 2
a106 3
<hr noshade size=1>
<a name="tunneling"></a><span class="InputHeader">Tunneling</span>
<ul>
d108 2
a109 1
<li>First, begin the program.</li>
d111 3
a113 1
<li>At the prompt, enter "<span class="TypewriterPlain">ssh -x -L 2401:localhost:2401 tunnel@@thisdomain.com</span>"</li>
d115 1
a115 1
  <li>The server should ask you for your password. Enter it. It is "<span class="TypewriterPlain">tunnel</span>"</li>
d117 1
a117 1
  <li>If this is your first time, the server will send you a message along these lines:
d119 1
a119 5
  <ul>

  <li><span class="TypewriterPlain">Host key not found from the list of known hosts.</span> </li>

  <li><span class="TypewriterPlain">Are you sure you want to continue connecting (yes/no)?</span> </li>
d121 1
d123 4
a127 3
  </li>

  <li>Enter "<span class="TypewriterPlain">Yes</span>." You can't just enter "y"; you have to spell it out. <li>The server will then respond with: "<span class="TypewriterPlain">Host "thisdomain.com" added to the list of known hosts.</span>" 
a128 10
  <li>The screen does not show a prompt. That's how it should be. The tunnel has been established. You are now ready to begin using CVS. <li>You can, at this point, minimize the terminal, but do not close it or enter <span class="TypewriterPlain">Ctrl-C (^C)</span>. Doing so will kill the terminal tunnel.</li>

</ul>
<p>

<hr noshade size=1>
<a href="/servlets/HelpTOC">Back to main Help index</a>
</span>
</body>
</html>
@


1.2
log
@added <title> tags to all files
@
text
@d1 2
a2 2
<HTML>
<HEAD>
d4 1
a4 1
<TITLE>SSH Tunneling Using Cygwin</TITLE>
d6 2
a7 5
</HEAD>
<BODY>
<span class="PlainText">
<SPAN class=ProjectHeader></SPAN> 
<a name="ddSSHGuideCygwin.html"></a><span class="InputHeader">Tunneling Using Cygwin: The Desktop Unix Emulator</span>
d9 5
a13 1
<span class="InputHeader">SSH Guide Index</span>
d16 2
d19 1
a19 1
<li><a href="#thisguide">About this Guide</a></li>
d21 1
a21 1
<li><a href="#aboutssh">About SSH</a></li>
d23 1
a23 1
<li><a href="#furtherdocumentation">Further Documentation</a></li>
d25 1
a25 1
<li><a href="ddSSHGuideConcepts.html">Concepts</a></li>
d27 10
a36 1
<li><a href="ddSSHGuideTerminals.html">Choosing the Desktop Terminal</a></li>
d38 1
a38 7
<li><a href="ddSSHGuideUsingterminals.html">Using the Desktop Terminal</a></li>

<ul>

<li><a href="ddSSHGuideUsingterminals.html#macs">Macintosh</a></li>

<li><a href="ddSSHGuideUsingterminals.html#windows">Windows</a></li>
d40 1
d42 1
d44 3
a46 7
<li><b>You are Here: Tunneling Using Cygwin: The Desktop Unix Emulator</a></li>
<li><a href=#Terminating.html">Terminating the Tunnel</a></li>
</ul>

<br><br>


d51 1
a51 1
href="http://www.cygwin.com/">website</a> offers complete and detailed
d60 1
a60 1
<li>At this point, you need to create the Unix folders. You can create the standard directories from within Cygwin, as Cygwin's configuration instructions suggest (<a href="http://www.cygwin.com/cygwin-ug-net/setup-dir.html">http://www.cygwin.com/cygwin-ug-net/setup-dir.html</a>), or you can set them up from within Windows. Using the Windows method has some advantages, especially for people who are not entirely familiar with Unix commands and protocols. Since Cygwin is able to read both Win32 (Windows) file paths as well as Unix ones (POSIX), it doesn't much matter how you do it.</li>
d62 1
a62 1
<li>Very clear instructions for creating the Unix directories can be found at <a href="http://www.woodsoup.org/projs/ORKiD/basic.htm">http://www.woodsoup.org/projs/ORKiD/basic.htm</a>. Although the instructions are specifically for a slightly earlier version of the program, they still obtain: the typical Unix directories must still be created. 
a96 1

d98 1
d100 2
a101 2

<b>Tunneling</b>
d106 1
a106 1
<li>At the prompt, enter "<span class="TypewriterPlain">ssh -x -L 2401:localhost:2401 tunnel@@idendev.com</span>"</li>
d122 1
a122 1
  <li>Enter "<span class="TypewriterPlain">Yes</span>." You can't just enter "y"; you have to spell it out. <li>The server will then respond with: "<span class="TypewriterPlain">Host "idendev.com" added to the list of known hosts.</span>" 
d127 1
a127 6
<p><a name="#Terminating"></a><span class="InputHeader">Terminating the Tunnel</span>

<p>The easiest way to terminate the tunnel is to <span class="TypewriterPlain">Ctrl-C (^C)</span> it out of existence. In both the Mac OS and Windows environment, you can also close the client window, thereby shutting the tunnel down.</p>



d129 5
a133 4
<HR noShade SIZE=1>
<a href="Help.html">Back to main Help index</a></p></span>
</BODY>
</HTML>
@


1.1
log
@new and revised help documentation for v1.0
@
text
@d1 7
d132 2
@

