-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
- From end-user's POV, this infamous XFS behavior is somewhat
taken as XFS's inferiority compared to other filesystems.
Even with "bad" applications (ex. firefox), this rarely happens
on others, so regardless of what's on the FAQ, people logically
concludes that the fault belongs to XFS anyway.
So, what is the correct way to do IO?
Is what firefox (and other bad apps) doing is so obvious(ly buggy),
that it'll be acknowledged as a bug once reported? Or is it simply
a mismatch between application expectation and XFS behavior,
requiring a non-(obvious|generic) fix?
Although I'm not a filesystem developer, I'm pretty impressed with
XFS and willing to file a report/patch to those "buggy" apps if the
issue is explainable to other app developers.
>> was to press the reset button on the computer. After the reboot, when I
>> opened Firefox again, I noticed that all my bookmarks were gone. Those
>> bookmarks were imported from my desktop machine a few days after I
>> configured
>> the new server.
>
> This is a firefox bug - I've seen it before (on my mother's machine).
>
> It's due to firefox not doing the correct thing with IO on the bookmarks
> file.
- --
Taisuke Yamada <tyamadajp@xxxxxxxxxxxxxxxxx>, http://rakugaki.org/
2268 E9A2 D4F9 014E F11D 1DF7 DCA3 83BC 78E5 CD3A
Message to my public address may not be handled in a timely manner.
For a direct contact, please use my private address on my namecard.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFF+Mrq3KODvHjlzToRAu/vAKC8pky15WJwocHbWhbRx9f2H+c5aQCeIeYp
ZJPcSeawAIbZN80GXJz+kYg=
=oAY3
-----END PGP SIGNATURE-----
|