From: YAMANASHI Takeshi <9.nashi@gmail.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] stealing hard drive's contents
Date: Mon, 21 Nov 2005 11:58:52 +0900 [thread overview]
Message-ID: <efc17e974136f0d5097174b39a9aaab3@orthanc.cc.titech.ac.jp> (raw)
> plan9.ucalgary.ca is going away and i need to move its venti to a
> newer, better hard drive. given that i'm some 3000km away from it and
> there's nobody there to fix things if they hit the fan, what's the
> best way of moving the data onto a local venti?
I just venti/copy'ied from BL to tip9ug venti. I didn't care about
if the time is off-peak or not. :)
But the network has to be stable. If venti/copy stops in the way,
bad things can happen. like, you've got the root score copied to
the local venti but not the whole tree.
--
"on travel, off the network ... and a fossil in my pocket"
next reply other threads:[~2005-11-21 2:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 2:58 YAMANASHI Takeshi [this message]
2005-11-21 3:13 ` Russ Cox
2005-11-21 9:41 ` Dave Eckhardt
-- strict thread matches above, loose matches on Subject: below --
2005-11-21 4:07 YAMANASHI Takeshi
2005-11-21 13:12 ` Russ Cox
2005-11-21 2:47 andrey mirtchovski
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=efc17e974136f0d5097174b39a9aaab3@orthanc.cc.titech.ac.jp \
--to=9.nashi@gmail.com \
--cc=9fans@cse.psu.edu \
/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).