Re: `CYGWIN=winsymlinks:nativestrict`, `ln -s target link` fails if target doesn't exist

> > POSIX says a symlink to a missing target is perfectly well-defined (you > > can't stat() through it, but you can readlink() it). But Windows native > > symlinks can't do that. So the problems you are encountering all stem > > from the fact that you are trying to make Windows do something it ca

Re: `CYGWIN=winsymlinks:nativestrict`, `ln -s target link` fails if target doesn't exist

On 2016-04-29 13:34, Gene Pavlovsky wrote: >>> POSIX says a symlink to a missing target is perfectly well-defined (you >>> can't stat() through it, but you can readlink() it). But Windows native >>> symlinks can't do that. So the problems you are encountering all stem >>> from the fact that you ar

RE: [cygwin] Re: `CYGWIN=winsymlinks:nativestrict`, `ln -s target link` fails if target doesn't exist

> -Original Message- > From: Peter Rosin > Sent: Friday, April 29, 2016 8:03 AM > > On 2016-04-29 13:34, Gene Pavlovsky wrote: > >>> POSIX says a symlink to a missing target is perfectly > well-defined > >>> (you can't stat() through it, but you can readlink() it). But > >>> Windows nat

Re: Post install script zp_texlive_finish.dash of TeX Live-update fails

On 4/29/2016 3:32 AM, Tobias Zawada wrote: Hello, the post install script zp_texlive_finish.dash of the TeX live update from 2016-04-29 fails. Please look at /var/log/setup.log.full to see if there's more information about what's failing. "/etc/postinstall/texlive-collection-basic.sh" 2016

Re: reading from pipes fails if working directory is on a removable drive

On 29.04.2016 05:50, Marco Atzeri wrote: On 29/04/2016 00:18, mihau wrote: ZoneAlarm Personal Firewall Can you disable it ? yes; no change. Michael -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.

Re: reading from pipes fails if working directory is on a removable drive

On 29/04/2016 14:28, mihau wrote: On 29.04.2016 05:50, Marco Atzeri wrote: On 29/04/2016 00:18, mihau wrote: ZoneAlarm Personal Firewall Can you disable it ? yes; no change. Michael As next step, can you remove it ? Some can interfere also when disabled. In addition you can run str

Re: reading from pipes fails if working directory is on a removable drive

On 29.04.2016 15:23, Marco Atzeri wrote: As next step, can you remove it ? Some can interfere also when disabled. I did think about it for a second but actually that's not an option; also it never interfered with cygwin or any other application. In addition you can run strace -o pipe.str

Re: reading from pipes fails if working directory is on a removable drive

On 29/04/2016 16:44, mihau wrote: On 29.04.2016 15:23, Marco Atzeri wrote: In addition you can run strace -o pipe.strace cat test.txt |head on fix and removable drive. May be will give some additional hint. exact same result as described in the original post yes but you mentioned that

Re: reading from pipes fails if working directory is on a removable drive

On 29.04.2016 16:51, Marco Atzeri wrote: yes but you mentioned that the problem is only on the removable drive so the two versions should be different somewhere ;-) oh yes, correct. my bad. fixed drive: $ strace -o pipe.strace cat test.txt | head test removable drive: $ strace -o pipe.strace

Re: Post install script zp_texlive_finish.dash of TeX Live-update fails

Thanks to the hint of Ken Brown I found some more info in setup.log.full (I will send setup.log.full only on direct request since it is 24 MB large.) It seems to me that the following section is of most interest: 2016/04/29 08:56:50 running: c:\cygwin64\bin\dash.exe "/etc/postinstall/zp_texlive_f

Re: Issues with ACL settings after updating to the latest cygwin.dll - correction

I'm having a similar issue with strange acl results... I wish I knew which update triggered this, but I'd ignored and/or worked around it... I can reproduce it with the following: user@localhost ~ $ touch /tmp/foo user@localhost ~ $ chmod 700 /tmp/foo user@localhost ~ $ echo foo>/tmp/foo -bash:

spinlock.h timeout causing *** fatal error - add_item abort

Hi, We occasionally see an api_fatal abort during process startup like: *** fatal error - add_item ("somepath", "/", ...) failed, errno 1 This happens if mountinfo.init(false) in user_info::initialize is called twice. The error occurs on a second call when trying to add the root mount point whe

Re: "man" hangs attempting to access UNC paths

So I figured out what causes this - but I don't know why. "/" ended up in my path - from some imported configuration in .bashrc. When I don't have "/" in the path, then man works. So, given that, why would that cause man to reference UNC paths? maninfo.txt

Re: "man" hangs attempting to access UNC paths

On 04/29/2016 10:32 AM, joeking wrote: > So I figured out what causes this - but I don't know why. > > "/" ended up in my path - from some imported configuration in .bashrc. > When I don't have "/" in the path, then man works. > > So, given that, why would that cause man to reference UNC paths?

Re: "man" hangs attempting to access UNC paths

On Fri, Apr 29, 2016 at 10:48:20AM -0600, Eric Blake wrote: > On 04/29/2016 10:32 AM, joeking wrote: > > So I figured out what causes this - but I don't know why. > > > > "/" ended up in my path - from some imported configuration in .bashrc. > > When I don't have "/" in the path, then man works. >

Re: Post install script zp_texlive_finish.dash of TeX Live-update fails

[Please don't top-post.] On 4/29/2016 11:28 AM, Tobias Zawada wrote: updmap: Directory "/var/lib/texmf/fonts/map/dvips/updmap" isn't writable: at /usr/bin/updmap line 1426. So this appears to be a permissions problem rather than a TeX Live problem. 2016/04/29 09:16:17 can't run /etc/postins

[ANNOUNCEMENT] Updated: octave forge packages

New versions of octave-bsltl1.0.0-1 octave-optim1.5.1-1 octave-parallel 3.0.5-1 octave-struct 1.0.13-1 are available in the Cygwin distribution: ADVISE On cygwin none of the forge packages is autoloaded, as some package could change substantially the no

Re: `CYGWIN=winsymlinks:nativestrict`, `ln -s target link` fails if target doesn't exist

I can confirm this behavior. Basically, mklink requires to choose file (default) or directory (/D) link. It is true whether or not the target exists (e.g. if your target is a directory, /D is not implied automatically, you have to specify it). By contrast, POSIX symlink doesn't distinguish file or