http://bugs.winehq.org/show_bug.cgi?id=14914
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |UNCONFIRMED Resolution|INVALID |
--- Comment #18 from Alexandre Julliard julliard@winehq.org 2008-08-21 11:57:19 --- (In reply to comment #17)
(In reply to comment #15)
@Dmitry
Did you once read any of my comments? I know that Wine just passes the file io requests to the kernel. That is the very problem and you named it as well. Linux kernel has different io semantics than Windows, at least concerning sparse files.
Which makes this a kernel/fs bug, not a Wine bug.
Well, no, there's no reason that Wine couldn't force Windows semantics on top of a unix fs, so in that sense it is a difference in behavior that Wine could be hiding. Filling the file with 0 would be fairly inefficient so we certainly don't want to do that, but on some modern file systems it is possible to control block allocation and that could potentially be supported. I'm quite skeptical that the difference would matter in practice.