| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 7 Jun 2011 11:13:06 -0700 From: Tony Luck <tony.luck@...il.com> To: Tarkan Erimer <tarkan@...knetserver.com> Cc: Linus Torvalds <torvalds@...ux-foundation.org>, david@...g.hm, Alessandro Suardi <alessandro.suardi@...il.com>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: Linux 3.0-rc2 On Tue, Jun 7, 2011 at 12:02 AM, Tarkan Erimer <tarkan@...knetserver.com> wrote: > I always use tarballs instead of git. Because; I have several Linux boxes > and just one time I download the kernel tarball then spreading it with scp > to other Linux boxes easily. Otherwise, I have to prepare a tarball by > myself to distribute it which is a time waste and unpractical. Also, getting > the whole 700-800 MB of kernel tree with git is not very Internet bandwidth > (Consider that in some ISPs and countries, Internet usage is limited by > monthly quotas.) friendly. If you maintain a git tree, then at each release you will only need to pull a small amount (the git delta from the last time you pulled). It is then quite simple to make your own tarball to copy around your machines with: $ git archive --format=tar --prefix=linux/ v3.0-rc2 | gzip > v3.0-rc2.tgz So you have a one time large bandwidth investment to do the initial git clone, and then much less traffic for each update. -Tony -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists