From: earnie_boyd AT yahoo DOT com (Earnie Boyd) Subject: Re: mounts, ls, and filename completion 13 Aug 1998 06:41:57 -0700 Message-ID: <19980812194730.11186.rocketmail.cygnus.gnu-win32@send103.yahoomail.com> Reply-To: earnie_boyd AT yahoo DOT com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii To: lhall AT rfk DOT com, pete AT horus DOT cix DOT co DOT uk, "J. J. Farrell" , john_r_velman AT mail DOT hac DOT com Cc: gw32 I hope I can do this easily so that all can understand: When you `mount -b D:/ /foo' the mounted reference is a logical pointer to the D:/ root directory _NOT_ to the directory /foo on D:. Therefore, when you do `ls /foo' you will also see the /foo directory and you would be able to do `cd /foo/foo'. Let us suppose that the `/' root directory is mounted to c:\ and that /foo resides on c:\. Let us now suppose you `mount -b D:/ /foo'. You still have a logical pointer to the D:/ root directory and filesystem commands to /foo will look at the D:/ root directory and c:/foo will not be used (usually). As for confusing cygwin32, which one is it supposed to use? It will attempt to use the logical pointer /foo and usually does; however, it is possible for it to use the physical directory /foo and occasionally does. When I was testing to respond to your querys, cygwin32 gave me "permission denied" errors accessing such a mounted directory. To help you understand the cygwin mount table, think of it more as a symbolic link table than as a table of directories available for use by the user. To help you further understand, remember that you are emulating UNIX, not using UNIX and that you are really using WIN32. Hope this helps, - \\||// ---o0O0--Earnie--0O0o---- --earnie_boyd AT yahoo DOT com-- ------ooo0O--O0ooo------- ---"J. J. Farrell" wrote: > > > From: Earnie Boyd > > > > ---Pete Jordan wrote: > > > > > > You need to create a directory with the same name as the mount > > > /before/ mounting it. For example: > > > > > > mkdir /foo > > > mount -b D:/ /foo > > > > Only if your on UNIX and this ain't UNIX. As a matter of fact, it is > > best _NOT_ to create the directory first as it only confuses you the > > user _AND_ cygwin32 the emulation filesystem. > > > > Now if you were to do: > > mkdir //d/foo > > mount -b //d/foo /foo > > that would be perfectly acceptable and would not confuse you or > > cygwin32. > > Now I'm thoroughly confused, on a couple of counts. > > 1) Why should Pete's version confuse the user and yours not? This > user found Pete's version immediately easy and obvious to > understand, but had to struggle for a while to understand yours. > I suspect that what is confusing depends on your background. > > 2) You say that you should not create the directory before mounting > on it as that confuses both the user and the software. By my > reading, your version also creates the directory before mounting > on it, but you say that won't confuse the software or the user. > I take it that you don't really mean that creating the directory > first will cause confusion, but I'd like to understand what you > do mean - how and why will your version work but Pete's not? > > Regards, > jjf > _________________________________________________________ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help".