Re: realpath issue with native[strict] symlinks

2021-05-09 Thread Orgad Shaneh via Cygwin
On Sat, May 8, 2021 at 12:20 AM Corinna Vinschen wrote: > > I reworked the code handling native symlinks to handle virtual drives > as well. It might even be a tiny bit quicker now. > > The changes have a behavioral change, but I think this is for the > better: Virtual drives are not treated as d

Re: realpath issue with native[strict] symlinks

2021-05-06 Thread Orgad Shaneh via Cygwin
On Thu, May 6, 2021 at 8:44 PM Corinna Vinschen wrote: > > On May 4 22:52, Orgad Shaneh via Cygwin wrote: > > On Tue, Apr 27, 2021 at 8:44 AM Orgad Shaneh wrote: > > > > > > On Apr 19 12:58, Corinna Vinschen via Cygwin wrote: > > > > On A

Re: realpath issue with native[strict] symlinks

2021-05-04 Thread Orgad Shaneh via Cygwin
On Tue, Apr 27, 2021 at 8:44 AM Orgad Shaneh wrote: > > On Apr 19 12:58, Corinna Vinschen via Cygwin wrote: > > On Apr 18 10:59, Orgad Shaneh via Cygwin wrote: > > > I was going to write: > > > > Nothing we can do about without re-implementing Cygwin's

Re: realpath issue with native[strict] symlinks

2021-04-26 Thread Orgad Shaneh via Cygwin
On Apr 19 12:58, Corinna Vinschen via Cygwin wrote: > On Apr 18 10:59, Orgad Shaneh via Cygwin wrote: > I was going to write: > > Nothing we can do about without re-implementing Cygwin's path handling > from scratch. For historical reasons, POSIX paths are evaluated

realpath issue with native[strict] symlinks

2021-04-18 Thread Orgad Shaneh via Cygwin
Hi, When winsymlinks:native/nativestrict is used, realpath doesn't resolve the full path correctly, when a symlink to the same directory is used. Example follows. The output is: /home/user/recurse/test/d1 /home/user/recurse/test2/d1 While it should be /home/user/recurse/d1 for both. A few obser

Re: A problem with noacl+umask+chmod result

2021-04-18 Thread Orgad Shaneh via Cygwin
On Sat, Apr 17, 2021 at 8:11 PM Kaz Kylheku (Cygwin) <743-406-3...@kylheku.com> wrote: > > On 2021-04-08 21:34, Orgad Shaneh via Cygwin wrote: > > On Fri, Apr 9, 2021 at 4:50 AM Andrey Repin > > wrote: > >> > >> Greetings, Orgad Shaneh! > >>

Re: A problem with noacl+umask+chmod result

2021-04-08 Thread Orgad Shaneh via Cygwin
On Fri, Apr 9, 2021 at 4:50 AM Andrey Repin wrote: > > Greetings, Orgad Shaneh! > > > On Wed, Apr 7, 2021 at 11:47 PM Orgad Shaneh wrote: > >> > >> Hi, > >> > >> If a filesystem is mounted with noacl, calling chmod to add write > >> permissions after umasking this permission doesn't work. Demonst

Re: A problem with noacl+umask+chmod result

2021-04-08 Thread Orgad Shaneh via Cygwin
On Wed, Apr 7, 2021 at 11:47 PM Orgad Shaneh wrote: > > Hi, > > If a filesystem is mounted with noacl, calling chmod to add write > permissions after umasking this permission doesn't work. Demonstrated > with command-line and C++. > > Did I miss something or is this a real bug? According to umask

Re: Cannot run executable named setlang

2021-04-08 Thread Orgad Shaneh via Cygwin
On Thu, Apr 8, 2021 at 3:55 PM Takashi Yano wrote: > > On Thu, 8 Apr 2021 15:25:45 +0300 > Orgad Shaneh wrote: > > Hi, > > > > I cannot run an executable if it is named setlang (case insensitive). > > It exits with code 127. > > > > Example: > > cp /bin/ls setlang > > ./setlang -> Error 127 > > >

Cannot run executable named setlang

2021-04-08 Thread Orgad Shaneh via Cygwin
Hi, I cannot run an executable if it is named setlang (case insensitive). It exits with code 127. Example: cp /bin/ls setlang ./setlang -> Error 127 I've noticed a difference in ldd output. cygwin dlls appear twice. ldd /bin/ls: ntdll.dll => /cygdrive/c/WINDOWS/SYSTEM32/ntdll.dll (0x7ff

A problem with noacl+umask+chmod result

2021-04-07 Thread Orgad Shaneh via Cygwin
Hi, If a filesystem is mounted with noacl, calling chmod to add write permissions after umasking this permission doesn't work. Demonstrated with command-line and C++. Did I miss something or is this a real bug? According to umask man, it should only affect newly created files and directories, but