public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jeff Schroeder" <jeffschroed@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: HP opensourced advfs from tru64 and what it means for btrfs
Date: Mon, 23 Jun 2008 07:37:32 -0700	[thread overview]
Message-ID: <c24352ca0806230737g287de15bv5916d1c7501f06be@mail.gmail.com> (raw)

http://advfs.sourceforge.net/ HP open sourced the advfs filesystem
from tru64 Unix today under the gplv2.

>From the page

"""
Our objective is to make the code available so that Linux developers
can pick and choose pieces
that make sense for existing and new linux file systems.  Its also a
good reference for anyone
interested in file systems.  However, we discourage Tru64 users from
trying to build and use the
code as it won't be supported by HP on Tru64.
"""

Would it make sense to look at using any of the code from this in
btrfs, or would it be easier to
re-implement it all over again? Even though filesystems ported from
other Posix operating systems to Linux (Ever looked at XFS code)
can be ugly, this might be a way to accelerate btrfs development.
If nothing else, it might be interesting to see how HP solved problems
btrfs will soon be solving.

-- 
Jeff Schroeder

Don't drink and derive, alcohol and analysis don't mix.
http://www.digitalprognosis.com

             reply	other threads:[~2008-06-23 14:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-23 14:37 Jeff Schroeder [this message]
2008-06-23 14:50 ` HP opensourced advfs from tru64 and what it means for btrfs 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

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=c24352ca0806230737g287de15bv5916d1c7501f06be@mail.gmail.com \
    --to=jeffschroed@gmail.com \
    --cc=jeffschroeder@computer.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