From: Larry McVoy <lm@bitmover.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: T1 line is here
Date: Tue, 25 Sep 2001 17:17:43 -0700 [thread overview]
Message-ID: <20010925171743.H28189@work.bitmover.com> (raw)
Our new T1 line is installed and working. We'll be updating the repo
server so that it resolves to the T1 line in the next day or two; we'll
leave the old address connected as well so things will continue to work
while the DNS entries time out.
It should be pretty zippy, the router in our office with the repository
server is 192.132.92.1 and pings from Cort's machine are 41 milliseconds,
pings to the east cost are 60 milliseconds. Those are both 30 ms less
than our DSL line, so not only is the bandwidth better, the latency seems
better as well.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~2001-09-26 0:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010925171743.H28189@work.bitmover.com \
--to=lm@bitmover.com \
--cc=linuxppc-dev@lists.linuxppc.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).