From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: overseers@sourceware.org
Subject: Re: sourceware hardware transition
Date: Mon, 11 Mar 2013 23:20:00 -0000 [thread overview]
Message-ID: <20130311232015.GB6202@ednor.casa.cgf.cx> (raw)
In-Reply-To: <20130311212918.GF3288@redhat.com>
On Mon, Mar 11, 2013 at 05:29:18PM -0400, Frank Ch. Eigler wrote:
>Hi -
>
>I propose to spend the week of March 18..22 on the long-awaited
>sourceware hardware transition task. I'd appreciate some overseer
>availability/assistance/advice.
>
>My rough plan is to:
>
>- announce to the various groups that there will be outage(s) next week
>
>Next monday:
>
>- bring down most network services on server
>- do a couple of final rsyncs from server.->server[45]
I did a recent rsync of qmail and www to /sourceware1. I would have done
more but I wasn't sure how the disks should be partioned since root is
a little undersized. I pinged you about this on irc but I don't think
you responded.
I think we have to do some disk reorganization before we start bringing
things up. I don't think there is any reason to keep the rather odd
disk layout that's currently on sourcware anymore where we keep
everything under /sourceware.
I can take some time off next week to work on this if necessary.
cgf
next prev parent reply other threads:[~2013-03-11 23:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 21:29 Frank Ch. Eigler
2013-03-11 21:43 ` Jeff Law
2013-03-11 21:58 ` Jeff Law
2013-03-11 23:20 ` Christopher Faylor [this message]
2013-03-12 5:25 ` Ian Lance Taylor
2013-03-13 6:36 ` Jonathan Larmour
2013-03-13 17:23 ` Frank Ch. Eigler
2013-03-13 17:26 ` Christopher Faylor
2013-03-20 1:41 ` Gerald Pfeifer
2013-03-20 2:19 ` Christopher Faylor
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=20130311232015.GB6202@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=overseers@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).