From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: "Frank Ch. Eigler" <fche@redhat.com>,
Sourceware Overseers <overseers@sourceware.org>,
Angela Marie Thomas <angela@releasedominatrix.com>,
Jonathan Larmour <jifl@jifvik.org>
Subject: Re: sourceware hardware transition plan, part 1/N
Date: Mon, 10 Sep 2012 19:01:00 -0000 [thread overview]
Message-ID: <20120910190039.GA3482@ednor.casa.cgf.cx> (raw)
In-Reply-To: <20120910175659.GE8150@redhat.com>
On Mon, Sep 10, 2012 at 01:56:59PM -0400, Frank Ch. Eigler wrote:
>Hi, Angela -
>
>> [...] Is the hardware already racked with console access? [...]
>
>Yes and no. The /root/.ssh/authorized_keys have been copied over so
>y'all may *look around* via ssh root@server[45].sourceware.org. The
>virtual console is on the RH internal network.
But that's nothing new...
Should we start rsyncing data over? It seems like we'll want a full
backup of old sourceware there eventually.
cgf
next prev parent reply other threads:[~2012-09-10 19:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 21:47 Frank Ch. Eigler
2012-09-07 22:47 ` Joseph S. Myers
2012-09-08 12:23 ` Frank Ch. Eigler
2012-09-08 13:19 ` Joseph S. Myers
2012-10-28 22:44 ` Gerald Pfeifer
2012-11-03 17:31 ` Daniel Berlin
2012-09-07 23:55 ` Jonathan Larmour
2012-09-10 17:32 ` Angela Marie Thomas
2012-09-10 17:57 ` Frank Ch. Eigler
2012-09-10 19:01 ` Christopher Faylor [this message]
2012-09-10 20:18 ` Angela Marie Thomas
2012-09-12 15:29 ` Frank Ch. Eigler
2012-09-12 15:37 ` Christopher Faylor
2012-09-12 15:51 ` Christopher Faylor
2012-09-12 15:59 ` Joseph S. Myers
2012-09-12 16:20 ` Jeff Law
2012-09-12 16:29 ` Joseph S. Myers
2012-09-12 16:09 ` Frank Ch. Eigler
2012-09-12 17:09 ` Christopher Faylor
2012-09-12 20:48 ` Joseph S. Myers
2012-09-13 3:18 ` Christopher Faylor
2012-09-13 3:59 ` Ian Lance Taylor
2012-09-07 23:59 ` 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=20120910190039.GA3482@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=angela@releasedominatrix.com \
--cc=fche@redhat.com \
--cc=jifl@jifvik.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).