[firstname.lastname@example.org: Re: ENOTSOCK errors with cygwin dll 1.3.21 and 1.3.22]
Mon May 26 16:44:00 GMT 2003
On Mon, May 26, 2003 at 11:57:00AM -0400, Pierre A. Humblet wrote:
> At 05:27 PM 5/26/2003 +0200, Corinna Vinschen wrote:
> >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?
I don't know. First of all sparseness is a property of the file system.
I don't see any call on Linux to influence that. Either a file is sparse
or it isn't and that's entirely controlled by the FS driver, FWICT. So
from my point of view it's entirely ok to do it like that.
> >> 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.
I've tested to read the file attributs of a sparse file on my XP system
from a 98SE VM. The sparse attribute is not propagated to that system.
So I guess we're on the bright side.
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:email@example.com
Red Hat, Inc.
More information about the Cygwin-developers