public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: linux-kernel@vger.kernel.org
Cc: dev@work.bitmover.com
Subject: [bkbits] predicted outage
Date: Thu, 1 Apr 2004 18:18:00 -0800	[thread overview]
Message-ID: <200404020218.i322I0GC017257@work.bitmover.com> (raw)

We're moving office space in about 10 days.  We expect one of our T1 lines
to be switched to the new office as of April 9th.  If that works, then we'll
move all the hardware to the new office and flip the routes to that T1 from
the old T1.  Sounds simple and since the new ISP is the old ISP it might 
actually work (Hah.  Like anything goes that smoothly).  On the other hand,
it might not go great and there might be some time where bkbits.net is not
off the air but it might be at a different IP address.  And DNS takes a 
while to time out.

As we get closer, I will remind you approximately 48 hours and 24 hours 
before the move so those of you who need to sync can sync and not be
disturbed.  If you want more status than that, let me know.

--lm

             reply	other threads:[~2004-04-02  2:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-02  2:18 Larry McVoy [this message]
2004-04-03  2:16 ` [bkbits] predicted outage David T Hollis

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=200404020218.i322I0GC017257@work.bitmover.com \
    --to=lm@bitmover.com \
    --cc=dev@work.bitmover.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