On Thu, 28 Jun 2007, Russell Coker wrote: > Package: dpkg > Version: 1.13.25 > Severity: normal > > Below is part of the output of stracing dpkg when installing a package. As > you can see it opens the file without O_SYNC and renames it without calling > fsync() first. This means that a reboot during the period for which write- > back caching is active (which depends on the load of the machine, the amount > of free RAM, and the filesystem in use) will cause loss of file data.
If the machine reboots while dpkg unpacks a package, dpkg will know that the package is not cleanly unpacked/updated and this will simply get fixed later after the reboot when the user finishes his update. I fail to see a scenario where this behaviour leads to a problem. If the .dpkg-new file is not written on disk, I don't see why the directory content would be updated on disk. Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/
