On Mon, Feb 17, 2003 at 07:48:57PM +0100, Vaclav Haisman wrote: >>Btw, now that I've said that it occurred to me to check >>GetVolumeInformation. There is apparently a FILE_SUPPORTS_SPARSE_FILES >>flag available. That's the ultimate way to deal with this rather than >>adding a wincap, I believe. Check (pc->fs.flags & >>FILE_SUPPORTS_SPARSE_FILES) in fhandler_disk_file::open and do the >>appropriate thing there. >> >>Sorry I didn't think of this before. > >I know about this flag and I have considered it when I started writing >this patch. It has one flaw. The volume of root of the path to the >file doesn't have to be the same volume as the file is physicaly stored >on in case of reparse points presence. Besides I don't see it as a >problem if this call fails to set the sparseness becase the file system >doesn't support it.
This is consistent with the way the rest of cygwin works, however. The same argument could be applied to testing for ntsec. If this was an issue then we should be changing the fs information to reflect reparse points. cgf
