Maybe 1.5 Regression: cp failing while working with cygwin 1.3.22

[Roland Schwingel]

Hi...

Corrina Vinschen wrote on 15.01.2008 15:03:40:
 > Here's the reason:
 > [...]
Thanks for the reply and the insight!

 > Maybe the smb.conf setting "follow symlinks = no" is an option for you?
Unfortunately not. This won't help me as I use the symlinks to make certain
things outside the scope of a share visible.

Well... Doing this is a bloody hack but for myself I recompiled 
cygwin1.dll and
changed in  fhandler_disk_file.cc the path_conv::isgood_inode() function to
return false if fs_is_samba() returns true and now it appears to work
ls -li also returns random numbers again.

Ok this is only a temporary fix for me and my installation and obviously
restores behaviour from 1.3 for me (and maybe opening other problems now).

But what would be the correct solution?

Trigger samba people to change their implementation to behave the same for
windows clients as they do for UNIX CIFS connections?

or

tweak cywins cp to take this into account and leave the cygwin dll as is?
(but maybe other applications are also affected by this problem)

or

restore 1.3's random inode number for samba connections?
(maybe as an option to $CYGWIN to be enabled/disabled)

Thanks,

Roland


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/