This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
re: Error: couldn't make stderr distinct from stdout
- From: "Larry Hall (RFK Partners, Inc)" <lhall at rfk dot com>
- To: <adee at mail dot ootips dot org>, <cygwin at cygwin dot com>
- Date: Tue, 22 Jan 2002 16:17:36 -0500
- Subject: re: Error: couldn't make stderr distinct from stdout
At 03:20 PM 1/22/2002, Adee Ran wrote:
>I get the above error when running bash on a telnet session on Win2K. That's a pity because the cmd shell is even more annoying than usual in this case.
>
>The only information I found about that is quite old:
>
>in http://sources.redhat.com/ml/cygwin/2000-12/msg00866.html (Date: Tue, 19 Dec 2000 13:02:57 +0100 ) Corinna Vinschen says:
>
> >There's has been made a change in Cygwin (...)
>(...)
> >The problem is that the W2K telnet server doesn't allow duplicating
> >the handle for some strange reason which only Microsoft knows of.
>
>is there a solution by now?
>
>my version data (from cygcheck):
>
> Cygwin DLL version info:
> dll major: 1003
> dll minor: 2
> dll epoch: 19
> dll bad signal mask: 19005
> dll old termios: 5
> dll malloc env: 28
> api major: 0
> api minor: 39
> shared data: 3
> dll identifier: cygwin1
> mount registry: 2
> cygnus registry name: Cygnus Solutions
> cygwin registry name: Cygwin
> program options name: Program Options
> cygwin mount registry name: mounts v2
> cygdrive flags: cygdrive flags
> cygdrive prefix: cygdrive prefix
> cygdrive default prefix:
> build date: Sun May 20 23:28:17 EDT 2001
> shared id: cygwin1S3
First, I'd recommend updating your DLL. However, to answer your
question, I think Corinna provided the best solution you're likely to
get on this subject, without a change from MS. Did you try using
telnet from the inetutils package?
Larry Hall lhall@rfk.com
RFK Partners, Inc. http://www.rfk.com
838 Washington Street (508) 893-9779 - RFK Office
Holliston, MA 01746 (508) 893-9889 - FAX
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/