From: Sean Quinlan <seanq@research.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Venti and the new plan 9 file system
Date: Fri, 4 Jan 2002 11:14:11 -0500 [thread overview]
Message-ID: <3C35D4D3.7E943BCB@research.bell-labs.com> (raw)
In-Reply-To: <1010141208.636788@firewall.isd.dp.ua>
If all goes well, it should in in the next release of plan 9.
seanq
Wladimir Mutel wrote:
>
> Sean Quinlan <seanq@research.bell-labs.com> wrote:
> > For those of you interested in the direction we are heading
> > with respect to plan 9's file system, you might want to
> > checkout our paper on Venti that will appear in the
> > USENIX fast conference.
>
> > http://www.cs.bell-labs.com/~seanq/pub.html#venti
>
> Very interesting to read. Will its source code be open ? Is it
> legal to reimplement this from scratch, e.g., in Linux ?
next prev parent reply other threads:[~2002-01-04 16:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-04 0:27 Sean Quinlan
2002-01-04 11:42 ` Wladimir Mutel
2002-01-04 16:14 ` Sean Quinlan [this message]
2002-01-04 17:22 ` Wladimir Mutel
2002-01-30 5:29 dmr
2002-01-30 5:31 rob pike
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=3C35D4D3.7E943BCB@research.bell-labs.com \
--to=seanq@research.bell-labs.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).