http://bugs.winehq.org/show_bug.cgi?id=10282
Szabolcs Szakacsits szaka@ntfs-3g.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |szaka@ntfs-3g.org
--- Comment #5 from Szabolcs Szakacsits szaka@ntfs-3g.org 2007-11-04 12:43:21 --- jestersi: very nice bug report and one of the most interesting ones I've seen for a while, especially if you can indeed reproduce the problems.
First of all, there isn't a single file system in the world which can provide 100% of the functionality what some programs expect. This is why file systems return EOPNOTSUPP and other errors to the applications what they can handle, act accordingly or report it to the user, e.g. "The used XXX file system doesn't support YYY operation, so this software can't do ZZZ". So, such problems definitely mustn't cause crashes, page faults if an application is well written.
What Vitaliy tried to explain you is that you should install Windows softwares under Wine to an NTFS partition to be able to run them under Wine because Wine doesn't support running them otherwise. This is completely file system independent. For instance if you install Windows software to an ext2 partition on Windows then Wine will not support that either.
About the crash. How do you exactly mount the partition? By root or by user? Using mount(8) or ntfs-3g? Is ntfs-3g setuid root? Do you have Wine logs where it crashes?
For me it seems, that depending on whether ntfs-3g is being running privileged or unprivileged the kernel CPU scheduler schedules processes/threads quite differently which triggers a multi-threading bug in Wine-opengl. This wouldn't be the first case when ntfs-3g triggers real problems in applications. Actually it happens relatively often.
Thank you for the bug report.
Regards, Szaka
-- NTFS-3G Lead Developer: http://ntfs-3g.org