On Mon, Nov 15, 2010 at 05:11:46AM +, TryingToHelp wrote:
>This is a known DOS/Windows bug. I'm fairly sure that DOS used NUL as a null
>device, and that Windows kept it around (not sure why, guess it's for
>backward-compatibility).
This thread is more than a month old. There is no reason to
On Sun, Nov 14, 2010 at 08:45:01PM -0700, Jeff Odegard wrote:
>On 12:59 PM, Ken Brown wrote:
>> On 11/5/2010 8:03 AM, Ken Brown wrote:
>>> If I start sshd on a machine running a recent snapshot, I'm unable to
>>> login to that machine via ssh. The connection is closed right after I
>>> type my pass
This is a known DOS/Windows bug. I'm fairly sure that DOS used NUL as a null
device, and that Windows kept it around (not sure why, guess it's for
backward-compatibility).
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation:
Bump. I just posted the same problem on Friday night on Windows 7.
On 12:59 PM, Ken Brown wrote:
On 11/5/2010 8:03 AM, Ken Brown wrote:
If I start sshd on a machine running a recent snapshot, I'm unable to
login to that machine via ssh. The connection is closed right after I
type my password.
On Sat, Nov 13, 2010 at 18:03, Charles Wilson wrote:
> On 11/11/2010 10:19 PM, David Antliff wrote:
>> On Cygwin 1.7.7, this does something nasty to the completely unrelated
>> yet existing telnetlib socket so that any further attempts to read or
>> write from this socket raise an exception:
[snip]
5 matches
Mail list logo
