From: "Paul G. Allen" <pgallen@randomlogic.com>
To: "kplug-list@kernel-panic.org" <kplug-list@kernel-panic.org>,
"Linux kernel developer's mailing list"
<linux-kernel@vger.kernel.org>,
"kplug-lpsg@kernel-panic.org" <kplug-lpsg@kernel-panic.org>
Subject: Re: Linx Kernel Source tree and metrics
Date: Fri, 27 Jul 2001 16:32:49 -0700 [thread overview]
Message-ID: <3B61FA21.CFF3BB08@randomlogic.com> (raw)
In-Reply-To: <3B612D26.BA131CEC@randomlogic.com> <01072714523106.00285@starship> <200107271308.f6RD8EA02743@mobilix.ras.ucalgary.ca> <3B61D1DA.49AFC88D@randomlogic.com>
It seems my web server is being hammered pretty hard with accesses to this data. I have spoken to the powers that be here at Akamai and it's quite possible we
can make this data available in one of our high-bandwidth (gigabit) web pools next week.
If this happens, I'll update it to the latest source (whatever happens to be available at that time). If it doesn't, I'll update it anyway and just bite the
bullet and upload the data to a server with more bandwidth.
PGA
--
Paul G. Allen
UNIX Admin II/Programmer
Akamai Technologies, Inc.
www.akamai.com
Work: (858)909-3630
Cell: (858)395-5043
next prev parent reply other threads:[~2001-07-27 23:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-27 8:58 Linx Kernel Source tree and metrics Paul G. Allen
2001-07-27 12:52 ` Daniel Phillips
2001-07-27 13:08 ` Richard Gooch
2001-07-27 20:40 ` Paul G. Allen
2001-07-27 23:32 ` Paul G. Allen [this message]
[not found] <200107270917.f6R9HUt19989@antimatter.net>
2001-07-27 9:25 ` Paul G. Allen
2001-07-27 9:33 ` Paul G. Allen
2001-07-27 9:53 ` Paul G. Allen
2001-07-27 9:52 Thomas Foerster
2001-07-27 10:26 ` Paul G. Allen
2001-07-27 10:30 ` Neil Brown
2001-07-27 11:18 ` Jan-Benedict Glaw
2001-07-27 11:47 ` Paul G. Allen
[not found] <no.id>
2001-07-27 23:46 ` Alan Cox
2001-07-28 0:20 ` Paul G. Allen
2001-07-28 1:33 ` Paul G. Allen
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=3B61FA21.CFF3BB08@randomlogic.com \
--to=pgallen@randomlogic.com \
--cc=kplug-list@kernel-panic.org \
--cc=kplug-lpsg@kernel-panic.org \
--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;
as well as URLs for NNTP newsgroup(s).