public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tarkan Erimer <tarkan@turknetserver.com>
To: linux-kernel@vger.kernel.org
Subject: tar.gz and tar.bz2 files of linux kernel on ftp.kernel.org
Date: Thu, 28 Oct 2010 10:18:04 +0300	[thread overview]
Message-ID: <4CC923AC.4050903@turknetserver.com> (raw)

Why there are two different (tar.gz and tar.bz2) kind of compressed 
linux kernel on ftp.kernel.org ?

One kind of (.tar.bz2 or .tar.xz etc.) compressed file, probably, will 
be enough for everybody. Personally, I always download the .tar.bz2 one 
because of its shorter file length compared to .tar.gz. If it's needed 
to have two different kind of compressed linux kernel because of some 
extraordinary situations, maybe we have to consider other better options 
like .tar.xz for instance. I did a quick comparison between .tar.bz2 and 
tar.xz compressed linux-2.6.36. Here is what I found :

linux-a9un:/home/tarkane/Downloads # ls -alh linux-2.6.36.tar.*
-rw-r--r-- 1 root root 68M Oct 21 09:14 linux-2.6.36.tar.bz2
-rw-r--r-- 1 root root 59M Oct 28 09:54 linux-2.6.36.tar.xz
linux-a9un:/home/tarkane/Downloads #

As seen above, .tar.xz has better ratio (%13.24 smaller sized file than 
.tar.bz2.) than the .tar.bz2 one. So,if it could be an, at least, an 
option to offer .tar.xz compressed kernel, we could have the following 
benefits :

- Better usage of ftp.kernel.org's and downloaders' (Some people use 
bandwidth limited Internet connections.) internet bandwidth.
- Better disk space usage on ftp.kernel.org servers due to more smaller 
file sizes.
- It will reduce the load on ftp.kernel.org servers due to shorter 
download times.

I will be happy to hear your opinions about it. :-)

Tarkan

             reply	other threads:[~2010-10-28  7:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-28  7:18 Tarkan Erimer [this message]
2010-10-28  7:44 ` tar.gz and tar.bz2 files of linux kernel on ftp.kernel.org Mikael Abrahamsson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CC923AC.4050903@turknetserver.com \
    --to=tarkan@turknetserver.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox