storing symlink in extended attribute (on ntfs)

[egor duda]

Hi!

Friday, 11 May, 2001 Christopher Faylor cgf@redhat.com wrote:

CF> This looks ok.  I'm a little concerned about adding YA way to set symlinks,
CF> though.

well, i really hope this change is both backward and forward
compatible. i.e. old dll should work seamlessly  with "new" symlinks,
and new dll -- with the old ones. the only problem is with moving and
copying cygwin symlinks with native tools -- it's still here, as it
was before. 

CF> As a specific comment, I wonder if it would just make sense to store volume
CF> information in the path_conv class to avoid going through the duplicate efforts
CF> in symlink.

i guess so. currently, GetVolumeInformation is called only when
symlink is created, not resolved, but this will slow things down on
file systems other than NTFS. to remove this penalty,
GetVolumeInformation() should be called in symlink resolution code to, 
and that's where volume information caching can save some cycles.

Egor.            mailto:deo@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19