This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Cygwin's ACL handling is NOT interoperable with Windows
- From: Andrey Repin <anrdaemon at yandex dot ru>
- To: "Stefan Kanthak" <stefan dot kanthak at nexgo dot de>, cygwin at cygwin dot com
- Date: Sun, 5 Aug 2018 18:22:31 +0300
- Subject: Re: Cygwin's ACL handling is NOT interoperable with Windows
- References: <2B3187EFB48B477183C355EDF9660136@W340> <1444436439.20180805170441@yandex.ru> <3AA6B0E5761945E58833642A6DB75341@W340>
- Reply-to: cygwin at cygwin dot com
Greetings, Stefan Kanthak!
> Andrey Repin wrote:
>> Greetings, Stefan Kanthak!
>>
>>> PS: <https://cygwin.com/cygwin-ug-net/using.html#pathnames-win32-api>
>>> too states bloody lies:
>>
>>> | The Windows subsystem only supports CWD paths of up to 258 chars.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>
>> 260 including drive letter.
> WRONG, AGAIN!
> 260 is the value of MAX_PATH, which accounts for the trailing \0, and
> commonly used as
> | char buffer[MAX_PATH];
> I recommend to read
> <https://docs.microsoft.com/en-us/windows/desktop/fileio/naming-a-file>
> VERY careful!
>>> The Win32 API supports pathnames with up to 32767 (Unicode) characters;
>>> this includes of course the CWD!
>>
>> CWD may be, but command processor does not.
> Neither Cygwin's WRONG documentation nor I referred to the command processor.
I think, this is an appropriate response to the underlying issue:
https://xkcd.com/386/
--
With best regards,
Andrey Repin
Sunday, August 5, 2018 18:21:42
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