[opensuse-buildservice] Compression format for images build
Hi all, When I'm trying to uncompress images built by OBS (e.g. [1]) in Windows, 7-Zip, PeaZip and WinRAR all fails. 7-Zip just failed to recognize the tar ball, and WinRAR complained with message 'sparse file is not supported'. After some searching, I find this bug report for 7-Zip[2]. It seems that sparse tar package is not supported in 7-Zip either. I saw from here[3] that image compressing method is hard coded in build_kiwi.sh, and using '-S' option for tar cmd. Can this option be controlled by project config? So that appliances which with Windows users as one of main audiances can be more friendly (I'm buiding one now). It will be inconvenient if users have to use GNUWin[4] or Cygwin tools to uncompress the image, especially for non-tech ones. Best Regards, [1] http://download.opensuse.org/repositories/openSUSE:/Tools/images/obs-server.... [2] http://sourceforge.net/tracker/?func=detail&aid=3116688&group_id=14481&atid=114481 [3] https://github.com/openSUSE/obs-build/blob/master/build_kiwi.sh [4] http://gnuwin32.sourceforge.net/packages/libarchive.htm -- Xin Wang (http://dram.me/) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am Samstag, 14. Juli 2012, 16:52:11 schrieb Xin Wang:
Hi all,
When I'm trying to uncompress images built by OBS (e.g. [1]) in Windows, 7-Zip, PeaZip and WinRAR all fails. 7-Zip just failed to recognize the tar ball, and WinRAR complained with message 'sparse file is not supported'.
After some searching, I find this bug report for 7-Zip[2]. It seems that sparse tar package is not supported in 7-Zip either.
I saw from here[3] that image compressing method is hard coded in build_kiwi.sh, and using '-S' option for tar cmd.
Can this option be controlled by project config?
no, it can not atm. The best solution would be if kiwi would take over this part.
So that appliances which with Windows users as one of main audiances can be more friendly (I'm buiding one now). It will be inconvenient if users have to use GNUWin[4] or Cygwin tools to uncompress the image, especially for non-tech ones.
Yes, it should work easily for windows users. On the other side, we must avoid that without sparse support the image sizes do explode. I can not remember the details anymore, but we had the case that IIRC EC2 images were way to large without. Interesting question is why ... shouldn't a compression algorithm compress plenty zeros nicely?
Best Regards,
[1] http://download.opensuse.org/repositories/openSUSE:/Tools/images/obs-server.... [2] http://sourceforge.net/tracker/?func=detail&aid=3116688&group_id=14481&atid=114481 [3] https://github.com/openSUSE/obs-build/blob/master/build_kiwi.sh [4] http://gnuwin32.sourceforge.net/packages/libarchive.htm
-- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
2012/7/14 Adrian Schröter
Am Samstag, 14. Juli 2012, 16:52:11 schrieb Xin Wang:
Hi all,
When I'm trying to uncompress images built by OBS (e.g. [1]) in Windows, 7-Zip, PeaZip and WinRAR all fails. 7-Zip just failed to recognize the tar ball, and WinRAR complained with message 'sparse file is not supported'.
After some searching, I find this bug report for 7-Zip[2]. It seems that sparse tar package is not supported in 7-Zip either.
I saw from here[3] that image compressing method is hard coded in build_kiwi.sh, and using '-S' option for tar cmd.
Can this option be controlled by project config?
no, it can not atm. The best solution would be if kiwi would take over this part.
So that appliances which with Windows users as one of main audiances can be more friendly (I'm buiding one now). It will be inconvenient if users have to use GNUWin[4] or Cygwin tools to uncompress the image, especially for non-tech ones.
Yes, it should work easily for windows users. On the other side, we must avoid that without sparse support the image sizes do explode. I can not remember the details anymore, but we had the case that IIRC EC2 images were way to large without. Interesting question is why ... shouldn't a compression algorithm compress plenty zeros nicely?
I did some tests, use [1] as a base, here's the data: .tar.bz2: size: 261M [A] after bunzip2: 769M (ls & du) [B] after tar xf: 895M (ls), 878M (du) [C] tar & xz -2: size: 217M [D] after unxz: 895M (ls), 881M (du) [E] after tar xf: 895M (ls & du) [F] xz -2 (vmdk only): size: 217M [G] after unxz: 895M (ls), 881M (du) [H] We can find that: 1. xz can compress sparse file [G. sparse vmdk file] and plenty zero file [D. zero tar file] equally. 2. compression ratio of 'xz -2' is better than bzip2 here. 3. Use 'tar & xz -2', vmdk file will not be sparse after uncompress [F]. 4. Use 'xz -2' to compress vmdk directly, sparse can be retained [H]. So can we use xz to compress vmdk directly, and then publish vmdk and vmx file separately? [1] http://download.opensuse.org/repositories/openSUSE:/Tools/images/obs-server....
Best Regards,
[1] http://download.opensuse.org/repositories/openSUSE:/Tools/images/obs-server.... [2] http://sourceforge.net/tracker/?func=detail&aid=3116688&group_id=14481&atid=114481 [3] https://github.com/openSUSE/obs-build/blob/master/build_kiwi.sh [4] http://gnuwin32.sourceforge.net/packages/libarchive.htm
-- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de
-- Xin Wang (http://dram.me/) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (2)
-
Adrian Schröter -
Xin Wang