Andrey Repin wrote:
Greetings, cyg Simple!
Don't forget that CMD will not create a second connection to a
\\host\share if Cygwin already has one open.
What do you mean by that?
$ cd //somehost/someshare
$ cmd /c start cmd
cmd will complain about UNC paths and start in %WINDIR% instead.
----
Try it the other way around. You'll get the same result.
It has nothing to do with cygwin opening it first. It has
to do with cmd not handling a "\\network\share" style address.
MS was too lazy to deal with command.com's "1-CurDir / drive"
scenario that is embedded in the Win32 interface. If you cd to
//host/<currentdir>, //host isn't a drive letter.
So what happens when the user uses an absolute path? "/tmp"...
where is that /tmp? Ends up at the root of each drive, but on
a UNC-based-net-connection? Undefined. So cmd.exe can't be used
on a UNC-based path, only on DOS compatible (drive letter
assummed) based-path.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
