From: "Bart Van Kerkhove" <overige.vk@easynet.be>
To: gentoo-portage-dev@lists.gentoo.org
Subject: [gentoo-portage-dev] downloading kernel sources with portage
Date: Sun, 28 Mar 2004 20:02:27 +0200 (CEST) [thread overview]
Message-ID: <1188.10.97.1.45.1080496947.squirrel@127.0.0.1> (raw)
Hi there,
Ive been using Gentoo Linux for about a year now and one thing that has
been bothering me is that every time a new kernel comes out portage
downloads the full version of the new kernel instead of a patch. Since
every kernel gets stored in distfiles it would be very easy to use the
older kernel and only download the patch.
For example the 2.6.x series:
linux-2.6.0.tar.bz2 32476 KB 32 MB
linux-2.6.1.tar.bz2 32461 KB 32 MB
linux-2.6.2.tar.bz2 33106 KB 32 MB
linux-2.6.3.tar.bz2 33469 KB 33 MB
linux-2.6.4.tar.bz2 33581 KB 33 MB
linux-2.6.*.tar.bz2 165093 KB 161 MB
Since portage has downloaded all 5 full kernels for me Ive downloaded
160MB of kernel sources.
If we had simply patched the allready stored 2.6.0 kernel it would have
been only 40MB:
linux-2.6.0.tar.bz2 32476 KB 32 MB
patch-2.6.1.bz2 760 KB 1 MB
patch-2.6.2.bz2 2268 KB 2 MB
patch-2.6.3.bz2 2006 KB 2 MB
patch-2.6.4.bz2 2210 KB 2 MB
linux.*+patch.* 39720 KB 39 MB
Ive tried this myself and its as easy as:
tar -xvjpf linux-2.6.0.tar.bz2 && cd linux-2.6.0
patch -p1 < ../patch-2.6.1
patch -p1 < ../patch-2.6.2
patch -p1 < ../patch-2.6.3
patch -p1 < ../patch-2.6.4
cd .. && mv linux-2.6.0 linux-2.6.4
Since bandwith doesnt grow on trees and the patching doesnt take long,
saving far over a gigabyte every 10 users it seems to me this is well
worth it. I understand we cant patch forever, but every 5 kernels or so
is a big saving in bandwith.
Comments? What do you think?
FrostFire
--
gentoo-portage-dev@gentoo.org mailing list
next reply other threads:[~2004-03-28 18:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-28 18:02 Bart Van Kerkhove [this message]
2004-03-28 22:21 ` [gentoo-portage-dev] downloading kernel sources with portage Lisa Seelye
2004-03-29 12:33 ` Michael Kohl
2004-03-29 16:58 ` Bart Van Kerkhove
2004-03-30 11:02 ` Bart Van Kerkhove
2004-04-04 11:08 ` Brian Harring
2004-03-28 23:48 ` Jeremy Maitin-Shepard
2004-04-03 21:50 ` Bart Van Kerkhove
2004-04-04 11:10 ` Brian Harring
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=1188.10.97.1.45.1080496947.squirrel@127.0.0.1 \
--to=overige.vk@easynet.be \
--cc=gentoo-portage-dev@lists.gentoo.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