Issue #2588 has been updated by swildner.
On Thu, 26 Sep 2013 16:12:37 +0200, wrote: > Besides burning CPU, the xz command has no visible effect on DragonFly > 3.5. Surely not as generally as you put it. An 1.25GB file took ~17 minutes to xz here on a rather old box. zoot# ls -l hyperv.tar -rw-r--r-- 1 root wheel 1347233792 Aug 12 13:51 hyperv.tar zoot# time xz hyperv.tar 1038.500u 15.003s 17:39.77 99.4% 29+73k 84+12712io 2pf+0w zoot# ls -l hyperv.tar.xz -rw-r--r-- 1 root wheel 843640560 Aug 12 13:51 hyperv.tar.xz Sascha ---------------------------------------- Bug #2588: xz(1) broken on DragonFly 3.5 http://bugs.dragonflybsd.org/issues/2588#change-11589 * Author: ftigeot * Status: New * Priority: Normal * Assignee: * Category: * Target version: ---------------------------------------- Besides burning CPU, the xz command has no visible effect on DragonFly 3.5. In contrast, xz file.tar immediately starts creating a second (hidden) file on DragonFly 3.4. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account