Hi!
Wednesday, 16 October, 2002 Sven Köhler [EMAIL PROTECTED] wrote:
SK the sollution that paths like //comp/share are interpreted like an
SK UNC-path is just not compatible with an application might expect from a
SK unix-environment.
Then those applications are making false assumptions.
hi,
a path like //usr/local is treated as an UNC path.
this might leads to problems when an application is using //usr/local as
a normal unix-path.
i don't know how to overcome the problem, but one might think of a path
like /unc/computer/share instead of using the path //computer/share
what
translates paths like /usr/local to c:\cygwin\usr\local and
manages mount-points etc...
cygwin opffers a complete virtual filesystem
the cygwin-developers chose, to NOT convert //usr/local to
c:\cygwin\usr\local
i would like to know why.
Think of it another way:
cygwin allows the user to specify
.
cygwin translates paths like /usr/local to c:\cygwin\usr\local and
manages mount-points etc...
cygwin opffers a complete virtual filesystem
the cygwin-developers chose, to NOT convert //usr/local to
c:\cygwin\usr\local
i would like to know why.
Sven,
Basically your complaint is inconsistent
Patches gratefully accepted (C). Oops, sorry, I guess it's Donations
gleefully accepted now... :-D
what do you mean with that?
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation:
speak definitively
about why Microsoft chose this behavior.
cygwin translates paths like /usr/local to c:\cygwin\usr\local and
manages mount-points etc...
cygwin opffers a complete virtual filesystem
the cygwin-developers chose, to NOT convert //usr/local to
c:\cygwin\usr\local
i would like
Christopher Faylor [EMAIL PROTECTED] writes:
cygwin allows the user to specify paths like: c:\foo\bar and c:/foo/bar.
Similarly, it allows //foo/bar and \\foo\bar .
If that doesn't satisfy you then you can go back to the Because we're mean
argument.
I've been hurt by this too, and it makes
Perhaps something like a unc_prefix is in order, similar to the cygdrive
prefix?
the sollution that paths like //comp/share are interpreted like an
UNC-path is just not compatible with an application might expect from a
unix-environment.
the 2 slashes should be collapsed and nothing else.
On 10/15/2002 1:05 PM, Sven Köhler wrote:
the sollution that paths like //comp/share are interpreted like an
UNC-path is just not compatible with an application might expect from a
unix-environment.
Don't be silly - there are Unix-y environments where // doesn't work
the way you think
PROTECTED]]
Sent: Tuesday, October 15, 2002 4:01 PM
To: [EMAIL PROTECTED]
Subject: Re: paths like //usr/local
Christopher Faylor [EMAIL PROTECTED] writes:
cygwin allows the user to specify paths like: c:\foo\bar
and c:/foo/bar.
Similarly, it allows //foo/bar and \\foo\bar
On 10/15/2002 1:05 PM, Sven Köhler wrote:
the sollution that paths like //comp/share are interpreted like an
UNC-path is just not compatible with an application might expect from a
unix-environment.
And there are other things too. Perhaps cygwin should ban \ file
separators in paths?
11 matches
Mail list logo