Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Thu, 10 Jul 2003 11:48:22 -0400
From: Christopher Faylor <cgf-idd AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: another cygwin-1.5.0 managed mount bug  (please don't use managed mode yet)
Message-ID: <20030710154822.GA3350@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <6A3008858445D711A58A00062939B2F1EAA4 AT EXCHANGE>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6A3008858445D711A58A00062939B2F1EAA4@EXCHANGE>
User-Agent: Mutt/1.4.1i

On Thu, Jul 10, 2003 at 06:12:00PM +0200, Pavel Rozenboim wrote:
>When I execute following commands in directory mounted in managed mode I get
>some failures:
>
>touch com1
>touch: setting times of `com1': Invalid argument
>
>(Same error for com2)
>
>touch com3
>touch: creating `com3': No such file or directory
>
>I have 2 serial ports, this probably explains different error messages.

This is not another bug.  It is the same bug previously reported.

Please no more bug reports on this until I announce that I've fixed things
in a snapshot.

Unfortunately, I didn't add any tests to the test suite for this functionality
and I didn't think to test it before releasing.  I introduced some bugs for
dealing with case sensitivity just prior to release that made managed moded
pretty much worthless in 1.5.0.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/