DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:references:date:in-reply-to
	:message-id:mime-version:content-type:content-transfer-encoding;
	 q=dns; s=default; b=Ooam7CYBh1o0qDWyDWKzG8i/UYwfd3/eiTXgh0MobaG
	xoyljqASyix1sOJjqHJ7heq/4MUdafUIoS1yTixazTM2/rPGXGomKphMd8pfuj8h
	mAXPLe9ZkYMEUiBv1HQjsn1he9JgAKMspJdZVGfk8xhZhkj3hfqjuonr3Mw5WiYM
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: 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>	<87efhbdbaz.fsf@Rainer.invalid>	<20180613080953.GR7851@calimero.vinschen.de>	<trinity-bc977f4a-d31b-4cf6-be60-493433b38724-1528884853707@3c-app-gmx-bs06>
Date: Wed, 13 Jun 2018 19:08:18 +0200
In-Reply-To: <trinity-bc977f4a-d31b-4cf6-be60-493433b38724-1528884853707@3c-app-gmx-bs06>	(Sven Eden's message of "Wed, 13 Jun 2018 12:14:13 +0200")
Message-ID: <87muvypqbh.fsf@Rainer.invalid>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

Sven Eden writes:
> True, if /this isn't just a mount point for //this, meaning
> that the "that"s are two different files.
[…]

Again, my main objection is that the interpretation of a path should not
change based on the availability or non-availability of any host (or its
name resolution) over the network.  That's exactly the kind of thing
that will come back to bite you in the most inconvenient moment.

Regarding the discussion about Linux behaviour, I'd be happy if Linux
had an option to just make any path with two leading slashes throw an
error if that path makes it anywhere a local filesystem gets involved.
That'd be quite helpful in quickly weeding out portability problems like
the one you showed.


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