> To quote from the Single Unix Specification v3:
>
> "A pathname consisting of a single slash shall resolve to the root
> directory of the process. A null pathname shall not be successfully
> resolved. A pathname that begins with two successive slashes may be
> interpreted in an implementation
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. Ex
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?
-Original Message-
> From: Jan Nieuwenhuizen [mailto:[EMAIL 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 use
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
> 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.
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 i
On Tue, Oct 15, 2002 at 03:51:19PM -0400, Igor Pechtchanski wrote:
>On Tue, 15 Oct 2002, [ISO-8859-1] Sven Köhler wrote:
>
>> >>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 d
> "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: http://cygwin.com
On Tue, 15 Oct 2002, [ISO-8859-1] Sven Köhler wrote:
> >>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
> >>l
On Tue, Oct 15, 2002 at 09:09:27PM +0200, Sven K?hler wrote:
>>>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
>
>>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/sha
On Tue, Oct 15, 2002 at 08:09:50PM +0200, Sven K?hler wrote:
>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
>lik
13 matches
Mail list logo
