On Aug 1 12:24, Sasha Firsov wrote: > Dear cygwiners, > In documentation on environment variables there is a reference only > for 2 choices. > http://cygwin.com/cygwin-ug-net/using-cygwinenv.html > None of which is given native NFS symlink option: windows > shortcut(LNK file) or "plain files with a magic number, a path and > the system attribute set" . > > From Corinna Vinschen post > http://sourceware.org/ml/cygwin/2012-04/msg00564.html > "Cygwin understands NFS symlinks just fine, and when it creates > symlinks on NFS, these are *real* symlinks, not Cygwin-type fake > symlinks. " > > How to make it working? Default behavior is to use "plain file" as > defined in environment document :(
Supported is only the Microsoft NFS client. It has a specific API to allow reading and writing native symlinks. This works automatically, independent of the "winsymlink" option. If it doesn't work for you, you either don't use the Microsoft NFS client, or you're actually accessing the remote share via SMB, not via NFS. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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
