9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Distributed filesystems:  Plan 9 vs. Linux
Date: Sun, 29 Feb 2004 12:38:51 -0700	[thread overview]
Message-ID: <5eb036eb621fc8ca01d2b10665ad4e7d@plan9.ucalgary.ca> (raw)
In-Reply-To: <029c01c3fefe$95f0a430$6539a8c0@hpn5415>

It's not that you can't do it in Lunix -- look at Globus' Replica
Location Service or MDS (Metasomething Discovery Service, they keep
changing the name) for just a few of the options for handling
replication, there are others specifically tailored to clusters too.
They are all crufty, don't play well with each other, require their
own clients and a pain in the proverbial to administer, but that's a
consequence of the multiple layers of abstraction they're built
upon to avoid admitting that UNIX simply lacks a decent
mechanism for importing remote resources.

Binding remote exports in a union directory is so trivial in Plan 9
that it's really a non-issue (you'll spend much more time tracking
which files are stored where, especially if they move).  The show
stoppers are the clients -- what will you be using on the client side?
Will you require users to be running Plan 9 to access the service, or
are you prepared to spend some time developing a way to bring it to
their environment (by, say, implementing a 9p client suitable for the
task, something like v9fs)...

Plan 9 lets you do something elegantly, bringing the result to the
outside world may be a bit trickier :)

my $0.02: andrey



  reply	other threads:[~2004-02-29 19:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-29 19:59 John E. Barham
2004-02-29 19:38 ` andrey mirtchovski [this message]
2004-02-29 23:32   ` boyd, rounin
2004-03-01 17:27   ` John E. Barham
2004-03-01 17:37     ` matt
2004-03-02  4:10       ` Martin C.Atkins
2004-02-29 20:26 ` Jeff Sickel
2004-03-01 17:14   ` John E. Barham
2004-03-01 18:26     ` Jeff Sickel
2004-03-01  1:56 ` James Horey
2004-03-01  2:04   ` Geoff Collyer
2004-03-03  7:46 YAMANASHI Takeshi

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=5eb036eb621fc8ca01d2b10665ad4e7d@plan9.ucalgary.ca \
    --to=mirtchov@cpsc.ucalgary.ca \
    --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).