Petter Reinholdtsen wrote: > The users of --force-unsafe-io seem to be those that [...]
In retrospect, introducing --force-unsafe-io was probably a mistake. Making sure to always call a wrapper function that behaves just like fsync() but can be disabled would be a maintenance burden for almost no benefit, given that eatmydata exists. The current semantics are at least distinct from eatmydata, though it's not obvious to me that it is a very useful distinction. (I guess the idea is that it is for situations in which you can easily detect corruption of individual installed packages and reinstall them, while the internal database is still precious.) Hope that clarifies a little, Jonathan -- To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
