X-Spam-Check-By: sourceware.org
From: Richard Foulk <richard AT skydive1 DOT com>
Message-Id: <200606112215.k5BMFOW7015470@sd.skydive1.com>
Date: Sun, 11 Jun 2006 12:15:24 -1000
To: cygwin AT cygwin DOT com
Subject: Re: mount never fails ... sorta
User-Agent: nail 11.20 1/13/05
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

> Richard Foulk wrote:
> > Give mount(1) nonexistent hosts or directories and it will complain,
> > but it still populates the mount table as if it succeeded.
> > 
> > It also always returns zero, for success or failure.
> 
> Cygwin's mount is a different bird than on Unix.  It really is just a mapping
> table of POSIX names to DOS or UNC-style paths.  It is not required that the
> POSIX path exist for things to work.  But since most people coming from a UNIX
> background expect that it does and it certainly helps things like shell
> path completion if the paths do already exist, you get a warning to let you
> know about this difference.
> 

I guess I should have said mount's behavior is wrong and broken.

It knows when there's an error it just does the wrong things.

	1. mount reports the error to stderr, but not via the return code.

	2. mount knows about the error but signals success anyway -- by
	   listing a (non-existent) mount within the mount table.

Sure Cygwin's mount is different than Unix's.  That's what Cygwin is all
about, hiding those differences.  Cygwin's mount fails at that.

Registering a mount that doesn't exist is quite broken.


Richard

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