Differences between gz, bzip2, xz, 7z, rar, lzop

 

Differences between gz, bzip2, xz, 7z, rar, lzop


Gzip and bzip2, as well as xz and lzop, are functionally equivalent. 

(There once was a bzip, but it seems to have completely vanished off the face of the world.) 

Other common compression formats are zip, rar and 7z; these three do both compression and archiving (packing multiple files into one). 

Here are some typical ratings in terms of speed, availability and typical compression ratio 

(note that these ratings are somewhat subjective, don't take them as gospel):

decompression speed (fast > slow): lzop > gzip, zip > xz > 7z > rar > bzip2
compression speed (fast > slow): lzop > gzip, zip > xz > bzip2 > 7z > rar
compression ratio (better > worse): xz > 7z > rar, bzip2 > gzip > zip > lzop
availability (unix): gzip > bzip2 > xz > lzop > zip > 7z > rar
availability (windows): zip > rar > 7z > gzip > bzip2, lzop, xz
 
 
source: https://superuser.com/questions/205223/pros-and-cons-of-bzip-vs-gzip 

Comments

Post a Comment

Popular posts from this blog

Securing the Pi-hole with fail2ban to prevent DNS Amplification attacks

Securing the Pi-hole with fail2ban to prevent DNS Amplification attacks   1. Install fail2ban  sudo apt-get update ; sudo apt-get install fail2ban 2. create jail file vi /etc/fail2ban/jail.d/pihole-dns.conf [pihole-dns] enabled = true port     = 53 action   = %(banaction)s[name=%(__name__)s-tcp, port="%(port)s", protocol="tcp", chain="%(chain)s", actname=%(banaction)s-tcp]            %(banaction)s[name=%(__name__)s-udp, port="%(port)s", protocol="udp", chain="%(chain)s", actname=%(banaction)s-udp] logpath = /var/log/pihole.log findtime = 60 maxretry = 5 bantime = 3600   3. create filter file vi /etc/fail2ban/filter.d/pihole-dns.conf # Fail2Ban configuration file # # script from www.marek.tokyo # [INCLUDES] # Read common prefixes. If any customizations available -- read them from # common.local before = common.conf [Definition] _daemon = dnsmasq #...
Read more

Wazuh opensearch dashboard ConnectionError: connect ECONNREFUSED ::1:9200"

 Wazuh opensearch dashboard ConnectionError: connect ECONNREFUSED ::1:9200"    If you see error like this:  Aug 19 13:38:21 wazuh opensearch-dashboards[486]: {"type":"log","@timestamp":"2024-08-19T04:38:21Z","tags":["error","opensearch","data"],"pid":486,"message":"[ConnectionError]: connect ECONNREFUSED ::1:9200"} the problem is with missing host localhost IP at: (default is IPv6 and deamon is not listening on it) /etc/wazuh-dashboard/opensearch_dashboards.yml  opensearch.hosts: https://127.0.0.1:9200 #opensearch.hosts: https://localhost:9200
Read more

Reduce (shrink) and resize raw disk at Proxmox

 Reduce (shrink) and resize raw disk at Proxmox 1. Check the status of raw disk:   #e2fsck -fy /hdd-img/images/111/vm-111-disk-1.raw e2fsck 1.46.5 (30-Dec-2021) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /hdd-img/images/111/vm-111-disk-1.raw: 135279/327680000 files (1.8% non-contiguous), 857599886/1310720000 blocks  2. At first, check raw disk size:   #qemu-img info /hdd-img/images/111/vm-111-disk-1.raw image: /hdd-img/images/111/vm-111-disk-1.raw file format: raw virtual size: 4.88 TiB (5368709120000 bytes) disk size: 3.59 TiB  3. Resize filesystem: -M - will resize to the minimum size based on saved files -p - will display progress bar #resize2fs -M -p /hdd-img/images/111/vm-111-disk-1.raw resize2fs 1.46.5 (30-Dec-2021) Resizing the filesystem on /hdd-img/images/111/vm-111-disk-1.raw to 852166716 (4k) blocks....
Read more