1.3.6 ssh Write failed: The descriptor is a file, not a socket

1.3.6 ssh Write failed: The descriptor is a file, not a socket

[Daryl Spartz]

The subject line problem, reported back in November, 2001 was stated to be
fixed in message archive post
http://www.cygwin.com/ml/cygwin/2001-11/msg00694.html by Jeff Mincy. I am
running 1.3.6 and STILL have the problem (running on win2k)

$ uname -a
CYGWIN_NT-5.0 POOLSIDE 1.3.6(0.47/3/2) 2001-12-08 17:02 i686 unknown

This problem has been around for a long time, last known to work on cygwin
version 1.3.2.

Daryl

spartz@us.ibm.com


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

Re: 1.3.6 ssh Write failed: The descriptor is a file, not a socket

[Corinna Vinschen]

On Thu, Jan 10, 2002 at 09:50:53AM -0800, Daryl Spartz wrote:
> The subject line problem, reported back in November, 2001 was stated to be
> fixed in message archive post
> http://www.cygwin.com/ml/cygwin/2001-11/msg00694.html by Jeff Mincy. I am
> running 1.3.6 and STILL have the problem (running on win2k)

I don't have that problem and others neither.  You should debug
that on your machine.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

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

Re: 1.3.6 ssh Write failed: The descriptor is a file, not a socket

[Christopher Faylor]

On Fri, Jan 11, 2002 at 10:02:24AM +0100, Corinna Vinschen wrote:
>On Thu, Jan 10, 2002 at 09:50:53AM -0800, Daryl Spartz wrote:
>> The subject line problem, reported back in November, 2001 was stated to be
>> fixed in message archive post
>> http://www.cygwin.com/ml/cygwin/2001-11/msg00694.html by Jeff Mincy. I am
>> running 1.3.6 and STILL have the problem (running on win2k)
>
>I don't have that problem and others neither.  You should debug
>that on your machine.

I don't have the problem either.

HTH!

cgf

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

Re: 1.3.6 ssh Write failed: The descriptor is a file, not a socket

[Pavel Tsekov]

I thought "me toos" are not welcomed on this list :P

Christopher Faylor wrote:

> On Fri, Jan 11, 2002 at 10:02:24AM +0100, Corinna Vinschen wrote:
> 
>>On Thu, Jan 10, 2002 at 09:50:53AM -0800, Daryl Spartz wrote:
>>
>>>The subject line problem, reported back in November, 2001 was stated to be
>>>fixed in message archive post
>>>http://www.cygwin.com/ml/cygwin/2001-11/msg00694.html by Jeff Mincy. I am
>>>running 1.3.6 and STILL have the problem (running on win2k)
>>>
>>I don't have that problem and others neither.  You should debug
>>that on your machine.
>>
> 
> I don't have the problem either.
> 
> HTH!
> 
> cgf



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

Re: 1.3.6 ssh Write failed: The descriptor is a file, not a socket

[Christopher Faylor]

On Fri, Jan 11, 2002 at 06:33:04PM +0100, Pavel Tsekov wrote:
>I thought "me toos" are not welcomed on this list :P

That's what I thought, too!

HTH,
cgf

>Christopher Faylor wrote:
>>On Fri, Jan 11, 2002 at 10:02:24AM +0100, Corinna Vinschen wrote:
>>>On Thu, Jan 10, 2002 at 09:50:53AM -0800, Daryl Spartz wrote:
>>>>The subject line problem, reported back in November, 2001 was stated to
>>>>be fixed in message archive post
>>>>http://www.cygwin.com/ml/cygwin/2001-11/msg00694.html by Jeff Mincy.  I
>>>>am running 1.3.6 and STILL have the problem (running on win2k)
>>>>
>>>I don't have that problem and others neither.  You should debug that on
>>>your machine.
>>>
>>
>>I don't have the problem either.
>>
>>HTH!

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

setup.ini for custom distrobution

[Michael Adler]

I'm putting together a modified distrobution of CYGWIN so that I can
easily install just the packages that I want, including some custom
packages. I wrote a script to create the setup.ini, but I'm not yet
satisfied because when I execute setup.exe most of the packages are set
for 'skip'. The setup.exe and setup.ini files are both on a CD and the
packages that I want are in the contrib/latest subdirectories. This is on
the first install, not a reinstall.

How can I write a setup.ini so that it will install everything without
having to click on 40 packages?

If this is a RTFM situation, please show me the Fine Manual.

If it goes well, I might write a doc 'how to create your own cygwin
distro'.

Thanks!

Mike Adler


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

Re: setup.ini for custom distrobution

[Robert Collins]

----- Original Message -----
From: "Michael Adler" <adler@glimpser.org>


> How can I write a setup.ini so that it will install everything without
> having to click on 40 packages?

1) Don't use a setup.ini.
2) Put everything into base.
3) read http://www.cygwin.com/setup.html

> If this is a RTFM situation, please show me the Fine Manual.

No, it's a case of read the manual we wish we had time to write. The
cygwin-apps archives include the discussion on setup development, which
would answer this for you.

> If it goes well, I might write a doc 'how to create your own cygwin
> distro'.

Right now, with the number of contributors we've got, this could be
disastrous :}.

Also, you don't _need_ a custom distribution with the next release of
setup. You can just merge in a 2nd setup.ini that causes the changes you
want, and adds any needed packages.

Rob


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

Off Topic clutching at straws - Interix

[Robert White]

Sorry as this is way off topic, but I know the product Interix has been
mentioned in passing on this list in the past.

Does anyone know how to go about debugging the message "Cannot connect to
Interix subsystem" whenever I try to run any of their commands such as ksh etc?

I have checked the posix subsystem and that seems to be OK, but it then
subsequently fails to connect to the interix subsystem.

Sorry once again if this is considered an intrusion, but I am desperate, after
24+ hours searching round the internet.

regds

Rob


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

Re: Off Topic clutching at straws - Interix

[Christopher Faylor]

On Sat, Jan 12, 2002 at 05:45:45PM +0000, Robert White wrote:
>Sorry as this is way off topic, but I know the product Interix has been
>mentioned in passing on this list in the past.
>
>Does anyone know how to go about debugging the message "Cannot connect to
>Interix subsystem" whenever I try to run any of their commands such as ksh etc?
>
>I have checked the posix subsystem and that seems to be OK, but it then
>subsequently fails to connect to the interix subsystem.
>
>Sorry once again if this is considered an intrusion, but I am desperate, after
>24+ hours searching round the internet.

This is certainly very much off-topic.  I hope that anyone who responds does so
personally.

cgf

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