Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin-developers AT sources DOT redhat DOT com
Message-ID:	<006601c02206$f08e9c40$3327f0d8@lag.net>
From:	"Matt" <matt AT use DOT net>
To:	<cygwin-developers AT sources DOT redhat DOT com>
References:	<00a801c01e93$d6fe7500$3327f0d8 AT lag DOT net> <20000914172419 DOT A24259 AT cygnus DOT com>
Subject:	Re: weird mount/ls behaviour
Date:	Mon, 18 Sep 2000 23:57:56 -0700
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400

> On Thu, Sep 14, 2000 at 02:36:27PM -0700, Matt wrote:
> >mount never seems to return an error if it can't qualify the win32
> >path supplied.
>
> Correct.  It never has and it is not intended to do so, AFAIK.

huh, ok. Why does 'ls' not show the bad mount point at all and 'ls -l' does?
This was the weird behaviour part of my report.

- Raw text -