Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <006001bfc71a$e2f6de90$0201a8c0@ntgodd> From: "Chris Wilson" To: "CygWin Project" Subject: Telnet Server and BASH.EXE Date: Fri, 26 May 2000 10:01:23 -0400 Organization: pcNetworks MIME-Version: 1.0 Content-Type: multipart/related; type="multipart/alternative"; boundary="----=_NextPart_000_005C_01BFC6F9.595740B0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 ------=_NextPart_000_005C_01BFC6F9.595740B0 Content-Type: multipart/alternative; boundary="----=_NextPart_001_005D_01BFC6F9.595740B0" ------=_NextPart_001_005D_01BFC6F9.595740B0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hello all. I've been using the CYGWIN software for quite some time now, = and just recently moved to Windows 2000. I haven't experienced any problems with the software running under W2K, = though I don't really do any CYGWIN development. I basically use it to = keep my Linux-user skills in check when I'm forced to work at a Windows = machine all day long. W2K has a nice little telnet server built in, and from the registry you = can manually set the default shell you wish to use. However, when I set = it for bash.exe I have problems. I have made the following registry modifications for the telnet server: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\TelnetServer\1.0 DefaultShell =3D D:\BIN\BASH.EXE --login -i -o ignoreeof LoginScript =3D (value not set) Termcap =3D D:\BIN\TERMCAP The default settings were: DefaultShell %SystemRoot%\system32\cmd.exe /q /k LoginScript %SystemRoot%\system32\login.cmd Termcap %SystemRoot%\system32\termcap The termcap file from the original entry, I copied into my CYGWIN's BIN = directory before making the registry change. Then I start the TelnetD = service. However, when I telnet to the machine I get the following response: 0 [main] bash 1000 hinfo_init: couldn't make stderr distinct from stdout And then it just hangs there until I disconnect the telnet session. In the task manager, I can see 2 items start when I telnet to the = machine. TLNTSESS.EXE and BASH.EXE, however I never get my bash prompt, = and like I said previously, the session hangs until I disconnect. The = TLNTSESS.EXE and BASH.EXE do get closed when I disconnect. I was wondering if anyone else has tried this, or is there another = telnet server I should be using instead of the built-in Microsoft one? Thank you for any help anyone might offer. Have a great day. - Chris Wilson ------=_NextPart_001_005D_01BFC6F9.595740B0 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
Hello all. I've been using the CYGWIN software for quite some time = now, and=20 just recently moved to Windows 2000.
 
I haven't experienced any problems with the software running under = W2K,=20 though I don't really do any CYGWIN development. I basically use it to = keep my=20 Linux-user skills in check when I'm forced to work at a Windows machine = all day=20 long.
 
W2K has a nice little telnet server built in, and from the registry = you can=20 manually set the default shell you wish to use.  However, when I = set it for=20 bash.exe I have problems.
 
I have made the following registry modifications for the telnet=20 server:
 
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\TelnetServer\1.0
 
DefaultShell =3D D:\BIN\BASH.EXE --login -i -o ignoreeof
 
LoginScript =3D (value not set)
 
Termcap =3D D:\BIN\TERMCAP
 
 
The default settings were:
 
DefaultShell  %SystemRoot%\system32\cmd.exe /q /k
 
LoginScript   %SystemRoot%\system32\login.cmd
 
Termcap      =20 %SystemRoot%\system32\termcap
 
The termcap file from the original entry, I copied into my CYGWIN's = BIN=20 directory before making the registry change.  Then I start the = TelnetD=20 service.
 
However, when I telnet to the machine I get the following = response:
 
0 [main] bash 1000 hinfo_init: couldn't make stderr distinct = from=20 stdout

And then it just hangs there until I disconnect the telnet=20 session.
 
In the task manager, I can see 2 items start when I telnet to = the=20 machine.  TLNTSESS.EXE and BASH.EXE, however I never get my bash = prompt,=20 and like I said previously, the session hangs until I disconnect. The=20 TLNTSESS.EXE and BASH.EXE do get closed when I disconnect.
 
I was wondering if anyone else has tried this, or is there another = telnet=20 server I should be using instead of the built-in Microsoft one?
 
Thank you for any help anyone might offer. Have a great day.

-
 
Chris Wilson
 
------=_NextPart_001_005D_01BFC6F9.595740B0-- ------=_NextPart_000_005C_01BFC6F9.595740B0 Content-Type: image/gif; name="Blank Bkgrd.gif" Content-Transfer-Encoding: base64 Content-ID: <005b01bfc71a$e05cabb0$0201a8c0 AT ntgodd> R0lGODlhLQAtAID/AP////f39ywAAAAALQAtAEACcAxup8vtvxKQsFon6d02898pGkgiYoCm6sq2 7iqWcmzOsmeXeA7uPJd5CYdD2g9oPF58ygqz+XhCG9JpJGmlYrPXGlfr/Yo/VW45e7amp2tou/lW xo/zX513z+Vt+1n/tiX2pxP4NUhy2FM4xtjIUQAAOw== ------=_NextPart_000_005C_01BFC6F9.595740B0--