On 11/16/2010 8:58 AM, Corinna Vinschen wrote:
> On Nov 15 15:25, Ken Brown wrote:
>> On 11/15/2010 11:53 AM, Corinna Vinschen wrote:
>>> On Nov 15 11:40, Christopher Faylor wrote:
On Mon, Nov 15, 2010 at 11:18:57AM -0500, Ken Brown wrote:
> On 11/15/2010 11:09 AM, Corinna Vinschen wrote:
On Nov 15 15:25, Ken Brown wrote:
> On 11/15/2010 11:53 AM, Corinna Vinschen wrote:
> >On Nov 15 11:40, Christopher Faylor wrote:
> >>On Mon, Nov 15, 2010 at 11:18:57AM -0500, Ken Brown wrote:
> >>>On 11/15/2010 11:09 AM, Corinna Vinschen wrote:
> On Nov 13 10:00, Ken Brown wrote:
> >On 11/
On Nov 16 09:33, Ken Brown wrote:
> On 11/16/2010 8:58 AM, Corinna Vinschen wrote:
> > Is there a chance that your service entires still point to a cygrunsrv
> > under C:\cygwin instead of D:\cygwin-1.7?
>
> No. The installation in C:\cygwin is newer than the one in D:\cygwin-1.7;
> it's just a
On Thu, Nov 18, 2010 at 05:08:16PM -0700, jeff.odeg...@gmail.com wrote:
>Were you able to reproduce this on Windows 7? When will this fix be
>released in the regular distro?
If you are seeing a problem with Cygwin 1.7.7 then, as I mentioned earlier,
this is not the same problem.
To answer your
Were you able to reproduce this on Windows 7? When will this fix be
released in the regular distro?
Thanks,
- Jeff
On 12:59 PM, Corinna Vinschen wrote:
On Nov 18 17:22, Corinna Vinschen wrote:
On Nov 18 12:07, Corinna Vinschen wrote:
On Nov 17 20:11, Christopher Faylor wrote:
On Wed, Nov
On 11/18/2010 1:56 PM, Corinna Vinschen wrote:
On Nov 18 17:22, Corinna Vinschen wrote:
On Nov 18 12:07, Corinna Vinschen wrote:
On Nov 17 20:11, Christopher Faylor wrote:
On Wed, Nov 17, 2010 at 05:03:03PM -0500, Ken Brown wrote:
On 11/17/2010 10:47 AM, Corinna Vinschen wrote:
Hmm. Except,
On Nov 18 17:22, Corinna Vinschen wrote:
> On Nov 18 12:07, Corinna Vinschen wrote:
> > On Nov 17 20:11, Christopher Faylor wrote:
> > > On Wed, Nov 17, 2010 at 05:03:03PM -0500, Ken Brown wrote:
> > > >On 11/17/2010 10:47 AM, Corinna Vinschen wrote:
> > > >> Hmm. Except, maybe, since you seem to
On Nov 18 12:07, Corinna Vinschen wrote:
> On Nov 17 20:11, Christopher Faylor wrote:
> > On Wed, Nov 17, 2010 at 05:03:03PM -0500, Ken Brown wrote:
> > >On 11/17/2010 10:47 AM, Corinna Vinschen wrote:
> > >> Hmm. Except, maybe, since you seem to be set up to build Cygwin from
> > >> CVS, could yo
On Nov 17 20:11, Christopher Faylor wrote:
> On Wed, Nov 17, 2010 at 05:03:03PM -0500, Ken Brown wrote:
> >On 11/17/2010 10:47 AM, Corinna Vinschen wrote:
> >> Hmm. Except, maybe, since you seem to be set up to build Cygwin from
> >> CVS, could you start building the 09-12 version from CVS and the
On Wed, Nov 17, 2010 at 05:03:03PM -0500, Ken Brown wrote:
>On 11/17/2010 10:47 AM, Corinna Vinschen wrote:
>> Hmm. Except, maybe, since you seem to be set up to build Cygwin from
>> CVS, could you start building the 09-12 version from CVS and then just
>> add one change from CVS at a time using
>
On 11/17/2010 10:47 AM, Corinna Vinschen wrote:
Hmm. Except, maybe, since you seem to be set up to build Cygwin from
CVS, could you start building the 09-12 version from CVS and then just
add one change from CVS at a time using
cvs up -D '-mm-dd HH:MM'
as filter until you encounter the
On Nov 17 09:56, Ken Brown wrote:
> On 11/16/2010 9:59 AM, Corinna Vinschen wrote:
> >The failing chmod(/dev/tty1, 0622) is actually trying to change the
> >permissions on internal objects, like events, mutexes, and pipes, which
> >together constitute a tty/pty.
>
> Here are some more data points:
On 11/16/2010 9:59 AM, Corinna Vinschen wrote:
The failing chmod(/dev/tty1, 0622) is actually trying to change the
permissions on internal objects, like events, mutexes, and pipes, which
together constitute a tty/pty.
Here are some more data points:
1. I have access to four computers with Cygw
On 11/16/2010 9:59 AM, Corinna Vinschen wrote:
These changes only affect files, not ttys.
The failing chmod(/dev/tty1, 0622) is actually trying to change the
permissions on internal objects, like events, mutexes, and pipes, which
together constitute a tty/pty.
I'm grasping at straws now, but w
On Nov 15 11:40, Christopher Faylor wrote:
> On Mon, Nov 15, 2010 at 11:18:57AM -0500, Ken Brown wrote:
> >On 11/15/2010 11:09 AM, Corinna Vinschen wrote:
> >> On Nov 13 10:00, Ken Brown wrote:
> >>> On 11/5/2010 8:03 AM, Ken Brown wrote:
> If I start sshd on a machine running a recent snapsho
On Mon, Nov 15, 2010 at 11:18:57AM -0500, Ken Brown wrote:
>On 11/15/2010 11:09 AM, Corinna Vinschen wrote:
>> On Nov 13 10:00, 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.
On 11/15/2010 11:09 AM, Corinna Vinschen wrote:
On Nov 13 10:00, 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. The problem fi
On Nov 13 10:00, 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. The problem first appears in the snapshot of
> >2010091
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
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 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. The problem first appears in the snapshot of
20100917. To reproduce:
1. Start sshd.
2. While lo
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. The problem first appears in the snapshot of
20100917. To reproduce:
1. Start sshd.
2. While logged in as one user, try to login as
22 matches
Mail list logo
