On 01/11/2010 05:22 AM, Corinna Vinschen wrote:
On Jan 10 21:01, Larry Hall (Cygwin) wrote:
<snip>
No. If the R/O attribute is supported, then a fourth option would
It isn't. NFS only handles POSIX permissions. However, if you're using
the Microsoft NFS client, you can convert the Cygwin syste-type symlinks
to "real" symlinks on the target filesystem. These are supported as well
by Cygwin.
Ah cool. You know, I think I remember you mentioning that before. :-)
However, please note that Microsoft's NFS client does not support UTF-8
as target charset.
be to convert the
symbolic links to their "winsymlinks" format. If course, doing that
means you loose
UTF character support. See
<http://cygwin.com/cygwin-ug-net/using-cygwinenv.html>
for more on this option.
Is my description under using-cygwinenv.html unclear? I only compared
the old and the new format. The new format using UTF-16 is used by both
styles of symlinks, the SYSTEM and the .lnk style.
OK, I didn't get that from my reading of the description. I'd recommend
adding that path names of either style now use UTF-16, just to be clear.
I doubt this is a critical issue of course but it's worthwhile to make this
distinction to avoid confusion.
--
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
216 Dalton Rd. (508) 893-9889 - FAX
Holliston, MA 01746
_____________________________________________________________________
A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
--
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
