Cool, I know how to fix this now, thank you!
This is now fixed in upstream PhysicsFS here for the 3.0 branch:
https://hg.icculus.org/icculus/physfs/rev/c17f025e7a92
...and here for the default (what will eventually become an unstable
3.1.0) branch...
I tried this and can confirm that removing setBuffer calls avoids the
fsyncs. I verified this with strace too, which should be doable on any
machine (just "strace -o /tmp/output ./neverball", and after playing
check that /tmp/output contains no fsync calls).
Cool, I know how to fix this now,
This is not actionable by Debian itself.
(But if you don't mind, we'll organize on this bug report briefly to get
this fixed upstream. Apologies in advance for a few emails worth of
extra chatter!)
--ryan.
Can someone humor me and make a quick change to Neverball for me?
In neverball/share/fs_physfs.c, there are three calls to
PHYSFS_setBuffer(). Just comment them out and rebuild Neverball with
PhysicsFS support and see if the problem goes away on the machine with
the slow disk.
I suspect I
Upstream patch is here:
https://hg.icculus.org/icculus/physfs/rev/a29fef4a20fd
I have one other pending bug to fix, hopefully tomorrow, then I'll put
out an official 3.0.2 release.
--ryan.
This is a bug in PhysicsFS, I'm working on it and then rolling 3.0.2
with the fix.
--ryan.
...the latest official source code release contains the fix for this bug:
http://icculus.org/pipermail/physfs/2010-March/000891.html
--ryan.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
(CC: physfs mailing list)
The problem on kFreeBSD isn't kFreeBSD specific at all. Debian on Linux
should have this problem, too, but maybe we got lucky there.
This patch fixed it awhile ago...
http://hg.icculus.org/icculus/physfs/rev/cd500847dbc9
...and will be in the 2.0.1 release.
(I
Hi, I'm the upstream maintainer of PhysicsFS.
I just tested this with an install of kFreeBSD in a vmWare virtual
machine and it is working as expected.
I tested both the 2.0.0 release and the tip of the Mercurial repository,
using the test case provided in this bug report (setting the $PATH
9 matches
Mail list logo
