From: Martin C.Atkins <martin@parvat.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] venti ports and productization
Date: Wed, 22 Oct 2003 15:22:11 +0530 [thread overview]
Message-ID: <20031022152211.0594a65d.martin@parvat.com> (raw)
In-Reply-To: <6587E314-03E0-11D8-90F1-000A95B984D8@mightycheese.com>
On Tue, 21 Oct 2003 09:05:31 -0700 Rob Pike <rob@mightycheese.com> wrote:
>
> you should make it protocol-compatible. can't be hard.
> ask for the details.
and On Tue, 21 Oct 2003 06:20:47 -0400 a@9srv.net wrote:
> the fact that it's not protocol-compatable does lower (but not
> totally eliminate) its value to me. if your version doesn't run
> on Plan 9 and host fossil, that does, as well. on the other hand,
I'll have a look at what it would take to make the protocol
compatible. Actually, one of the things I've chosen to do
differently makes the protocol incompatible (it changes the 'score',
in a way that I'd prefer not to discuss until I'm sure it is
desirable!) However, it might be possible to support the Venti
protocol simultaneously.
Rog's Inferno code looks like a good starting point for information
(thanks Rog!), although perhaps I could download the 'real thing'
now, without it influencing my ideas too much about how to approach
various design decisions. (I came across a 'Linux/BSD/etc CD' vendor
here in Bangalore last week, who listed Plan 9 as being available -
is there a Plan 9 UG in Bangalore?!)
> those first two points make me skeptical, but i'll be checking it
> out today. fix those two (so why didn't you use the venti code?)
I also wanted to be very certain that no Venti code found its
way into my implementation, lest I violate any copyrights.
Patents, are of course another issue. I have searched without finding
anything that seems relevant, but that is the problem with patents!
> even the ideas are worth a lot, and if you can put file systems
> on top of it (like fossil does, rather than just using it as an
> archival vault) that my unix systems can use, that's a big win.
I haven't any plans at the moment for a read-write filesystem, like
fossil, but I certainly aim to provide something like /backup.
> and provide a few tools my VP of Marketing can use, and get an
> OS X port, and i'll buy a few coppies.
We certainly intend that the system will be 'user-friendly', but in
the Unix sense, not the lots-of-icons Windows sense.
Martin
--
Martin C. Atkins martin@parvat.com
Parvat Infotech (Private) Limited http://www.parvat.com
prev parent reply other threads:[~2003-10-22 9:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-11 0:37 a
2003-10-11 1:45 ` jmk
2003-10-11 1:50 ` bs
2003-10-11 2:14 ` Russ Cox
2003-10-11 17:05 ` a
2003-10-21 10:14 ` Martin C.Atkins
2003-10-21 10:20 ` a
2003-10-21 14:26 ` jmk
2003-10-21 15:35 ` a
2003-10-21 15:50 ` Russ Cox
2003-10-21 18:24 ` rog
2003-10-22 4:33 ` okamoto
2003-10-22 5:15 ` okamoto
2003-10-22 9:48 ` a
2003-10-22 14:57 ` Richard Miller
2003-10-22 16:54 ` jmk
2003-10-21 17:20 ` Scott Schwartz
2003-10-21 21:30 ` C H Forsyth
2003-10-21 22:13 ` Dan Cross
2003-10-21 16:05 ` Rob Pike
2003-10-21 16:50 ` rog
2003-10-22 9:52 ` Martin C.Atkins [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=20031022152211.0594a65d.martin@parvat.com \
--to=martin@parvat.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).