This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: Mount point not visible in ls
- From: "Larry Hall (RFK Partners, Inc)" <lhall at rfk dot com>
- To: "Conrad Scott" <Conrad dot Scott at dsl dot pipex dot com>, <cygwin at cygwin dot com>
- Date: Tue, 07 May 2002 16:40:59 -0400
- Subject: Re: Mount point not visible in ls
- References: <001201c1f516$37f9d4d0$6132bc3e@BABEL>
At 03:53 PM 5/7/2002, Conrad Scott wrote:
>Thanks to all those who suggested, correctly, that my problem would have
>been caused by the mount point (/usr/bin) having been deleted. I had my Un*x
>head on, where you can't mount on a non-existent mount point.
>
>While on this subject, what is the rationale for this to work in cygwin (w/
>only a warning if performed interactively)? The result, where the mounted
>directory is only visible to certain commands, seems liable to generate
>confusion (or maybe I've been the only one?).
You can check the email archive on this if you're interested in the detailed
history. The short-form is the implementation is just a mapping, so there's
really no requirement that the directory exists. One could envision this as
something more complicated but that's really all it is. However, it's
because of the UNIX mind-set with the like-named command that the current
"mount" warns when the directory doesn't exist. There hasn't been a reason
to add more semantics to make it more like the UNIX equivalent in this regard
however and there are benefits to not doing so.
Larry Hall lhall@rfk.com
RFK Partners, Inc. http://www.rfk.com
838 Washington Street (508) 893-9779 - RFK Office
Holliston, MA 01746 (508) 893-9889 - FAX
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/