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
Date:	Tue, 23 Aug 2005 02:41:57 -0700
From:	Yitzchak Scott-Thoennes <sthoenna AT efn DOT org>
To:	cygwin AT cygwin DOT com
Subject:	Re: Unable to access forced mounts from /bin/sh
Message-ID:	<20050823094157.GB3156@efn.org>
References:	<Pine DOT GSO DOT 4 DOT 61 DOT 0508210147050 DOT 16057 AT slinky DOT cs DOT nyu DOT edu> <4309C081 DOT 9030400 AT byu DOT net>
Mime-Version:	1.0
In-Reply-To:	<4309C081.9030400@byu.net>
User-Agent:	Mutt/1.4.2.1i
X-IsSubscribed:	yes

On Mon, Aug 22, 2005 at 06:09:37AM -0600, Eric Blake wrote:
> On the other hand, what if the user does:
> $ mkdir /a
> $ mount -u -f c: /a/b
> $ rmdir /a
> 
> This will take some thought and planning for cygwin1.dll and mount(1) to
> get sane behavior in all cases.  Maybe the best solution for this case is
> to have rmdir(2) to return EBUSY or ENOTEMPTY if the directory being
> removed is currently hosting a forced mountpoint.

The directory would still be removable via windows programs.

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

- Raw text -