[corinna-cygwin@cygwin.com: Re: ENOTSOCK errors with cygwin dll 1.3.21 and 1.3.22]

Pierre A. Humblet Pierre.Humblet@ieee.org
Mon May 26 16:22:00 GMT 2003

At 05:27 PM 5/26/2003 +0200, Corinna Vinschen wrote:
>On Mon, May 26, 2003 at 11:05:49AM -0400, Pierre A. Humblet wrote:
>> 1) The way I think you have it, a file can be made sparse even when 
>>    O_CREAT | O_TRUNC isn't set. Is that desirable? 
>Yes, I think so.  Why shouldn't a file become sparse when the accessing
>application are going to create holes by seeking beyond EOF?   That's
>the only situation in which this might happen.

I have no strong opinion here. I simply noticed the difference between
Vaclav Haisman's original method and your way. How do other Unix do it? 
>> 2) in fhandler::write, test wincap.has_lseek_bug before the sparse file.
>>    This is to cover the (hypothetical, so far) case where a win 95 would
>> mount a 
>>    remote file system supporting sparse files. I don't know if fs_flags 
>>    would show the file can be sparse, nor if the win95 lseek bug would
>> actually 
>>    show up. So it may be paranoia.
>You can test this, can't you?

Not in practice. I would have to install my corporate VPN software on
my antique Win95, with a high likelihood of headache and wasted day.


More information about the Cygwin-developers mailing list