public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: alb348@gmail.com
To: linux-xfs@oss.sgi.com
Subject: Extended Attributes across filesystems
Date: Sun, 24 Oct 2010 00:52:58 +0200	[thread overview]
Message-ID: <4CC3674A.2050305@gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1238 bytes --]

Hi,

I am doing some research into filesystems, and I understand that you are 
amongst the leading experts on the topic.

I would be really grateful if you could help me by answering some quick 
questions regarding Extended Attributes:

1) Apart from the maximum number / size limitations affecting some 
filesystems (ext2, ext3, ext4), as mentioned in attr5 / man5 section of 
the Linux manual online, are there any other relevant differences across 
the filesystems that may create problems in transfering Extended 
Attributes (along with the files) across filesystems?

2) Will the attr (also called xattr) functions work equally well on all 
the filesystems that support EA? In other words, are the EA-management 
implementations across the Unix filesystems sufficiently standardized?

3) As far as you know, is there any operating system, apart from 
BeOS/Haiku, where the indexing and querying processes of EAs are managed 
by the operating system itself? Do you think that this particular 
feature of Haiku is a really a significant advantage or not so much?

I imagine that you are very busy with you work, and I would really 
appreciate your help.

Looking forward to your reply, I wish you all the best.

Regards,

Tes Bezier



[-- Attachment #1.2: Type: text/html, Size: 1674 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

                 reply	other threads:[~2010-10-23 22:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4CC3674A.2050305@gmail.com \
    --to=alb348@gmail.com \
    --cc=linux-xfs@oss.sgi.com \
    /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