linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Avishay Traeger" <avishay@gmail.com>
To: "Boaz Harrosh" <bharrosh@panasas.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [osd-dev] [RFC 0/9] osdfs
Date: Tue, 4 Nov 2008 12:28:47 +0200	[thread overview]
Message-ID: <c41302d20811040228y23ce963fh39c27f79cb7711df@mail.gmail.com> (raw)
In-Reply-To: <49101FE2.30109@panasas.com>

On Tue, Nov 4, 2008 at 12:11 PM, Boaz Harrosh <bharrosh@panasas.com> wrote:

<snip>

>>> As such, "osdfs" seems like too-generic a name. How about boazfs?  :)
>>
>> I agree.  osdfs is the name given by Avishay and IBM and we just adopted it.
>> I think that obfs (Object-based File System) would better represent
>> what it is (although it's still generic compared to boazfs :-)
>>
>
> If at all then it's avishayfs, but unless I write this filesystem from
> scratch I don't think I can do anything about the name. The code is
> copyrighted to Avishay Traeger, and that is the name he chose. Also
> he has a sourceforge.net project of that name for a long time.
>
> Avishay would you be willing to change the name? See above, people
> think it is too generic a name. Like if someone would do a scsifs
> or blocksfs.
>
> Personally for me it's just a name, I don't mind either way.

I don't care if we change the name.  I suppose we can discuss
alternatives outside of the mailing lists, but I'd rather not do
boazfs or avishayfs :-)

By the way, just to clarify: I wrote this file system at IBM, but they
were nice enough to give me full ownership of the code.  I then
proceeded to put the code up on sourceforge.  Thanks to Boaz and Benny
for reviving the code and submitting it for inclusion in the kernel.

Avishay

      reply	other threads:[~2008-11-04 10:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-30 14:26 [RFC 0/9] osdfs Boaz Harrosh
2008-10-30 14:30 ` [RFC 1/9] osdfs: osd Swiss army knife Boaz Harrosh
2008-10-30 14:31 ` [RFC 2/9] osdfs: file and file_inode operations Boaz Harrosh
2008-10-30 14:32 ` [RFC 3/9] osdfs: symlink_inode and fast_symlink_inode operations Boaz Harrosh
2008-10-30 14:33 ` [RFC 4/9] osdfs: address_space_operations Boaz Harrosh
2008-10-30 14:34 ` [RFC 5/9] osdfs: dir_inode and directory operations Boaz Harrosh
2008-10-30 14:35 ` [RFC 6/9] osdfs: super_operations and file_system_type Boaz Harrosh
2008-10-30 14:36 ` [RFC 7/9] osdfs: mkosdfs Boaz Harrosh
2008-10-30 15:03 ` [RFC 8/9] osdfs: Documentation Boaz Harrosh
2008-10-30 15:04 ` [RFC 9/9] [out-of-tree] open-osd: Global Makefile and do-osdfs test script Boaz Harrosh
2008-11-03 21:07 ` [RFC 0/9] osdfs Jeff Garzik
2008-11-04  8:04   ` [osd-dev] " Benny Halevy
2008-11-04 10:11     ` Boaz Harrosh
2008-11-04 10:28       ` Avishay Traeger [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=c41302d20811040228y23ce963fh39c27f79cb7711df@mail.gmail.com \
    --to=avishay@gmail.com \
    --cc=bharrosh@panasas.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).