Hi LaMont, LaMont Jones wrote:
> With the introduction of fsync() calls to protect data, applications > that do potentially large apt-get install invocations may not want > to incur the penalty of fsync() calls from dpkg. > > In the case of building a livecd, this can be the difference between > a 10 minute apt invocation, and 21 minutes. Makes sense. > The use cases where --force-unsafe-io would make sense are those > where apt is modifiying an underlying (possibly empty) base chroot > and the results will be thrown away before the next apt invocation > such that a crash just means "start from the known good base". As a hackish workaround, it would be nice to get libeatmydata into Debian (see <http://bugs.debian.org/512588>). That would prevent fsync() calls in maintainer scripts, too. Of course a --force-unsafe-io option is probably better, since among other things it expresses the intent more clearly. Regards, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
