DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=GfNxQ2Ed6sym/0/n
	s19rAxDf6HH7R6vr4p3qguNJ5+FNmRzQIt8m/Orn86Rnk4vrKpKBZYJHSdHAjmD5
	tWsifg/oZf7AZ4url835L0jrZYbvUk4A+SVDoorYOkRjQOkBswek+oRqS5Li/4nA
	D38P6P0jdtvctRXAbAZ/7I5rUu8=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Tue, 24 Sep 2019 15:46:08 +0300
From: Andrey Repin <anrdaemon@yandex.ru>
Reply-To: cygwin@cygwin.com
Message-ID: <643902820.20190924154608@yandex.ru>
To: =?utf-8?Q?J=C3=BCrgen_Wagner?= <juergen@wagner.is>, cygwin@cygwin.com
Subject: Re: ls \\\\\?\\DRIVE\\ Aborted (core dumped)
In-Reply-To: <7518af94-3c5b-0019-b99b-8409c138b40c@wagner.is>
References: <1569223086.860642696@f357.i.mail.ru>   <CAJLNCaRU3VtPUu=q+R+-X0PurudJ0_8LmHHGKJkkETJtCPDX3Q@mail.gmail.com>  <5ccc23b3-0240-7382-d018-a7a6bf285f47@cornell.edu>  <5e1afbfe-997a-a528-acfc-38512310041a@SystematicSw.ab.ca>  <4210536081.20190924012630@yandex.ru>  <7518af94-3c5b-0019-b99b-8409c138b40c@wagner.is>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

Greetings, Jürgen Wagner!

Please no top-posting in this list. Thank you in advance.

> ls \\\\.\\d:\\
> ls: cannot access '\\.\d:\': Not a directory
=>> The alternative notation with a "." does not seem to be understood. 
> It works in DOS shells.

This is not an "alternative notation", this is a "device namespace".
Shell is not necessarily an indication of the right path.
You may be better off writing a small program that calling Win32 CreateFile
directly, if you want to test various paths.
Ref: https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file

> ls //\?/d:/
> ls: cannot access '//?/d:/': Not a directory
=>> The replacement notation with forward slashes (which works with UNC 
> paths) does not seem to be honored here.

Which is also dubious in case of Cygwin.
And double forward slashes are indicating Cygwin UNC path.
Not a Windows NT namespace prefix.

> It seems to me the device notation is not really implemented in Cygwin, 
> and if invalid device paths are used or strange, invalid syntactic forms 
> are used, this fails with a core dump.

> This is on CYGWIN_NT-10.0 saraswati 3.0.7(0.338/5/3) 2019-04-30 18:08 
> x86_64 Cygwin on a Dell 5470 with the latest Windows 10 version.


-- 
With best regards,
Andrey Repin
Tuesday, September 24, 2019 15:41:52

Sorry for my terrible english...
--
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