This is the mail archive of the cygwin@sourceware.cygnus.com mailing list for the Cygwin project. See the Cygwin home page for more information.
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index] [Subject Index] [Author Index] [Thread Index]

Re: Interesting bug?



---Tripp Lilley <tlilley@perspex.com> wrote:
>
> mount reports (among other things):
> 
> v:\\tmp	/tmp	native	text!=binary
> 
> which is correct.
> 
> in cmd.exe:
> 
> c:
> cd \tmp
> (pwd now C:\tmp)
> 
> ls
> 
> 'ls' displays contents of /tmp, not c:\tmp! ls //c/tmp works as
expected.
> 'rm', 'chmod', and others seem to be looking in //c/tmp as expected
when
> run with relative path names (ie: echo 'hello' > /tmp/foo.txt,
followed by
> 'rm foo.txt' with c:\tmp as pwd bombs as expected saying "foo.txt:
No such
> file or directory")
> 

Relative paths with the official b20.1 release are known to feature a
few inconsistencies.  The path emulation has been reworked for a newer
release.  Furthermore if you have a mounted directory for /tmp on one
drive and the root mounted to a different drive and you have a tmp
directory physically under root this is what is known as a mount point
and isn't intended to be the /tmp directory but a placeholder that is
usually empty.

If you don't understand this structure then you will definitely get
confused.  A lot of the problems stem from the fact that the
filesystem isn't a unix filesystem but the cygwin product pretends
that it is.  It can give some interesting results.

==
-                        \\||//
-------------------o0O0--Earnie--0O0o-------------------
--                earnie_boyd@yahoo.com               --
-- http://www.freeyellow.com/members5/gw32/index.html --
----------------------ooo0O--O0ooo----------------------

PS: Newbie's, you should visit my page.
_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com