Did upstream reply yet? If upstream is unresponsive, perhaps you or I could modify the relevant tools to deal with the dirty flag. Hopefully this important issue can be resolved in time for Feisty.
As for checking every 30 mounts or so: Windows doesn't do it, and Windows is maintained by competent coders, so I think we'll be fine if we don't do it either.
* Do we really need to do it?
* And if we do it, how would we keep track of maximal mount count? (Will /etc usually be writable at mounting time? Could we keep track of the number of past mounts for each fat32 partition in a file in /etc?)
Did upstream reply yet? If upstream is unresponsive, perhaps you or I could modify the relevant tools to deal with the dirty flag. Hopefully this important issue can be resolved in time for Feisty.
As for checking every 30 mounts or so: Windows doesn't do it, and Windows is maintained by competent coders, so I think we'll be fine if we don't do it either.
* Do we really need to do it?
* And if we do it, how would we keep track of maximal mount count? (Will /etc usually be writable at mounting time? Could we keep track of the number of past mounts for each fat32 partition in a file in /etc?)