public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Adrian Carter <adrian@lidcam.com.au>
To: frederick.page@amb-informatik.de, cygwin@cygwin.com
Subject: Re: No more //c
Date: Thu, 06 Sep 2001 03:16:00 -0000	[thread overview]
Message-ID: <5.1.0.14.2.20010906201701.00aada50@127.0.0.1> (raw)
In-Reply-To: <OFBB335618.4A6FFFF5-ONC1256ABF.00279BC0@11.AM-GRUPPE.DE>

At 12:09 PM 6/09/2001 +0100, frederick.page@amb-informatik.de wrote:
>Hi there,
>
> http://sources.redhat.com/ml/cygwin-announce/2001/msg00109.html says
>about the upcoming changes in Cygwin 1.3.3:
>
>Briefly, the problem with using //x to refer to drive x is that it
>clashes with Windows' use of // to denote a network share.  So a system
>called 'x' on your network was previously inaccessible to cygwin.

Perhaps clashes is being used in a 'looks real bad when seen in a list of 
resources that also contains SMB shares'. i.e:

//x/blah
\\blah\x

Kinda confusing... to a 'dummy' it could easily be seen perhaps as a typo.

Im guessin.

Adrian



>I'm not sure, whether this new change is necessary at all: to my
>understanding, Windows uses the non-standard backslash, a network
>share would be noted here as \\Sharename (and *not* //Sharename).
>
>Am I missing something?
>
>Kind regards    Frederick
>
>
>--
>Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
>Bug reporting:         http://cygwin.com/bugs.html
>Documentation:         http://cygwin.com/docs.html
>FAQ:                   http://cygwin.com/faq/

Adrian Carter
Senior Support Engineer  LIDCAM

Performance Networking Solutions by LIDCAM -
Lucent, Sun / Cobalt, Extreme, Netopia, Nortel / Alteon, Redback, 
Cacheflow, Sendmail

Voice: 02 9922 7066 / 0410 577 049 / Fax: 02 9922 7071
adrian@lidcam.com.au / www.lidcam.com.au
Mail: Suite 5, Level 11, 100 Walker St, Nth Sydney, NSW, 2060
----------------------------------------------------------------
This communication (email) & files transmitted with it are privileged & 
confidential information intended solely for the addressee. No infringement 
of this firm's rights in respect to this confidential information will be 
permitted. No liability is accepted for damage caused in the transmission 
of this email.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  reply	other threads:[~2001-09-06  3:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-06  3:09 frederick.page
2001-09-06  3:16 ` Adrian Carter [this message]
2001-09-06  3:20 ` Corinna Vinschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5.1.0.14.2.20010906201701.00aada50@127.0.0.1 \
    --to=adrian@lidcam.com.au \
    --cc=cygwin@cygwin.com \
    --cc=frederick.page@amb-informatik.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).