From: a@9srv.net
To: 9fans@9fans.net
Subject: Re: [9fans] p9p vbackup on linux
Date: Thu, 3 Jul 2008 19:16:39 -0400 [thread overview]
Message-ID: <0d47a3892670317239cd01c8760288f4@9srv.net> (raw)
In-Reply-To: <20080703215705.E47401E8C87@holo.morphisms.net>
// The bytes you didn't post are the first 8 bytes of
// sha1sum /dev/zero.
Hey! How do you know what's in my /dev/zero?
// Better to just use vacfs -m if you want to view vac,
// and skip NFS entirely.
To the extent that I just (or primarialy) want to see vac
dumps, sure. The idea was having a single location for
the variety of image types. Also, doing so with NFS
allows me to do it on a wide variety of Unix hosts with
no modifications or even installed software.
Of course, having played with it for a few days now,
I'll likely just end up doing vac dumps anyway. -a just
makes it that much more compelling.
Anthony
prev parent reply other threads:[~2008-07-03 23:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 10:22 John Soros
2008-06-25 13:21 ` a
2008-07-03 21:59 ` Russ Cox
2008-07-03 23:16 ` a [this message]
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=0d47a3892670317239cd01c8760288f4@9srv.net \
--to=a@9srv.net \
--cc=9fans@9fans.net \
/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).