From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: linux-nfs@vger.kernel.org, nfsv4@linux-nfs.org,
pnfs@linux-nfs.org, labeled-nfs@linux-nfs.org,
keyrings@linux-nfs.org
Cc: "Dr. J. Bruce Fields" <bfields@fieldses.org>
Subject: linux-nfs.org will be going down for an upgrade today...
Date: Mon, 10 May 2010 13:07:00 -0400 [thread overview]
Message-ID: <1273511220.5740.12.camel@localhost.localdomain> (raw)
Hi,
I'm planning on upgrading the Linux distribution on linux-nfs.org to a
newer release today. Unfortunately, this has to be done during working
hours since I no longer have physical access to the CITI machine room
(and so have to rely on Bruce being available should the remote access
fail).
I expect to start at around 2pm EST (in 1 hour from now). Hopefully the
down time will be less than an hour or two.
During that time, expect no access to www.linux-nfs.org, the git daemon,
wiki.linux-nfs.org, bugzilla.linux-nfs.org or the linux-nfs.org mailing
lists.
I'll send a mail once everything is up and running again...
Cheers
Trond
next reply other threads:[~2010-05-10 17:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-10 17:07 Trond Myklebust [this message]
2010-05-11 19:12 ` linux-nfs.org will be going down for an upgrade today Trond Myklebust
[not found] ` <1273605127.2810.12.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-05-17 17:19 ` Chuck Lever
2010-05-17 17:38 ` Trond Myklebust
[not found] ` <1274117929.4354.3.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2010-05-17 17:48 ` Chuck Lever
[not found] ` <4BF18172.4040607@oracle.com>
2010-05-17 19:15 ` Trond Myklebust
[not found] ` <1274123725.4354.6.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2010-05-17 20:16 ` Chuck Lever
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=1273511220.5740.12.camel@localhost.localdomain \
--to=trond.myklebust@fys.uio.no \
--cc=bfields@fieldses.org \
--cc=keyrings@linux-nfs.org \
--cc=labeled-nfs@linux-nfs.org \
--cc=linux-nfs@vger.kernel.org \
--cc=nfsv4@linux-nfs.org \
--cc=pnfs@linux-nfs.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).