From:	TYann AT vet DOT com DOT au (Trevor Yann)
Subject:	Re: mount() semantics
23 Sep 1998 02:48:27 -0700 :
Message-ID:	<3.0.5.32.19980922140931.0081cd00.cygnus.cygwin32.developers@mail.mel.cybec.com.au>
References:	<19980921191324 DOT 55118 AT cygnus DOT com>
Mime-Version:	1.0
To:	cygwin32-developers AT cygnus DOT com

I like the idea of forcing the directory to exist, but we have to be able
to cope with the directory being later deleted from outside the cygwin32
environment. Perhaps we could check this at startup, and remove/disable
mounts where the unerlying directory no longer exists.

At 19:13 21/09/98 -0700, you wrote:
>Consider:   mount Q:/baz /foo/bar
>
>Under Unix, /foo/bar would have to be a valid directory.  Under
>Cygwin32, it does not.  Even worse, /foo doesn't even have to exist so
>if you cd into /foo/bar, and then try to cd .., an error results.
>I'm pretty convinced something needs to change.
>
>I am tempted to suggest requiring that /foo/bar exist as of b20,
>modifying mount() in winsup accordingly.  That would have the
>advantage of making mount()'s semantics much closer to Unix.  But it
>would also have the disadvantage of requiring physical directory mount
>points which could be a bummer to have to cope with.
>
>If you all think that would be too drastic, we could at least check
>for the parent directory's existance (although that's a bit trickier)...
>
>Thoughts?
>
>-- 
>Geoffrey Noer
>noer AT cygnus DOT com
>

- Raw text -