Re: Cygwin's ACL handling is NOT interoperable with Windows
- Date: Mon, 6 Aug 2018 08:15:27 +0200
- From: Michael Wild <themiwi@xxxxxxxxx>
- Subject: Re: Cygwin's ACL handling is NOT interoperable with Windows
On Sun, Aug 5, 2018 at 5:35 PM Andrey Repin <anrdaemon@xxxxxxxxx> wrote:
> 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)
> >>> 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
> I think, this is an appropriate response to the underlying issue:
+1 from me.
I propose to ignore Stefan until he learns his manners, is less
cantankerous and maybe even volunteers to submit a patch if indeed there is
a problem with the ACL handling (although, to be honest, I can hardly
imagine it, Corinna being involved...).
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple