From: Chris Samuel <chris@csamuel.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: HP opensourced advfs from tru64 and what it means for btrfs
Date: Tue, 24 Jun 2008 23:50:17 +1000 [thread overview]
Message-ID: <200806242350.19802.chris@csamuel.org> (raw)
In-Reply-To: <20080623145026.GA13310@2ka.mipt.ru>
[-- Attachment #1: Type: text/plain, Size: 1269 bytes --]
On Tue, 24 Jun 2008, Evgeniy Polyakov wrote:
> Sure it is interesting as studing anything new, but there is nothing in
> advfs which can prevent btrfs from success. Virtually nothing.
As Bdale commented on the LWN article:
http://lwn.net/Articles/287108/
# While it would be fine with HP if someone wants to "port" AdvFS to Linux
# or any other operating system with a GPLv2 compatible license, this
# contribution is not intended to "compete" with other existing file system
# projects underway in and around the kernel.org development community.
#
# Rather, our hope is that the algorithms, design documentation, and test
# suite now available at the AdvFS site... and the active participation of
# HP engineers in various open-source file system projects who have lots of
# AdvFS experience... will help to accelerate the inclusion of AdvFS-like
# enterprise features and capabilities in next-generation file systems for
# Linux.
NB: Asides from briefly using AdvFS under OSF/1 back in the mid-90's I've
no other link to it or HP.
--
Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
This email may come with a PGP signature as a file. Do not panic.
For more info see: http://en.wikipedia.org/wiki/OpenPGP
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 481 bytes --]
prev parent reply other threads:[~2008-06-24 13:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-23 14:37 HP opensourced advfs from tru64 and what it means for btrfs Jeff Schroeder
2008-06-23 14:50 ` Evgeniy Polyakov
2008-06-23 18:21 ` Chris Mason
2008-06-23 18:45 ` Evgeniy Polyakov
2008-06-23 18:59 ` Chris Mason
2008-06-24 13:50 ` Chris Samuel [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=200806242350.19802.chris@csamuel.org \
--to=chris@csamuel.org \
--cc=linux-btrfs@vger.kernel.org \
/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