This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Aw: Re: Problematic interpretion of paths starting with double slashes
- From: Achim Gratz <Stromeko at nexgo dot de>
- To: cygwin at cygwin dot com
- Date: Tue, 12 Jun 2018 22:01:08 +0200
- Subject: Re: Aw: Re: Problematic interpretion of paths starting with double slashes
- References: <trinity-82173dac-d842-4a87-8d1f-bed9a958d178-1528793630066@3c-app-gmx-bs08> <dc8418d2-2004-97f0-2d8c-ab438f007eba@redhat.com> <trinity-2aa37c55-032a-4631-9d8f-657ecd85e170-1528809265158@3c-app-gmx-bs08>
Sven Eden writes:
> Doing a simple stat on / if (and only if) the UNC lookup
> fails, does not endanger anything. It wouldn't break
> anything or do any other damage. Besides from adding an
> additional <0.01s lag to any failed access that *really*
> meant a network share.
>
> So no. Adding this tiny extra functionality wouldn't break
> anything for anybody, but allowed the usage of software that
> relies on the non-cygwin behaviour. (And is outside the
> users control.)
Well, it does break things if both
//this/or/that
/this/or/that
exist and then at some point host "this" becomes unreachable. So I'd
keep //unc/path to mean just that on principle.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra
--
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