From: smiley@icebubble.org
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] FS for sharing between Linux and Plan 9
Date: Mon, 31 Oct 2011 01:03:11 +0000 [thread overview]
Message-ID: <861utuht0w.fsf@cmarib.ramside> (raw)
In-Reply-To: <CAOr72mj8-FACD4FW2cd6ms++E6qT0u4xDpw=wRajSS48C2zwmg@mail.gmail.com> (Jeremy Jackins's message of "Sun, 30 Oct 2011 16:30:09 -0600")
Jeremy Jackins <jeremyjackins@gmail.com> writes:
> Until recently I was using btrfs on this disk for the snapshot
> support, and was only sharing it between Linux machines.
I know it's kinda OT, but was there a particular reason you wanted more
than btrfs could offer?
> I like Fossil/Venti, but if I use this on the HDD I lose the ability
> to take the disk outside of my home network and plug it into a Linux
> machine (right?)
There's a port of Plan 9 utilities to Linux userspace. It's called Plan
9 Port (aka p9p). See http://swtch.com/plan9port/. Linux machines with
p9p should be able to talk to fossil/venti.
Of course, if your "external drive" contains a CPU (i.e., one of the NAS
boxen being sold as "external drives"), the "drive" itself may be able
to run 9p. :)
> Is there an obvious solution which I am missing? My goal essentially
> is to keep all my important files in this central location, easily
> update it with new changes from machine A, then update machine B with
> these changes.
Would replica meet your needs? Under some circumstances, rsync
outperforms replica. For some purposes, a DVCS such as Mercurial (which
has also been ported to P9) is more appropriate. It depends on a mix of
factors.
--
+---------------------------------------------------------------+
|Smiley <smiley@icebubble.org> PGP key ID: BC549F8B |
|Fingerprint: 9329 DB4A 30F5 6EDA D2BA 3489 DAB7 555A BC54 9F8B|
+---------------------------------------------------------------+
next prev parent reply other threads:[~2011-10-31 1:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-30 22:30 Jeremy Jackins
2011-10-31 1:03 ` smiley [this message]
2011-10-31 1:35 ` andrey mirtchovski
2011-10-31 5:51 ` Jeremy Jackins
2011-11-04 20:50 ` smiley
2011-11-04 20:57 ` Russ Cox
2011-11-04 22:53 ` David du Colombier
2011-11-05 20:32 ` smiley
2011-11-05 22:56 ` David du Colombier
2011-11-07 17:09 ` David du Colombier
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=861utuht0w.fsf@cmarib.ramside \
--to=smiley@icebubble.org \
--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).